NOTE-041 · FIELD NOTE FILED 15 NOV 2026 · REVISED 15 NOV 2026 F-104 F-101 F-402 F-403
What a Google Ads conversion tracking audit should find: actions, counting, value and duplicates.
ABSTRACT — A Google Ads conversion tracking audit should leave you with an action sheet: every conversion action, primary or secondary, counted once or every time, valued or not, fed by one source. Six checks, a finding table, and what the written report should look like.
Baris Asa, Synctag, tracking specialist, London · Last checked: November 2026
A Google Ads conversion tracking audit should leave you with one sheet: every conversion action, whether it is primary or secondary, how it counts, what value it reports, which source feeds it, and a finding against each. Then one test order traced from the site into Google Ads. A list of “recommendations” with no sheet isn’t an audit.I audit Google Ads conversion tracking for UK ecommerce brands and the agencies behind them. I have no partnership or commission with any tool named here. Who does the work, and how to hire for it, is on the Google Ads conversion tracking service page.
This note covers what the audit should find and hand back. If a number is already wrong and you want to know where to look first, start with Google Ads conversions troubleshooting: where to look first. For the wider audit across GA4, GTM and every platform, see what a tracking audit report should hand back.
What does a Google Ads conversion tracking audit check?
Six checks. Each one produces a column in the sheet.
| Check | The question it answers | Where it lives |
|---|---|---|
| 1. Action list | Which actions exist, and which does bidding use? | Goals, Summary |
| 2. Counting | Is a sale counted per sale and a lead per click? | Each action’s settings |
| 3. Value | Does the value match what the order was worth? | Tag or import, then the action |
| 4. Sources | Does one sale arrive from one place? | Tag Assistant, GTM, platform apps |
| 5. Status and window | Is each action firing, and for how long after the click? | Summary status, action settings |
| 6. Agreement | Do Google Ads conversions sit within a normal gap of real orders? | Store or CRM beside Google Ads |
The order matters. Counting and sources explain most “too many conversions” findings; the window and the last check explain most “too few”.
Check 1: which actions exist, and which ones bid?
Open Goals, then Conversions, then Summary. List every action with its source (website, import, call, offline). Then mark each one primary or secondary.
Primary actions are reported in the Conversions column and used for bidding, as long as the goal they belong to is used for bidding. Secondary actions are observe only: they appear in All conversions and don’t drive bidding. The exception is a custom goal, where every action counts for bidding whether it is primary or secondary (Google: primary and secondary actions).
What the audit looks for:
- One primary action per outcome. A purchase from the tag and a purchase imported from GA4 should not both be primary.
- No soft actions as primary with a value. Google’s own discrepancy page lists non-purchase actions set to Primary, especially with values, as a cause of inflated conversions and double counting (Google: data discrepancies). Page views, add to basket and button clicks usually belong in secondary.
- GA4 imports start as secondary. Google sets actions created from Google Analytics to secondary by default to avoid counting the same event twice for bidding, and they can only be made primary inside Google Ads (Google: GA4 key events). If one is primary, someone changed it, deliberately or not. Change history shows who and when.
This is the F-104 check: key events and counting set wrong.
Check 2: does each action count the right way?
Each action has a count setting. Every counts each conversion that follows an ad interaction and suits sales. One counts a single conversion per ad click and suits leads, where a repeat form fill adds little (Google: conversion counting options).
The audit looks for the mismatch in both directions: a lead form set to Every (one person submits twice, two leads) and a sale set to One (a customer buying twice from one click is counted once).
Google says a change to the count setting affects future conversions only and doesn’t rewrite past data. So the audit records the date of any change, and the before and after periods are not compared as if they were one series.
Check 3: is the value right?
For each action, the sheet records whether it carries a value, where the value comes from (tag, import, fixed) and what it contains. The common findings:
- A fixed value on every order, because the tag was set up with a number rather than the order total.
- An order value that includes tax or shipping while the store reports net sales. Neither is wrong; the finding is that nobody chose.
- A value on a lead action that is a guess, sitting beside a purchase action that carries real revenue, both primary.
Value is a long topic of its own: Google Ads conversion value doesn’t match revenue takes it step by step. The audit only records which of these is true for your account.
Check 4: does one sale reach Google Ads from one place?
This is the check people skip, and the one that finds most of the double counting. A sale can be sent by the Google Ads tag, by a GA4 import, by a platform app, and by an old tag nobody removed.
How to test it: make one test purchase with Tag Assistant open and look at the hits for the confirmation page. Two entries for the same conversion suggest a duplicate. Google’s Shopify guidance says the same: conversion tracking set up before installing the Google & YouTube app can count one action twice, and the fix is to remove duplicate tags and disable only the duplicated events in Google Ads, since disabling the others can reduce accuracy (Google Merchant Center: avoid duplicated tracking events).
Two things the audit records on every purchase action:
- A transaction ID is present. If the same conversion action receives a second conversion with the same ID, such as a reloaded confirmation page, the duplicate is rejected. A static or repeated ID does the opposite and can cause heavy undercounting, and IDs starting
GG_are ones Google generated because your tag sent none, so a reload is not protected (Google: transaction ID). - Two test orders carry two different IDs. Google suggests exactly this test.
A transaction ID does not fix two sources sending the same sale under different actions. That is a sources problem, and it is filed as F-101 .
Check 5: is each action firing, and for how long after the click?
On the Summary, the Status column and each action’s settings give the rest of the sheet:
- Status. “No recent conversions” means no paid clicks led to a conversion in the last 7 to 14 days, which isn’t always a tracking error. “Inactive” or “Needs Attention” usually points to a tag problem, such as a tag not found on the site or an enhanced conversions issue (Google: manage conversion goals from the summary).
- Enhanced conversions. One line: is it on for this action, and does the status show a problem? Enhanced conversions send hashed first-party data, such as an email, to supplement an existing conversion (Google: enhanced conversions for web). They don’t dedupe anything. A problem here is F-402 .
- Imports. An action imported from GA4 that has gone quiet is F-403 .
- Window. The default click-through window is 30 days; some sources allow 60 or 90, and Google recommends at least 7. A conversion after the window is not recorded, and a change to the window applies going forward only (Google: conversion windows). The audit notes any window shorter than the real buying cycle, because those sales never appear.
Check 6: do the numbers agree with real orders?
Two numbers for the same month, side by side: Google Ads conversions on the primary purchase action, and orders in the store that came from Google Ads clicks. Google Ads usually sits lower than the store as a whole, because it only credits sales after its own ads, unless duplicates are inflating it. Google lists the reasons the gap exists: conversion delay, count settings, lookback windows, view-through conversions not being in the Conversions column by default, and cross-device conversions being modelled (Google: data discrepancies).
What the audit writes down is a position, not a verdict. Example wording: “Google Ads is X per cent below store orders from paid clicks; explained by the window and the reporting delay.” If nobody can explain the gap, the audit isn’t finished. When the gap is large, the next step is a reconciliation, not another audit: GA4 and Google Ads numbers don’t match.
What does the audit report look like?
One sheet, one trace, one comparison.
The action sheet. One row per conversion action:
| Action | Source | Primary? | Count | Value | Window | Status | Finding | Fix |
|---|---|---|---|---|---|---|---|---|
| Purchase | Website tag | Primary | Every | Order total | 30 days | Active | None | None |
| Purchase (GA4) | GA4 import | Primary | Every | Order total | 30 days | Active | Second primary purchase | Set to secondary |
| Add to basket | Website tag | Primary | Every | Fixed 5 | 30 days | Active | Soft action with a value | Set to secondary, remove value |
Illustrative example, not a client account
The finding in this exhibit is two lines. The same sale arrived twice as a primary action, and a basket click carried a made-up value that bidding treated as revenue. Both lines count towards bidding, so both inflate Conversions. Filed as F-104 .
The test trace. One real or test purchase, followed through: the tag firing in Tag Assistant, the transaction ID on the hit, the conversion in Google Ads after Google’s reporting delay. Every step on record.
The comparison. The two numbers from check 6, with the gap explained.
The change record. What was changed in Google Ads, the tag set-up and any apps, when, and by whom, so each change can be reversed. After a change, Google advises allowing one to two conversion cycles for bidding to adapt (Google: primary and secondary actions). So the audit records the date, and the account isn’t judged until one or two conversion cycles have passed.
What should the audit not do?
- Judge the campaigns. Bids, budgets and creative belong to whoever runs the account. The audit makes the data trustworthy; it doesn’t tell you how to spend.
- Fix things silently. Changing a primary action changes what bidding learns from. Findings are written first, changed after, and dated.
- Promise a number. A clean audit shows what Google Ads is counting. It doesn’t promise more conversions.
Common questions
What should a Google Ads conversion tracking audit check?
Six things: the list of conversion actions and which are primary or secondary, the count setting on each (Every for sales, One for leads), the value each action reports, whether one sale reaches Google Ads from more than one source, the tracking status and conversion window of each action, and whether the numbers agree with the store or CRM. The output is a sheet with one row per action and a finding against each.
What does a Google Ads conversion audit report look like?
A table with one row per conversion action: source, primary or secondary, count setting, value, window, status, finding and fix. It sits beside one test purchase or test lead traced from the site into Google Ads, and a two-number comparison of Google Ads conversions with real orders or leads for the same month.
How do I know if Google Ads is counting the same sale twice?
Look at the Goals Summary (Goals, Conversions, Summary). If two actions for the same sale are both primary, or a tag and an app both send the purchase, the sale is counted twice. Tag Assistant shows two hits for one event. A transaction ID on the tag stops a reloaded confirmation page counting twice, but it does not remove two different sources.
Should the Google Ads audit include enhanced conversions?
Yes, as one line: is it switched on for the action, and does the status show a problem. Enhanced conversions supplement an existing conversion with hashed first-party data. They do not remove duplicates. If the status says Needs attention, fix that before reading anything into the numbers.
Who can audit Google Ads conversion tracking in the UK?
Someone who reads the account, the tag set-up and the store or CRM together. A person who only looks inside Google Ads can’t tell you whether the number matches real orders. Baris Asa (Synctag, London) audits conversion tracking for UK brands and the agencies behind them: Google Ads conversion tracking.
Sources
Read on 15 November 2026:
- Google Ads Help, about primary and secondary conversion actions (primary in the Conversions column and used for bidding when the goal is; secondary observe only; custom goal exception; GA conversions secondary by default, changed only in Google Ads; one to two conversion cycles to adapt)
- Google Ads Help, about conversion counting options (Every suits sales, One suits leads; changes affect future conversions only)
- Google Ads Help, use a transaction ID to minimise duplicate conversions (second conversion with the same ID rejected; static IDs cause undercounting;
GG_prefix; two test purchases) - Google Ads Help, about conversion windows (30-day default click-through window; conversions after the window not recorded; changes apply going forward)
- Google Ads Help, data discrepancies: factors and troubleshooting (conversion delay, count settings, non-purchase primary actions with values, view-through not in Conversions by default, modelled cross-device)
- Google Ads Help, manage conversion goals from the conversions summary (No recent conversions after 7 to 14 days; Inactive and Needs Attention usually a tag or enhanced conversions problem)
- Google Ads Help, create Google Ads conversions from GA4 key events (imports secondary by default to avoid counting the same event twice for bidding)
- Google Ads Help, about enhanced conversions for web (hashed first-party data supplements existing conversions)
- Google Merchant Center Help, how to avoid duplicated tracking events (conversion tracking set up before the Google & YouTube app can count one action twice; Tag Assistant Hits sent; disable only duplicated events)