CONVERSION TRACKING QA

Your Conversion Data Might Be Lying — Most Accounts Have Errors You Haven't Found

Post-iOS 14, most US advertisers set up Meta's Conversions API to recover lost signal — but CAPI implementations are rarely complete. The two most common states: CAPI sending events that aren't being deduplicated against the Pixel, doubling reported conversions; or CAPI set up in Events Manager but not actually sending purchase events. Meanwhile, GA4 key events imported into Google Ads create a separate set of duplicates alongside natively tagged conversion actions. This QA audit finds every error across your full tracking stack.

Request a Tracking QA → View the evidence →
5-day turnaround · Written QA report · Every issue rated by severity · No retainer required
This is for you if

This QA is for US businesses that have tracking in place across Google, Meta, and GA4 but can't reconcile the numbers between platforms

The performance marketing lead whose Meta ROAS doesn't match revenue — You know iOS 14 changed Meta's reporting. You may have CAPI running. But when you compare your Meta-reported purchase conversions to your actual revenue for the same period, the gap is larger than normal attribution variance explains. The most likely causes are CAPI deduplication errors causing double-reporting, view-through attribution inflating the conversion count, or purchase value parameters not passing correctly. The QA identifies which.

The DTC or e-commerce brand that imported GA4 conversions into Google Ads and noticed the numbers change — You set up GA4, marked purchase and lead events as key events, and imported them into Google Ads as conversion actions. Shortly after, reported conversion volume increased — but actual orders did not. The import created a second conversion source running alongside your existing Google Ads native tags. Both are counting the same events. Smart Bidding is now optimising on inflated data.

The growth or demand gen manager who had tracking set up by an agency and hasn't audited it since — Your tracking setup was configured during an initial agency onboarding — or across multiple agency transitions. What was configured, when, and whether it is still working as intended has not been systematically verified. Given the number of platform updates, site changes, and GTM modifications that typically accumulate over 12–24 months, a QA is the only way to confirm the current state with certainty.

What's broken

The four most common tracking errors we find in US accounts

Meta CAPI deduplication errors post-iOS 14

This is the most prevalent tracking error in US Meta Ads accounts. When CAPI is implemented alongside the browser Pixel without correct deduplication — meaning events sent via CAPI and events sent via Pixel are not being matched by a shared event ID — Meta records each conversion twice: once from the browser and once from the server. The reported conversion count is double the actual figure, and the ROAS number is correspondingly inflated. The opposite problem — CAPI set up but not sending the key Purchase or Lead events — leaves the iOS signal gap unaddressed.

GA4 key event imports creating duplicate conversion actions in Google Ads

When GA4 key events are imported into Google Ads as conversion actions while the account also has native Google Ads conversion tags for the same events, Google Ads counts both independently. The conversion volume Smart Bidding reads is two times the actual figure. This is the most common source of duplicate conversions in accounts that have undergone a GA4 migration without a post-migration tracking review.

Purchase events firing without revenue values

Purchase events that fire without transaction value data — or with hardcoded placeholder values rather than dynamic revenue figures — prevent value-based bidding from functioning in both Google Ads and Meta. For US e-commerce businesses with broad product price ranges and varying order values, the inability to distinguish a $30 order from a $3,000 order means Smart Bidding allocates budget with no regard for margin or revenue contribution.

Form events firing on page load instead of form submit

GTM-based form conversion tags frequently fire on the confirmation page URL loading rather than on a successful form submit action. Every visitor who reaches the confirmation page — including those who navigated there directly, refreshed the page, or were redirected after an incomplete form — is counted as a conversion. In high-traffic US campaigns, this error can inflate lead conversion counts by an order of magnitude.

What we engineer

What the QA covers

Google Ads conversion actions

We audit every active conversion action in your Google Ads account — status, category, counting method, value settings, attribution window, and whether GA4-imported conversions are running alongside native tags for the same events. We identify every source of duplicate counting and confirm which conversion actions are feeding Smart Bidding.

Meta Pixel events and CAPI

We verify the Meta Pixel is firing correct standard events with accurate parameters — value, currency in USD, content IDs where relevant. We check the CAPI implementation specifically: whether it is sending the same events as the Pixel, whether event IDs are being passed from both sources for deduplication matching, and whether Events Manager shows matched events or unmatched parallel signals. We assess which events are being recovered post-iOS 14 and which are not.

GA4 key events

We review GA4 key event configuration, trigger logic, and parameter accuracy — including value, currency, transaction ID, and item data for e-commerce. We identify which GA4 key events are being imported into Google Ads as conversion actions and check whether those imports are running alongside existing native tags for the same actions.

GTM tags and triggers

We conduct a full GTM container audit: every tag, every trigger, every variable. We test each conversion tag in preview mode against its intended user action — purchase confirmation, form submit, button click — and verify it does not fire on unintended conditions. Tags that are paused but not removed, duplicate tags from previous agency setups, and triggers with incorrect conditions are all documented.

Cross-domain tracking

We test whether GA4 and Google Ads tracking correctly maintain session continuity when users move from your main site to a third-party checkout, booking platform, or form tool on a different domain. For US e-commerce, this includes payment platforms such as Stripe, Shopify Payments, and PayPal. Attribution breaks at these handoff points cause purchase conversions to appear as direct or unattributed sessions rather than being credited to the originating ad.

Attribution model configuration

We review the attribution model in use across Google Ads and GA4 and assess whether it reflects your actual customer journey. For US DTC brands with multi-touch journeys across Meta, Google, and email, data-driven attribution typically outperforms last-click. We also check whether Meta's view-through attribution window is configured in a way that inflates contribution relative to actual ad-driven conversions.

Conversion window settings

We verify that conversion window settings are appropriate for your business model and purchase cycle. For short-cycle e-commerce, longer windows import noise into bidding signals. For B2B SaaS or professional services with 30–90 day sales cycles, default 30-day windows routinely miss legitimate late conversions. Both configurations introduce systematic error into Smart Bidding signal quality.

Request a Tracking QA →
What changes

What you receive

Before
After
Before Complete QA report with every issue found
After A written report listing every tracking error found across Google Ads, Meta Pixel and CAPI, GA4, and GTM. Each issue is described precisely — what is wrong, where it is, and what it is affecting — and rated by severity: critical (actively distorting campaign decisions), significant (causing data loss or inflation), or advisory (reduces future risk).
Before Exact fix instructions for each issue
After Every issue in the report includes step-by-step instructions for fixing it. For CAPI deduplication errors, the report specifies the event ID parameter that must be passed from both the browser Pixel and the server-side CAPI payload, and how to verify matching in Events Manager. For GA4 import conflicts, the report identifies which conversion action to disable and how to confirm the remaining source is counting correctly. Implementation can proceed without additional interpretation.
Before Accurate conversion data as a foundation for bidding
After Correcting the errors identified in the QA gives Smart Bidding and Meta's advantage algorithm accurate signals to work from. CAPI deduplication brings Meta conversion counts to their true figure. GA4 import conflicts removed give Google Ads a single, accurate conversion source. Purchase values passing dynamically enable value-based bidding to function. The algorithms can then optimise toward actual business outcomes.
Before A documented tracking baseline for future reference
After The QA produces a written record of your tracking setup in its correct, verified state. When platform updates, site changes, or new GTM containers introduce regressions, you have a specific baseline to check against. Tracking errors caught early cost significantly less than those discovered months after they began affecting bidding performance.
Common questions

FAQ

We have CAPI set up — why would deduplication still be an error?

CAPI deduplication requires that both the browser Pixel and the CAPI server payload send a matching event ID for the same user action. If the event ID is not included in the Pixel's dataLayer push, or is not passed in the CAPI event payload, Meta cannot match the two signals and records them as separate conversions. Having CAPI configured in Events Manager does not confirm that deduplication is working — only that CAPI is connected. The QA tests whether matching event IDs are present in both sources.

We imported GA4 conversions into Google Ads — how do we know if that created a duplicate?

The indicator is a step increase in reported Google Ads conversions in the period following the import, without a corresponding increase in actual leads or orders. To confirm it definitively, you would need to compare the conversion action breakdown in Google Ads — which shows conversions attributed to each source separately — against actual business volume. The QA does this comparison systematically and identifies which conversion actions are duplicating which.

Our CAPI was set up via a third-party tool — Klaviyo, Segment, or our CDP — does that affect the QA?

No. We review the Events Manager event stream regardless of how CAPI events are being sent — whether through a native integration, a customer data platform, or a custom server-side implementation. What matters for the QA is the quality of the signals arriving in Events Manager and whether deduplication is functioning correctly, not the technical route by which events are delivered.

Do you check Meta's attribution window settings as part of the QA?

Yes. Meta's default attribution window includes both click-through and view-through conversions. For US businesses running multi-channel campaigns, view-through attribution causes Meta to claim credit for conversions that were driven by other channels. The QA reviews whether the attribution window is configured appropriately and flags view-through settings that are inflating reported ROAS relative to actual Meta-driven conversions.

What is the difference between a Conversion Tracking QA and a full Paid Ads Audit?

A Conversion Tracking QA is a focused technical check of whether your tracking is recording the right events accurately — CAPI deduplication, GA4 import conflicts, duplicate Google Ads conversion actions, trigger logic errors, and attribution window configuration. A Paid Ads Audit is broader, covering campaign structure, keyword strategy, bidding, creative, and landing pages in addition to tracking. If the specific concern is whether your conversion data can be trusted, the QA addresses that directly. If you want a comprehensive account diagnostic, the Paid Ads Audit includes tracking as one of its five check areas.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

Confirm Whether Your Conversion Data Is Accurate Before Your Next Budget Decision

Five business days. A written QA report. Severity ratings and exact fix instructions for every issue found. If your account has CAPI deduplication errors, GA4 import conflicts creating duplicate conversions, or form triggers firing on page load — this QA will find them and tell you exactly how to correct them. If the setup is clean, you have documentation confirming that.

Request a Tracking QA →

5-day turnaround · Written QA report · Every issue rated by severity · No retainer required