CONVERSION TRACKING QA

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

Australian Shopify businesses running Google Ads are among the most affected by a specific and widespread tracking error: Shopify's native Google Ads integration and a separate GTM purchase tag fire simultaneously, counting every sale twice. That double-counted data feeds Smart Bidding, inflates reported ROAS, and causes the algorithm to make systematically wrong decisions. This QA audit finds that error and every other like it 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 Australian businesses that have conversion tracking in place but can't fully trust what it's reporting

The Shopify store owner running Google Ads with both native integration and GTM active — You connected your Shopify store to Google Ads through the Google channel app and also have Google Tag Manager installed with a purchase conversion tag. Both are firing. Your reported conversion volume is roughly double your actual order count, your ROAS looks strong, and your Smart Bidding campaigns are optimising toward a signal that bears no relationship to real revenue. The QA will confirm whether this is happening and tell you exactly how to resolve it.

The marketing manager who migrated from Universal Analytics to GA4 and hasn't checked conversion mapping since — The migration from UA to GA4 involved setting up new key events, updating GTM triggers, and reconfiguring Google Ads to import from GA4 instead of UA. These migrations introduce a predictable set of tracking errors — events double-counted during the transition period, old conversion actions left active alongside new ones, and trigger logic that worked in UA not correctly replicated in GA4. If this migration happened in your account and was not followed by a systematic QA, there is a high probability of residual errors.

The performance marketing lead whose Meta ROAS figures don't reconcile with Shopify revenue — Your Meta Ads account reports strong purchase ROAS. Your Shopify analytics show a different number for the same period. The gap is consistent enough to indicate a systematic error rather than normal attribution variance. The most common cause is Meta counting view-through conversions alongside click-through ones, or the Pixel firing multiple purchase events per transaction. The QA identifies which.

What's broken

The four most common tracking errors we find in Australian accounts

Shopify native Google Ads integration and GTM both firing purchase events

This is the single most common tracking error in Australian e-commerce accounts. Shopify's Google channel integration fires a purchase conversion directly to Google Ads. If GTM is also installed with its own purchase tag — which most accounts set up for additional tracking control — both fire on the same order confirmation page. The result is a purchase conversion count that is consistently twice the actual order volume, and a ROAS figure that Smart Bidding treats as accurate.

Duplicate conversion events inflating counts by 2–3x

Beyond the Shopify-specific scenario, duplicate conversion events occur wherever both a native Google Ads tag and a GA4-imported conversion are active for the same action. In accounts running both mechanisms, every conversion is counted twice. This compounds with the Shopify issue in accounts where all three sources — Shopify native, GTM, and GA4 import — are active simultaneously.

Purchase events firing without revenue values

A purchase event that sends a conversion signal without a corresponding transaction value removes the information Smart Bidding needs to distinguish a high-value order from a low-value one. For Australian e-commerce businesses with a wide product price range, this means the algorithm optimises for order volume regardless of margin. Revenue-based bidding cannot function until this is corrected.

Form events firing on page load instead of form submit

Lead generation businesses running Google Ads or Meta Ads in Australia frequently have this error in their GTM setup. The trigger fires when the confirmation page loads rather than when the form is successfully submitted — meaning every visitor who reaches the confirmation URL is recorded as a converted lead, including those who navigated there directly or refreshed the page. Reported CPL figures in affected accounts can be less than half the actual cost.

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, attribution window, and value settings. We specifically check for the Shopify native integration conflict — whether the Google channel app and GTM are both sending purchase signals — and identify any GA4-imported conversion actions that are running alongside natively tagged events.

Meta Pixel events

We verify that the Meta Pixel is firing the correct standard events with the correct parameters — including value, currency in AUD, and content IDs for product catalogue campaigns. We check for duplicate event fires within a single page session and verify that deduplication is correctly configured where both the Pixel and Conversions API are in use.

GA4 key events

We review which events are marked as key events in GA4, verify trigger logic for each, and check that parameters including value, currency, transaction ID, and item data are passing correctly. We identify any GA4 key events being imported into Google Ads that duplicate existing conversion tags.

GTM tags and triggers

We conduct a full GTM container audit: every tag, every trigger, and every variable in the container. We run each conversion tag in preview mode against the actual pages and user actions it is meant to track — purchase, form submit, button click, phone call. Tags that fire on unintended conditions are documented and flagged for correction or removal.

Cross-domain tracking

We test whether GA4 and Google Ads tracking correctly maintain session continuity when users move from your main site to a payment gateway — Afterpay, Stripe, PayPal, Zip — and back. Cross-domain attribution breaks at payment handoff are the most common cause of purchase conversions appearing as direct sessions rather than being attributed to the originating ad.

Attribution model configuration

We review whether the attribution model in use across Google Ads and GA4 is appropriate for your business and customer journey length. For Australian retail businesses with short purchase cycles, data-driven attribution typically outperforms last-click. For B2B businesses with longer cycles, the model configuration requires more deliberate calibration.

Conversion window settings

We verify that conversion window settings match your typical time-to-conversion. For Australian e-commerce, a 30-day click conversion window is often appropriate; for considered purchases or B2B lead generation, longer windows may be justified. Windows that are too short miss legitimate conversions; windows that are too long import noise into bidding signals.

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, GA4, and GTM. Each issue is described precisely — what is wrong, where it is, what it is affecting — and rated by severity: critical (actively distorting campaign decisions), significant (causing data loss or inflation), and advisory (an improvement that reduces future risk).

Before Exact fix instructions for each issue

After Every issue in the report is accompanied by step-by-step instructions for fixing it. For the Shopify native integration conflict, the report specifies which integration source to disable and how to verify the remaining tag is firing correctly. For GTM trigger errors, the corrected trigger configuration is specified. No ambiguity, no further interpretation required.

Before Accurate conversion data as a foundation for bidding

After Correcting the errors identified in the QA removes the false signals distorting your Smart Bidding and Meta advantage campaigns. Reported conversion volume reflects actual orders and leads. ROAS figures are calculable from real revenue. Budget allocation decisions can be made from data that corresponds to business reality.

Before A documented tracking baseline for future reference

After The QA produces a written record of your tracking setup in its correct state. When a site update, a new campaign, or a GTM change introduces a regression, you have a baseline to check against. Tracking errors caught quickly cost less than errors discovered months after the fact.

Common questions

FAQ

We use Shopify — is the native Google Ads integration the same as a GTM tag?

They are two separate tracking mechanisms that both write to your Google Ads conversion data. Shopify's Google channel app sends a purchase conversion directly from Shopify's servers when an order is placed. A GTM purchase tag fires from the browser on the order confirmation page. If both are active, both conversions are recorded and counted independently by Google Ads — the platform has no automatic deduplication between them.

How do we know if our tracking is currently double-counting?

The QA process tests for this directly. In the meantime, a useful indicator is comparing your Google Ads reported conversion volume against your actual order count or lead count in the same period. If reported conversions are consistently 1.5× to 3× your actual business volume, double-counting is highly likely. The QA confirms whether this is the case and identifies the specific source.

We migrated from Universal Analytics to GA4 last year — could there still be errors from that migration?

Yes. GA4 migrations frequently leave residual tracking issues: old UA-based Google Ads conversion actions that remain active alongside new GA4-imported ones, trigger logic that was rebuilt with different conditions than the original UA configuration, and custom dimensions or parameters that were not correctly remapped. These errors persist indefinitely unless a systematic check is done post-migration.

Does the QA cover Meta Conversions API as well as the Pixel?

Yes. Where CAPI is in use alongside the browser Pixel, we check that deduplication is correctly configured — meaning events sent via CAPI and events sent via Pixel for the same user action are matched and not double-reported in Meta Events Manager. Incorrectly configured CAPI deduplication is one of the most common causes of inflated Meta conversion data.

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. A Paid Ads Audit is broader — covering campaign structure, keyword strategy, bidding, creative, and landing pages in addition to tracking. If your primary concern is whether your conversion data can be trusted, start with the QA. 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

Founder — Ecommerce SEO

Keshab Joshi

PPC Expert

Hawrry Bhattarai

Google Ads Expert

Arogya Rijal

SaaS SEO Expert

About Us →

Start here

Know Whether Your Conversion Data Can Be Trusted 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 the Shopify double-counting error, a broken GA4 migration, or a form trigger firing on load instead of submit — this QA will find it. If the setup is clean, you will have documentation confirming that before you scale.

Request a Tracking QA →

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