Measurement guide
Conversion tracking that counts enquiries rather than page views
Almost every account we audit is optimising against a number that is wrong. Not slightly wrong. Counting thank-you page loads that never happened, or the same enquiry three times, or a form that stopped submitting in March.
12 min read · 7 steps · By Aman Mishra · Written August 2026
What you end up with
A short list of counted actions that each represent one real enquiry, imported into Google Ads without duplication, and reconciled against your inbox for a full month.
Have these ready
- Edit access to the site or its tag manager
- Admin on GA4 and on Google Ads
- A month of enquiries you can count by hand
What it takes
12 min to read
7 steps, in the order below. Skip to the one you are stuck on.
Optimising against a wrong number does not produce a wrong answer slowly. It produces a confidently wrong answer quickly, because every system downstream is working hard to get more of whatever it is counting.
This is the first thing we fix on any account, before touching a bid or a page, and it is the least interesting work in marketing.

-
Write down what counts as a lead before opening any tool
The list should be short and every item should be something a person did that could become revenue. If you cannot say why an action is on the list, it is not.
On paper, before anything technical.
For most businesses the list is short: the enquiry form, the phone call, the quote request, the booking, and possibly a chat conversation that reaches a real person. Four or five items.
For each one, ask what it is worth and whether it could become revenue. If the answer is unclear, it does not belong on the list.
Things that are not leads, and are counted as leads constantly: newsletter signups, PDF downloads, video plays, time on page, scroll depth, visits to the contact page. All of these can be worth measuring. None of them is somebody asking you to sell them something, and optimising a campaign toward them produces traffic that downloads things and never calls.
-
Count the enquiry rather than the page
A thank-you page view is a proxy and it breaks in several predictable ways. Fire on the successful submission event where you can.
The default setup counts a view of the thank-you page. It is easy and it is wrong often enough to matter.
Three ways it breaks. Somebody reaches the page from the navigation or an old bookmark, and gets counted. Somebody refreshes after submitting, and gets counted twice. The site is a single page application, and the view fires on a route change whether or not the submission succeeded.
Where your form can fire an event on successful submission, use that. The event fires when the thing you care about actually happened, and only then.
If a thank-you page is your only option, at minimum make sure it is not reachable from the navigation, and set it to noindex so it does not collect organic traffic.
-
Track calls properly or admit you are not tracking them
For most service businesses the phone is the main channel and it is the one usually missing from the numbers entirely.
For most service businesses this is the biggest hole in the numbers.
The proper version is dynamic number insertion: a tracking number displayed on the site that swaps depending on the source, so the call is attributable. It costs money and it works.
The cheap version is tracking clicks on the tel link. This is not a call. Somebody can click and hang up, and calls from a desktop where the number is copied out by hand are invisible. It is still far better than counting nothing.
Whichever you choose, be clear about what it is. A business that treats tel link clicks as calls will overstate its lead count. A business that ignores the phone entirely will understate it and misjudge which channels work, because the channels that drive calls will look dead.
-
Set the events up once and import them
Define the conversion in one place, then bring it into Google Ads. Defining the same action separately in two systems is how accounts end up double counting.
Define each conversion once, then bring it where it needs to go.
The usual sensible arrangement is to define the events in GA4 and import them into Google Ads as conversion actions. One definition, one source of truth, and if the definition changes it changes everywhere.
The failure mode is defining the same action twice: once as a GA4 event imported into Ads, and again as a native Google Ads tag on the same form. Now every enquiry is counted twice, the cost per conversion looks half what it is, and bidding is being told the account is twice as successful as it is.
If you inherit an account, check for this specifically. It is common and it is invisible unless you go looking.
-
Decide what is primary and what is secondary
Only the actions that represent a real enquiry should be optimised against. Everything else is useful context and should not influence bidding.
Google Ads lets you mark conversion actions as primary or secondary, and GA4 has key events. Use them.
Primary means it influences bidding. Only actions on your short lead list belong here. If a newsletter signup is primary, Smart Bidding will find people who sign up for newsletters, and it will be very good at it.
Secondary means it is recorded and reported but does not steer anything. This is where downloads, signups and softer engagement belong. Useful for understanding, not for optimising.
-
Check the numbers against your actual inbox
Take a full month, count the real enquiries by hand, and compare. This is the step that finds everything the setup missed.
This is the step everybody skips and it is the one that finds the problems.
Take a full calendar month. Count the enquiries you actually received: emails in the inbox, calls in the log, forms in the CRM. Deduplicate the people who filled in a form and then rang.
Now compare with what the tracking reports.
If tracking is higher, you are double counting somewhere, or counting something that is not an enquiry, or a bot is filling in your form. If it is lower, something is not firing, or consent is blocking it, or a channel is not tagged.
Being within a reasonable margin is fine. Being out by a factor is a setup problem, and until it is resolved every optimisation decision made from the data is a guess.
-
Add a monitor so you find out when it breaks
Tracking fails silently. A form change, a plugin update or a consent banner can stop the data without anything looking wrong on the site.
Tracking fails silently and it fails often. A theme update, a form plugin change, a new consent banner, a developer removing a script that looked unused.
The site keeps working. The forms keep arriving. The number just stops, and nobody notices for six weeks because a downward trend looks like a bad quarter.
Two cheap protections. Set an alert for conversions falling below a floor over a few days. And put the reconciliation into your monthly routine: real enquiries counted by hand against reported conversions, one line in the report. It takes ten minutes and it is the only thing that reliably catches this.
When you have done all 7
A short list of counted actions that each represent one real enquiry, imported into Google Ads without duplication, and reconciled against your inbox for a full month.