How do I know if my conversion tracking is broken?
Common signs of broken conversion tracking include: conversion volumes that seem too low compared to your actual sales or leads, all conversions attributed to "direct" traffic despite running paid campaigns, Google Ads Smart Bidding in permanent learning mode or "limited by conversion data" warnings, Revenue in GA4 that does not match your order management system, and zero conversions recorded for certain payment methods (PayPal, Apple Pay, Klarna).
What are the most common causes of missing conversions?
The most common causes are: thank-you page URL changing so the conversion trigger no longer matches; cross-domain tracking break between your website and checkout domain; payment gateway redirect not returning users to your confirmation page; ad blockers preventing the tracking tag from firing; incorrect trigger conditions excluding mobile or certain browsers; and conversion tags firing only when the GTM snippet loads (missing cases where GTM is blocked).
What causes duplicate conversions in Google Ads?
Duplicate conversions are most often caused by: multiple GTM containers or tags firing the same conversion action; a conversion tag firing on both the thank-you page load and a button click on the same page; the thank-you page being refreshed by the user (recording the purchase again); both GTM and a hard-coded script (e.g., from a Shopify app) firing the same conversion tag; or a single-page application triggering the purchase event multiple times due to component re-rendering.
Can you fix tracking that was set up by a previous agency?
Yes — this is one of the most common scenarios we handle. Previous agency tracking setups often contain undocumented tags, non-standard implementations, and accumulated issues from multiple campaigns and redesigns. We approach every inherited setup fresh: audit everything, document what exists, identify what is wrong, and implement clean fixes rather than adding patches on top of existing problems.
What is cross-domain tracking and how do I know if mine is broken?
Cross-domain tracking allows GA4 to follow a user's session across multiple domains (e.g., your website and your checkout domain) as a single continuous session with the correct traffic source attribution. If it is broken, GA4 sees each domain crossing as a new direct session — meaning all conversions appear attributed to direct traffic regardless of the actual source. A sign of broken cross-domain tracking is an unusually high proportion of direct conversions in your GA4 reports.
How do you fix conversion tracking on payment gateways that redirect externally?
For payment gateways that send users off-site (PayPal, Stripe checkout, external booking systems), we implement one or more of: cross-domain tracking (if the gateway supports the linker parameter), server-side conversion events via the Measurement Protocol triggered by your payment platform's webhook, or offline conversion import from your order management system. The right approach depends on what data your payment gateway provides post-purchase.
What is the difference between GTM debugging and GA4 debugging?
GTM debugging (using GTM Preview mode) shows you which tags fired, which triggers activated, and what variable values were at the time of firing — in the browser, on your website. GA4 debugging (using GA4 DebugView) shows you which events GA4 actually received from GTM or other sources — after the data has been sent to and processed by GA4. Both are needed to diagnose conversion tracking issues, as a problem could exist in GTM (tag not firing) or in the GA4 data pipeline (tag fires but event not received).
How do you fix tracking on single-page applications (SPAs)?
Single-page applications built in React, Vue.js, or Angular present specific tracking challenges because page navigation does not trigger a full browser reload — standard pageview triggers in GTM do not fire. We implement virtual pageview tracking using GTM's History Change trigger (for hash-based routing) or custom data layer pushes (for pushState navigation), and adjust all event triggers to account for the SPA's lifecycle correctly.
What is the GTM Preview mode and how does it help diagnose tracking issues?
GTM Preview mode is a debugging tool that activates a debug panel on your website, showing in real time which tags fired, which triggers activated, what variables evaluated to, and the complete data layer history — without affecting real visitors. It is the first tool we use when diagnosing any tracking issue, as it allows us to precisely trace what GTM does (or does not do) in response to any user interaction.
After you fix my tracking, how do I ensure it stays working?
We provide a written summary of every fix applied and a list of the specific scenarios tested (payment methods, devices, browsers). For ongoing stability, we recommend: version-controlling your GTM container (creating named versions before any changes), testing any new GTM deployments in Preview mode before publishing, monitoring conversion volumes in Google Ads weekly for unexpected drops, and scheduling a quarterly tracking health check.