Tracking doesn’t fail loudly. Tags break in site updates, pixels double-fire, consent gets displayed but never enforced. The reports keep showing normal-looking numbers the whole time. A website tracking audit is how you find out what your tags are actually doing. Here are the warning signs, what to check, and how to run one, manually or automatically in two minutes.
Suspect something’s broken? Tracking Auditor audits your live GA4 and GTM and grades the setup A–F. Your first audit is free.
Run a free audit →If any of these look familiar, you don’t have a reporting question. You have a tracking problem.
Orders keep coming in, yet analytics shows a conversion cliff. A trigger broke, usually after a site update nobody connected to tracking.
More than a ~5–10% gap between GA4 and your backend means duplicated or missing purchase events, not 'attribution differences'.
Almost always duplicate tracking: two tags with the same measurement ID counting every visit twice.
Broken UTM handling, a consent setup stripping attribution, or a redirect eating campaign parameters.
Some disagreement is normal. A 2x disagreement means one side's tracking is wrong, and you're bidding on it.
The most common compliance failure: consent is displayed but never actually enforced. Legal exposure plus polluted data in one finding.
Six areas, from the tags on the page to the container behind them. Tag auditing (the container review) is where most of the findings live.
Inventory what's installed (analytics, ad pixels, heatmaps, chat widgets) and confirm the pages that matter most actually carry them: checkout, thank-you, lead forms. Tracking gaps cluster on the pages where they cost the most.
Watch a fresh session in DevTools: what fires before the consent banner, after acceptance, after rejection. Tags that ignore the banner are the finding that turns a tracking audit into a compliance issue.
Two Google tags with one measurement ID, the same pixel hard-coded and in GTM, a purchase event pushed by both the theme and a plugin. Duplication inflates everything and is invisible in reports. The numbers just look good.
For each conversion, trigger the real action and follow it: dataLayer push, tag manager trigger, tag fire, event in the platform. A chain is only as reliable as its least-documented link.
A purchase tag that fires with no value, the wrong currency, or a missing transaction ID 'works' in a tag assistant and still corrupts every report and bidding algorithm downstream.
Paused consent tags, leftover staging pixels, Universal Analytics remnants, triggers referencing pages that no longer exist. Container hygiene predicts data quality.
The five-step version. For the full GA4-and-GTM walkthrough, see the complete Google Analytics audit guide; for the wider picture of what an audit covers, see the analytics audit, explained.
Audit the purchase or lead-conversion path first, not the homepage. A broken pageview costs little; a broken purchase event misdirects budget daily.
Private window, DevTools Network tab open, filter for your tag domains. Walk the conversion path as a real user, first accepting consent, then again rejecting it.
Pull a week of orders or leads from the backend and the same window from analytics. The size and direction of the gap tells you what kind of problem you have.
Inventory tags, triggers and variables in GTM. Flag duplicates, paused consent tags, anything pointing at dev/staging, and anything nobody can explain.
Consent enforcement and broken conversions first, duplicates second, hygiene last. Then re-test the same paths to confirm the fixes actually shipped.
Before a full audit, the free Google Analytics checker gives you a quick read on a GA4 setup, and the sample report shows exactly what a complete scored audit looks like. A different problem worth knowing about: if you can’t audit the container because you’ve lost access to the GTM account, the free GTM Inspector reads the live public container so you can recover your setup and rebuild.
A website tracking audit checks that every tag and pixel on your site fires correctly, respects visitor consent, and reports accurate data. It covers the tag manager container, analytics configuration, cookies, and each conversion event end to end.
Open your site in a private window with browser DevTools' Network tab open, filtered to domains like google-analytics.com and googletagmanager.com. Walk your conversion path and confirm each expected event fires once, after consent, with the right values. Then compare a week of analytics conversions against your order system.
Tag auditing is the tag-manager-focused part of a tracking audit: reviewing every tag, trigger and variable in the container for duplicates, dead weight, missing consent settings, and legacy tags that should have been removed. It's where most tracking problems are found and fixed.
After every significant site change (redesigns, checkout changes, new consent banners, platform migrations) and at least annually otherwise. Tracking breaks without warning, so the audit is the alerting.
Yes. Tracking Auditor connects read-only to your GA4 property and GTM container and runs the full audit (consent enforcement, duplicate detection, event quality, cookie classification and conversion integrity) in about two minutes, scored A-F with a prioritised fix plan.
Connect GA4 and GTM read-only and get the full tracking audit: consent enforcement, duplicates, event quality, cookies and conversion integrity, scored A–F with a prioritised fix plan. Your first audit is free, no card required.
Run your free audit