Measuring calls and bookings from Google Ads
A decision path for the businesses whose customers ring or book
How to count calls and bookings from Google Ads properly: forwarding numbers, call assets, the sixty-second rule, booking-engine thank-you pages, iframes.
By Daniel Stoychev, Webso Digital · 5 September 2026 · 5 min read
A Google Ads account only improves when it can see what a real enquiry looks like, and for most Manchester service businesses the real enquiry is a phone call or a booking rather than a form. Calls are measured with Google's forwarding numbers on the ad and on the website, counted only above a length that filters out misdials; bookings are measured on the confirmation page of the booking system, or by an event the system fires when a booking completes. The path below asks which of the two you live on and follows it to the setup that counts it once.
Start here: what does a customer do?
Three answers cover nearly every business. A plumber, a locksmith, a solicitor and a garage get rung. A restaurant, a clinic, a salon and a venue get booked, often through a third-party system. A dentist, a physio and a hotel get both, depending on the customer's age and the time of day. Pick the answer that describes most of your enquiries, follow that branch, and add the other branch afterwards if it applies.
Branch A: the phone rings
Calls from the ad itself
A call asset adds your number to a text ad, and on a phone it becomes a button. A call-only ad has no website link at all; its whole job is the tap. Both use a Google forwarding number, which is a temporary number Google shows in place of yours and routes to you, so the call is counted in the account with its length. Set the conversion to count calls over a threshold; we use around sixty seconds, because shorter calls are usually wrong numbers, engaged tones and people asking whether you cover Wigan. Recording is not part of it; Google counts duration, not content.
Calls from the website after the click
Most calls come after the click, from the number on your landing page. Google's website call conversion swaps that number for a forwarding number when the visitor arrived from an ad, using a small script on the page, and counts the call with its length in the same way. The number in your header has to be plain text or a link Google can find, and the swap must survive whatever your website builder does to the page; we test it by clicking an ad from a phone and reading the number that appears.
When forwarding numbers are not allowed
Some businesses cannot show a number that is not theirs, because a regulator, a franchise or a directory listing requires the real one. The fallback is a click-to-call conversion, which counts the tap on the number without counting the call's length, and a manual reconciliation each month against the phone system's log. It is weaker, and the report should say so.
Branch B: the diary fills
A booking system on your own domain
If the booking completes on a page of your own site, the confirmation page is the conversion. Fire the Google Ads conversion tag on that page only, with the booking value if the system exposes it, and make sure the page cannot be reached by refreshing or bookmarking without a booking, or it will count twice. The same page sends an event to GA4, and the two counts should agree to within a handful each month.
A third-party booking engine in an iframe
This is where most restaurant, salon and clinic accounts go wrong. The booking widget lives on the booking company's domain inside a frame, and your tags cannot see inside it. Three options, in order of preference: the booking platform sends a completion message to the parent page that you can listen for and turn into a conversion; the platform offers its own Google Ads or GA4 integration you switch on with your conversion ID; or the platform redirects to a thank-you page on your domain after booking, which you tag as in the previous paragraph. If none of the three exists, the honest fallback is counting the click into the booking widget as a soft conversion and reconciling against the diary monthly.
Bookings by phone
A clinic whose older patients ring rather than book online is in both branches at once. Count the sixty-second call as a conversion in Branch A, and mark it as a booking enquiry rather than a booking, so the report does not claim more appointments than the diary shows.
Both branches: the rules that keep the count honest
| Rule | Why it matters for bidding |
|---|---|
| One action per real enquiry, tested by you | Smart Bidding optimises to whatever fires; a doubled count halves the reported cost per lead and misleads the strategy |
| Primary actions only for money events | A newsletter sign-up or a menu view counted as primary pulls bids towards browsers |
| Call length threshold set and written down | Without it, every ten-second misdial teaches the account that the search that caused it was good |
| Consent Mode installed with the cookie banner | Under UK law the tags wait for consent; with Consent Mode, Google models the visitors who decline so the count is not full of holes |
| GA4 events named the same as the Ads conversions | Two systems that disagree by a wide margin mean one of them is broken, and the report should say which |
| A monthly reconciliation against the phone log or the diary | The account's count is a proxy; the diary is the truth |
What the report should say once it works
A Manchester restaurant's monthly report should read: spend, calls over a minute, completed bookings, cost per booking, and the share of bookings on matchdays and market weekends against the rest. A plumber's should read: spend, calls over a minute by borough, cost per call, and the share of calls the owner says turned into jobs. The last line comes from the client, and without it the report is only half done.
The most common failure we find is an account that has been 'converting' for a year on a thank-you page that fires whenever anyone lands on it. Fixing that one action changes what every bid decision has been based on, and the first month afterwards usually looks worse before it looks better. That is the honest number arriving.
If you would like the calls and bookings counted properly before another month of bidding is based on the wrong number, tell us how your customers reach you.
Questions on this topic
Why sixty seconds and not thirty?
Thirty seconds catches the caller who asks whether you cover their area and hangs up. Sixty catches a real conversation for most trades and clinics. It is a judgement, and we adjust it after reading a month of call lengths in the account.
Will a forwarding number confuse my customers?
Rarely. It rings your real line and the caller never dials it twice. The one problem is a customer saving the forwarding number, which expires; the fix is the real number in the email and on the invoice.
My booking system is Fresha, ResDiary or similar. Can it be tracked?
Usually. Most of the large hospitality and salon platforms offer a Google Ads or GA4 integration, or a redirect to a page of your choice after booking. Which one you have decides the method, and we check before promising a number.
Does GA4 replace Google Ads conversion tracking?
No. GA4 can import conversions into Google Ads, and that works, but the native Google Ads tag with Consent Mode counts more reliably for bidding. We run both and expect them to agree roughly, not exactly.
Can I see which borough the calls came from?
Yes. Calls counted through forwarding numbers appear in the locations report like any conversion, so the cost per call in Trafford against Oldham is a normal monthly read.