CONVERSION TRACKING QA

Your UK Conversion Tracking Is Probably Feeding Smart Bidding the Wrong Numbers

Broken tags, duplicate conversion events, and misconfigured GA4 triggers are endemic across UK paid accounts. When Consent Mode v2 is not implemented correctly, conversions disappear whenever a user declines cookies — and Smart Bidding has no modelled data to fall back on. The result is bidding that optimises against a fraction of actual conversion activity.

Request a Tracking QA → View the evidence →
5-day turnaround · Written QA report · Severity-rated findings · Exact fix instructions · No retainer
This is for you if

Who This Is For

Marketing leads at UK businesses running Google Ads, Meta, or both: Your campaigns are live and converting — or so the platform reports suggest. But the conversion figures across Google Ads, Meta, and GA4 never reconcile, and you have no reliable way to know which number to trust. You need a systematic check of every tag, trigger, and conversion action before you increase spend or restructure bidding strategy.

UK businesses that migrated to GA4 and have not verified tracking since: The migration from Universal Analytics to GA4 introduced conversion tracking gaps in a large proportion of UK accounts. If your GA4 events were not re-verified after the migration, there is a meaningful chance that duplicate events are firing, conversion windows are misconfigured, or key actions are not being tracked at all. Those errors have been feeding your bidding algorithms for months.

E-commerce and lead generation operators preparing to scale paid budgets: You are planning to increase paid spend significantly and you need to know whether the conversion data foundation is sound enough to support that scale. Smart Bidding trained on corrupted data does not improve with more budget — it amplifies the errors. The QA establishes whether tracking is reliable before spend increases.

UK businesses concerned about Consent Mode v2 compliance: The UK post-GDPR advertising landscape requires that conversions are modelled when users decline consent. If Consent Mode v2 is not correctly implemented in your GTM setup, you are losing conversion signal every time a user opts out — and you may be out of compliance with the consent requirements that apply to your business. The QA reviews your Consent Mode implementation as standard.

What's broken

What we find in the majority of UK accounts

Duplicate conversion events inflating reported conversions

Duplicate conversion actions are the most common tracking error we find in UK accounts. The same purchase, form submission, or phone call fires multiple times — once through the Google Ads tag, once through GA4, and sometimes again through a GTM trigger that has never been deactivated from a previous setup. Smart Bidding sees three conversions where one occurred, and every subsequent bidding decision is calibrated against that inflated baseline.

Consent Mode v2 not implemented or misconfigured

Google's Consent Mode v2 is required for advertisers operating in the UK and EEA to model conversions when users decline cookie consent. Many UK accounts have the Consent Mode tag present but incorrectly configured — the consent signals are not being passed correctly, the default consent state is set to "granted" rather than "denied", or the integration between the Consent Management Platform and GTM has broken after a site update. When this happens, modelled conversions are absent and conversion data drops sharply whenever consent rates are low.

GA4 events firing on page load rather than on user action

A significant proportion of UK GA4 setups record conversions when a confirmation or thank-you page loads — not when the underlying transaction completes. This distinction matters when sessions time out, when users navigate back, or when server-side confirmation fails silently. Page-load triggers over-count conversions and produce conversion data that cannot be reconciled with actual CRM or revenue records.

Attribution gaps between Google Ads, Meta, and GA4

UK businesses commonly run Google Ads and Meta with separate reporting cadences and no shared attribution logic. GA4 records one conversion figure, Google Ads reports another, and Meta reports a third — and none of them agree. Without a clear view of which conversions are being double-counted across platforms and which are being missed entirely, budget allocation decisions are being made against data that cannot be trusted.

What we engineer

What the Conversion Tracking QA covers

Full tag and trigger audit across GTM, Google Ads, Meta, and GA4

We review every tag, trigger, and variable in your GTM container. We check each Google Ads conversion action for correct firing conditions, deduplication logic, and value passing. We verify Meta Pixel and Conversions API implementation against actual transaction data. GA4 events are audited against the measurement plan to confirm that every conversion action is firing once per genuine user action, with the correct parameters.

Consent Mode v2 compliance review

We verify that your Consent Mode v2 implementation is passing the correct consent signals to Google. This includes checking the default consent state configuration, verifying that your Consent Management Platform is correctly integrated with GTM, and confirming that consent signals update dynamically when users interact with your cookie banner. Where Consent Mode is absent or misconfigured, we document the exact fix required.

Duplicate event identification and deduplication

We map every conversion action across all platforms against a single source of truth — typically GA4 or your CRM — and identify where the same user action is being counted multiple times. Duplicates are documented with the specific tag or trigger responsible, a severity rating, and the exact steps required to resolve them without disrupting existing conversion history.

Attribution gap analysis across Google Ads, Meta, and GA4

We pull conversion figures from each platform for the same time period and reconcile them against each other. Where figures diverge materially, we identify the cause — whether that is cross-channel double-counting, modelled versus observed conversions, or differences in attribution window configuration — and document what an accurate conversion picture looks like when the gaps are corrected.

Missing conversion actions

We review the full customer journey across your site and paid campaigns to identify conversion actions that should be tracked but are not. For UK lead generation accounts, this typically includes phone call conversions from Google Ads call extensions and form submissions on subsidiary pages. For e-commerce, it includes add-to-basket, checkout initiation, and purchase events that may be absent from the conversion action set.

Request a Tracking QA →
Common questions

FAQ

What does the Conversion Tracking QA cover?

The QA audits every conversion action across Google Ads, Meta Ads, GA4, and GTM — checking for broken tags, duplicate events, missing conversions, incorrect trigger conditions, and attribution gaps between platforms. For UK accounts, Consent Mode v2 implementation is reviewed as standard. You receive a written report with severity ratings and exact fix instructions for every issue found.

How long does the QA take?

The report is delivered within 5 business days of receiving access to your GTM container, Google Ads, Meta Business Manager, and GA4 property. If access to any platform is delayed, we communicate the impact on the timeline immediately. Most UK QA engagements are delivered within the 5-day window without issue.

Does the QA include Consent Mode v2?

Yes. Consent Mode v2 compliance is included as standard in the UK Conversion Tracking QA. We verify whether your consent signals are being passed correctly from your Consent Management Platform through GTM to the Google tag, check the default consent state configuration, and confirm that conversions are being modelled when users decline consent. Where Consent Mode is absent or misconfigured, the fix instructions are included in the report.

We already have an agency managing our GTM and tracking. Is the QA still relevant?

Yes. Many UK clients commission the QA specifically because they want an independent verification of tracking that their agency set up. The QA is not a judgement of your agency's competence — it is a systematic check of what the tracking currently does, regardless of who built it. Several common tracking errors are introduced during GA4 migrations or site updates and are easily missed in ongoing management.

What if we have never run a tracking audit before?

That is the most common situation. The QA does not require any prior audit history. We review the current state of your tracking from scratch and document every issue we find, regardless of when it was introduced. For accounts that have never been audited, the findings are typically more significant — but so is the improvement in data quality after the fixes are applied.

Start here

Find out what your conversion tracking is actually reporting

The QA takes 5 business days and requires no ongoing commitment. You receive a written report that documents every broken tag, duplicate event, attribution gap, and Consent Mode compliance issue — with a severity rating and exact fix instructions for each one. Whether your team or agency implements the fixes, you will be making bidding and budget decisions based on conversion data you can trust.

Request a Tracking QA →

5-day turnaround · Severity-rated findings · Consent Mode v2 compliance included · No retainer