Google Ads conversion tracking: setups, breaks, fixes
Five ways to tell Google Ads what a conversion is, the failures that quietly starve smart bidding, the order to check them, and the point at which you pause automated bidding and fix the tag.
By Daria Dovzhikova · September 2026
The short version
- Without conversion tracking, Google Ads optimises for clicks. It has nothing else to optimise for.
- Five setups: Google tag, Tag Manager, GA4 import, enhanced conversions, offline import. Pick one per action. Two on the same action doubles the count.
- Purchases count Every, leads count One. Google says so, and a refreshed thank-you page is why.
- The number to watch is the ratio of reported conversions to real orders. When it moves and you cannot explain it, pause automated bidding on the affected campaigns and fix the tag.
Three years, three hundred thousand dollars, no tracking
A home services owner on r/PPC wrote it up in one paragraph: a relative set up the account about three years ago, tickets run $150 to $600, over $300,000 spent since, and no real conversion tracking was ever set up. The account had been running the whole time. Google Ads had been bidding on the only signal it had, which was clicks, for three years.
That is the extreme case, but the ordinary case is a version of it. Tracking exists, it is partly broken, and nobody has compared what the platform reports to what the business banked. Google's own description of conversion tracking is plain: you choose what you identify as valuable, a purchase, a sign-up or a phone call, and the platform measures it. Every automated bidding strategy sits on top of that measurement. If the measurement is wrong, the bidding is wrong with it, quietly and at scale.
The five setups
| Setup | What it sees | What it needs | How it breaks |
|---|---|---|---|
| Google tag on the page | Browser events on your site: purchase, form submit, call click. | The tag on every page and an event snippet on the conversion action. Auto-tagging on so the click ID is in the URL. | Blockers, declined consent, redirects that drop the click ID, the snippet firing on refresh. |
| Google Tag Manager | The same browser events, managed through a container. | A conversion tag per action with the right trigger. One person who owns the container. | Two triggers on one action, a stale container version, a trigger on page load instead of the confirmation. |
| GA4 key event import | Whatever GA4 already measures, credited to Google Ads by click ID. | Linked accounts, auto-tagging on, a Marketer role in GA4 and admin in Google Ads, and a site that does not strip the GCLID. | The same action imported and also tagged directly, which double counts. GA4's cookie lasts up to two years, Google Ads' window is 1 to 90 days, so counts differ by design. |
| Enhanced conversions | Browser events plus hashed first-party data: email, name, address, phone. | The data present on the conversion page or form, normalised and SHA-256 hashed before it leaves. The leads variant pairs with offline import. | Fields missing on the page, a variable that captures a label instead of the value, hashing done twice. |
| Offline conversion import | Deals that closed in the CRM, credited back to the click that started them. | The GCLID stored with each lead, uploaded with the exact case. New actions need 4 to 6 hours before the first upload. File and API imports pull from 90 days back; Salesforce and HubSpot start with 14 days. | A form that never captured the GCLID, an upload outside the window, a CRM stage that never fires. |
The details come from Google's pages on importing GA4 key events, enhanced conversions and offline conversions by GCLID. One rule holds across all five: one setup per conversion action. The moment a purchase is both tagged on the page and imported from GA4, every purchase is two purchases, and smart bidding starts paying for demand that does not exist.
What breaks, and in which direction
Counting setting. Google's guidance is one sentence: select Every for sales to track each purchase and One for leads to prevent duplicate counts from page refreshes. A lead form set to Every over-reports every time someone refreshes the thank-you page. A purchase set to One under-reports every repeat buyer. Both are one dropdown.
Duplicate actions. Over-reports. The same outcome tagged directly and imported from GA4, or two Tag Manager triggers on one confirmation. The Conversions list shows it in thirty seconds if anyone looks.
Consent and blockers. Under-reports. A declined banner or a content blocker stops the tag. With consent mode, Google uses the consent pings to model the gap; its page separates a basic implementation, which gets a general model, from an advanced one, which gets an advertiser-specific model. A tag that never loads sends no ping and gets no model.
The click ID. Under-reports, silently. Google says the GCLID must not be altered or dropped by your website, for example by redirects, because it is what ties a conversion back to the ad. A redirect from http to https, from a vanity path, or through a consent gateway can strip it. Everything downstream, GA4 import and offline upload alike, then has nothing to match on.
Value and currency. Misreports. The purchase fires with no value, or with the cart subtotal before discount, or with the same hard-coded value on every order. Target ROAS bidding then optimises for a number that is not revenue.
Windows. Not a break, but a reason counts differ. Google Ads cookies expire 90 days after a click and the conversion window can be set between 1 and 90 days, while GA4's cookie lasts up to two years. Same action, different memories.
The diagnostic, in order
| Step | What to do |
|---|---|
| 1. Count the actions | Open Conversions. Every action, its source, its counting setting, its status. Two actions for one outcome is the first thing to fix. |
| 2. Fire one test yourself | Complete a purchase or a form with the network tab open. Watch for the Google Ads request. Refresh the thank-you page and watch whether it fires again. |
| 3. Compare to the order of record | Same seven days: conversions in Google Ads against orders in the store or leads in the CRM. Note the ratio, not the difference. |
| 4. Check the click ID survives | Click your own ad, follow every redirect, read the final URL. If the gclid parameter is gone, imports and GA4 attribution are blind. |
| 5. Check consent and the blockers | Load the site with consent declined, then with a content blocker. See which tags still fire. Consent mode models the gap; a missing tag does not. |
| 6. Read the value | Purchases should carry the order value and currency. A conversion with no value, or the same value on every row, is a snippet reading the wrong variable. |
Step three is the one people skip and the one that matters. A ratio of reported conversions to real orders, over the same seven days, is a single number you can watch week to week. It does not need to be 1.0. It needs to be stable and explained.
When to pause automated bidding
Another r/PPC thread framed the harder question well: a tracking problem is not always a total outage. One browser, consent state, import job, region or conversion action can fail while the platform still receives enough events to look healthy. What threshold makes you pause automated bidding, switch to a safer strategy, or keep running while the tracking is repaired?
My answer is the ratio from step three. Smart bidding learns from the conversions that arrive. If a third of them stop arriving, it reads that as demand falling and bids down. If a duplicate action doubles them, it reads that as demand rising and bids up. In both cases it is responding correctly to wrong data. So the rule is: when the ratio moves and you cannot name the cause within a day, move the affected campaigns off the conversion-based strategy, to manual CPC or a target you set by hand, until the cause is named and fixed. Then give the repaired action a clean window before you hand control back.
This is the same discipline as the Meta pixel and Conversions API reconciliation, and the same reason the attribution model argument is usually a tracking argument in disguise. Run the Attribution Leak Calculator on last month first. If the gap is large, closing it is the week-one baseline of the Growth Pilot, measured on match rate and attributed revenue before and after, so the two experiment cards run against numbers you can trust.
Questions
What is Google Ads conversion tracking?
The system that tells Google Ads which valuable actions happened after an ad interaction. Google defines a conversion action as a specific customer activity that is valuable to your business, and lists four sources: website actions, app actions, phone calls, and offline conversions uploaded from files or APIs. Without it, campaigns are optimising for clicks, because clicks are all the platform can see.
Should I use the Google Ads tag or import from GA4?
Pick one per action. A direct tag gives Google Ads its own record, including value and enhanced conversions data. A GA4 import reuses what GA4 measures and keeps one definition across both tools, but Google Ads' conversion window runs 1 to 90 days while GA4's cookie lasts up to two years, so the counts will not match. Tagging an action directly and importing it too is the most common cause of doubled purchases I see.
Every or One: which counting setting?
Google's guidance is to select Every for sales, so each purchase counts, and One for leads, to prevent duplicate counts from page refreshes. A lead action set to Every will count a refresh of the thank-you page as a second lead. A purchase action set to One will hide a repeat customer.
What are enhanced conversions?
A way to send hashed first-party data with the conversion so Google can match it to a signed-in account when the cookie is missing. Google accepts email, name, home address and phone, normalised and hashed with SHA-256 before it leaves the page. Enhanced conversions for web improves online sale measurement; enhanced conversions for leads pairs website leads with offline conversions you import later.
How do offline conversions work?
Your site stores the Google Click ID with each lead. When the deal closes, you upload the GCLID and the conversion time and value, by file, API or a connector. Google says to wait 4 to 6 hours after creating the action before the first upload, that the GCLID is case sensitive, and that file and storage imports pull the last 90 days on every run while Salesforce and HubSpot connectors start with 14 days and then import changes.
What does consent mode do for conversion tracking?
When a visitor declines, the tag sends consent pings instead of full data, and Google uses those pings to model the missing conversions. Google's page distinguishes the basic implementation, which gets a general model, from the advanced one, which gets an advertiser-specific model. Modelled conversions fill a gap; they do not replace a tag that never loaded.
When is tracking too incomplete to keep automated bidding running?
When the ratio between reported conversions and real orders moves suddenly, or when one conversion action stops while the rest look healthy. Smart bidding learns from whatever conversions arrive. If a third of them vanish for a week, it bids as if demand fell. If a duplicate action doubles them, it bids as if demand doubled. Watch the ratio, and when it moves and you cannot explain it, switch the affected campaigns to a manual or target-based strategy until the tag is fixed.
How do I check my own setup in ten minutes?
Run the Attribution Leak Calculator with last month's spend, reported conversions and real orders. Then open Conversions in Google Ads and count how many actions point at the same outcome. Then complete one test conversion with the network tab open and refresh the confirmation page. Those three steps find most of what I get called in for.
Related guides
Google Ads conversions do not match the orders?
Thirty minutes to find which direction the gap runs and what is causing it.