CallRail on your landing pages
Local service campaigns have two kinds of leads: the people who fill the form and the people who call. Most reporting only sees the first kind, so a Google Ads campaign that keeps a roofer's phone busy can look like it barely converts. CallRail fixes the second half by swapping a tracking number onto the page and logging every call with the source, the campaign and, with a website pool, the keyword.
LanderLab is where those campaigns land. You build a landing page per service, per city or per promo, test variants against each other and send the form leads to the CRM. Drop CallRail's JavaScript snippet into the page's custom code, or once into the domain's so every landing page on it loads it, and the calls those pages drive are counted too. The report that goes to the business owner then counts the callers as well as the form fills.
CallRail calls, traced to the page and the ad
With CallRail's snippet on your LanderLab page, the calls that come from it are tracked back to that page and to the ad the caller clicked. In CallRail, those calls sit next to the ones from the rest of your marketing, each with the source and campaign it came from.
How deep that goes is up to you. A source tracking number tells you the channel. A website pool gives each visitor a number for the length of the visit, and CallRail links the call to that visitor's session: the landing page, the source and the keyword they searched.
When the lead picks up the phone
For a roofer, a dentist or a law office, the lead often calls instead of filling in the form. If only form fills are counted, a campaign that makes the phone ring looks like it loses money and gets cut. Tracing calls back to the page and the ad shows what the spend actually bought.
That matters most when you test. Run two landing pages for the same service and the one with fewer form fills may be the one that rings the phone more. With calls tracked per page, you judge them on both.
Google Ads calls reported as conversions
CallRail's visitor tracking captures the gclid for each visitor. With CallRail's Google Ads integration on and auto-tagging enabled in Google Ads, calls from Google PPC are reported back to Google Ads as conversions, either as one Phone Call conversion or split into first-time and repeat callers.
The campaign then bids with the calls in view. Keywords that drive calls but few forms stop getting starved, and the account learns from the leads that actually reached the business.
Calls an owner can check
If you run ads for local businesses, a tracked call is a result the owner can hold against their own phone log: who called, when, and from which campaign. Put that beside the page's form leads and the month's report covers everyone the ads brought in, not only the people who typed.
The same snippet runs CallRail's form tracking, which captures standard HTML forms with a submit button. Where it picks up your page's form, the form leads sit in CallRail next to the calls; where it doesn't, LanderLab sends them to the CRM with the same UTMs in hidden fields.
