Services / Measurement
If the phone rings and nothing counts it, your data lies
Local customers call. Accounts that only count form fills feed Smart Bidding a distorted map, and the branches whose customers prefer the phone quietly lose budget for it. We wire calls, forms, and booked revenue into one per-branch measurement layer before optimizing anything.
What gets installed?
- Google forwarding numbers on ads plus dynamic number insertion on landing pages, mapped per branch
- Minimum-duration thresholds so misdials and robocalls never count as conversions
- GA4 events per location, with the Consent Mode v2 setup the EEA and UK have run under since March 2024, verified in Tag Assistant
- Offline conversion imports from your booking system or CRM, upgrading calls to appointments and revenue
- A post-release test script your developers can run in minutes, so site updates stop silently breaking the wiring
What changes once calls count?
The map redraws. In the gym-chain engagement, adding call conversions raised measured lead volume enough that three sites the blended report had written off turned out to be phone-heavy performers; the full sequence is in that diary, where trial CPL fell from €38 to €19 in eight weeks. Bidding followed the corrected data, never a strategy epiphany. Against the health and fitness vertical's $67.36 median CPL, branches that looked expensive were merely miscounted.
Why offline imports are the difference-maker
A call is interest; a booked appointment is money. Importing booked outcomes back into Google Ads lets bidding optimize toward revenue instead of ring time, and it is the only clean way to judge Local Services Ads, which bill per lead, against search, which bills per click. The channel comparison in the branch ledger, LSA cost per lead (about $53 for home services) against search cost per lead, only means something when both resolve to the same booked outcome. Details on the LSA side sit in that service.
The compliance stance
Counting without recording is the default: number, duration, branch, campaign, and nothing else. Consent Mode v2 passes visitor choices to Google's tags, and since March 2025 accounts without it lose conversion modeling for non-consented EEA users entirely, so the consent layer is a performance requirement as much as a legal one. Where a client wants call recording for training, that runs on their phone system under their own lawful basis, outside our tracking stack.
Fair questions
Why does call tracking matter so much for local businesses?
Because the phone is where local conversions happen: bookings, quotes, and reschedules arrive by call far more than by form. An account bidding only on form fills undercounts most branches badly, and Smart Bidding then starves the locations whose customers prefer calling. Counting calls per branch corrects both.
How are calls counted as conversions?
Google forwarding numbers on ads and dynamic number insertion on landing pages, with a minimum-duration threshold so misdials don't count. Each call maps to its branch and its campaign. Where a booking system or CRM exists, offline imports upgrade 'call happened' to 'appointment booked' and 'revenue banked'.
Is this GDPR-compliant?
Yes, wired properly: Consent Mode v2 has been required for EEA and UK advertisers since March 2024, and call recording, where used at all, needs its own announcement and lawful basis. We default to counting and routing calls without recording them, which keeps the data useful and the compliance surface small.
What does the tracking setup cost?
Priced after a quick look at your stack, because a 6-branch dental group with one booking system differs from a 40-site franchise with none. Typical setups land between €900 and €2,800 one-off, and the scope arrives in writing before any tag or number changes.
Find out what your phones know
The free audit flags which branches are undercounted; the tracking scope follows in writing.
Request your free audit