The tracking audit: what Measurebase checks in your Tag Manager setup
A tagging setup breaks quietly. Someone republishes the web container with the Google Analytics tag pointing straight at Google again, a conversion tag loses its event ID, a plugin pastes a second snippet onto every page, a DNS record changes at the registrar. Nothing errors, data just stops being right. The tracking audit reads your web and server container through the Tag Manager API, visits your site with a real browser, looks at what your domain actually receives, and tells you what is wrong, what could be better and what is in order. Every night, or whenever you queue one.
What it needs from you
Nothing. The audit runs every night for every active domain, on every plan, whether Google Tag Manager is connected or not. Without a connection it works from the site crawl and Measurebase's own request data for your domain; the checks on your web and server container need Tag Manager connected.
Connecting is part of adding a domain, right in the dialog, or can be done later on the domain's settings page: sign in with Google, pick the GTM account and the web and server containers. Measurebase asks for read access to your containers plus edit access limited to its own workspace. Read access in Tag Manager is enough for the audit; applying fixes needs edit rights. You can disconnect at any time.
Does a shop or blog on a subdomain load a container of its own? Add it as an additional web container, for the whole domain or for the subdomains it serves, and the audit reads it as well. Its findings name the container. More on sites like this in one domain, many subdomains.
Want a fresh result after a change? The Run audit now button on the domain's Tracking audit page queues a manual audit, up to five per domain per day.
Nothing is changed in Tag Manager by the audit itself. It reads the published version of each container, your domain's own request log and what the site crawl finds, nothing more. Filling in the measurement setup on the settings page is optional, but worth it: once Measurebase knows which destinations this domain should measure, the audit also checks that each of them is really there.
What gets checked
More than forty checks, grouped by where the problem would live. Each finding names the container, the tag, trigger, variable or client it is about, and what to change.
Routing: does measurement flow through your domain?
- Web container · the Google Analytics tag sends its hits to this domain's tagging host and nowhere else, it is live and has a firing trigger, no measurement ID is configured twice, GA4 event tags send to the property the Google Analytics tag configures, and ecommerce events fire on their data layer events rather than on every page. The audit reads Tag Manager's Destination tags (Google Analytics, Google Ads, Floodlight and Merchant Center) as well as legacy Google tags, and suggests converting a legacy Google tag.
- Server container · the GA4 client that claims the hits exists, the "Google Tag Manager: Web Container" client allows your web container so the site can load it first-party, a live GA4 tag forwards the hits to Google Analytics, the client manages its cookies server-side and migrates the existing JavaScript client ID, default paths are accepted, and server-side Google Ads conversions have their Conversion Linker.
- Backed by traffic · the audit also compares the containers with what your domain actually received: whether GA4 hits arrive at all when the site loads its Google tags, whether the web container is fetched through this domain instead of from googletagmanager.com, whether every Google tag ID the site loads is configured in the published container, and whether every GA4 event tag's event has shown up in the last weeks of hits.
Deduplication: browser and server copies that agree
A platform fed by both a browser pixel and a server-side Conversions API tag counts every conversion twice unless both carry the same event ID. The audit checks that every Meta, TikTok, Snapchat, Pinterest or ChatGPT pixel tag sends one, that your GA4 event tags carry an event_id for the server copies to deduplicate against, and that purchase events carry a transaction_id so GA4 can deduplicate purchases.
Consent: do your tags respect the choice?
Your domain's request log records the Consent Mode state of every GA4 hit, so the audit knows whether visitors actually send consent signals. When they do, it flags marketing tags that require no additional consent and would fire regardless of the choice. When a consent tag is in the container but hardly any hit carries a consent state, it says so. Tags that fire on Consent Initialization without being consent tags are called out too.
Container health
Paused tags and tags without a firing trigger, placeholder values such as G-XXXXXXX left in a field, tags blocked by an exception trigger that always matches, test tags that are live on every page, vendor pixels pasted as custom HTML next to a template tag, Universal Analytics leftovers, and test event codes left in Conversions API tags. On top of that, a tidy-up finding lists the templates, variables and triggers nothing in the container uses, with their names, so you can delete them in one pass.
Measurement setup alignment
With the measurement setup filled in, the audit checks that every destination you enabled has its tag in the live containers. It knows the difference between a GA4 property and the Google Ads configuration, treats server-side Google Ads conversions as complete without a browser conversion tag, and tells you to store a platform's API token first when a server tag cannot exist without it.
The site itself
Not everything lives in Tag Manager. From your domain's request log the audit sees whether your pages load the container with the enhanced tracking script rather than the standard snippet, whether that script loads the container you linked, whether a snippet is on the page twice, and whether page views are sent twice because a page runs twice. With the ad-block guard switched on, it checks that page views really arrive through the masked relay. And it looks outward: the DNS record for your tagging host points at Measurebase, and the host answers HTTPS with a valid certificate that is not about to expire.
The site crawl: what loads outside Tag Manager
Not every tag lives in your containers. As part of every audit, a real browser visits your site's pages and lists every script and pixel that loads outside Google Tag Manager: hardcoded pixels such as Meta or TikTok, Shopify app pixels, consent banners and whether tracking waits for consent, and tag gateways. It recognizes more than 230 vendors, so a pixel someone pasted into the theme years ago shows up by name.
Measurement hits are blocked inside that browser. The crawl never sends data to your analytics or ad platforms, and its visits never show up in your reports. It is on by default, and you can switch it off per domain.
Errors, warnings, info and passed checks
- Errors break measurement. The moment an audit finds one, the domain's audit alert opens: it is in the alert bell, on the Alerts page, in your email and in Slack if you connected it. The same set of errors tomorrow changes nothing; a different set refreshes the alert; a clean audit resolves it.
- Warnings are probable issues: data that is likely counted twice, a tag that likely never fires, a setting that will cost you later.
- Info findings are optional improvements. An audit with only info findings counts as clean.
- Passed checks are everything the audit looked at and found in order. They are folded away under the findings, so a clean container does not read as a wall of green, but they are there when you want to see what was verified.
The Tag Manager page shows the counts per container and for the site, and every finding opens to the tag, trigger, variable or client it is about, as it was at the moment of the audit.
Four findings have their own article on causes and fixes:
- Tags that fire before consent: how to find and fix them
- Duplicate tracking: hard-coded tags, two containers and double page views
- Google hits that bypass your server container
- Why Safari still caps your cookies at 7 days, even with server-side tagging
Proposed fixes
For many findings Measurebase can propose the change itself: a Google Analytics tag that gets its server_container_url, a legacy Google tag converted in place to a Google Analytics or Google Ads tag, a GTM client that is created, a pixel tag that gets its Unique Event ID, a destination from your measurement setup built from the same templates as the GTM template builder. You tick the changes you want, review them, and apply. Measurebase writes them into a workspace named "Measurebase" in your container and audits that workspace right away, so you see the result before anything goes live.
Measurebase never publishes. You preview and publish in Tag Manager, as you always did, or abandon the workspace if you change your mind. Applied changes stay listed on the Tag Manager page with what happened to each operation.
History and workspace audits
Every audit is kept, with what changed in the containers since the one before: versions published, tags added, clients changed. Before you publish a workspace of your own, you can audit it instead of the published version to see whether the change holds up. Such an audit never replaces the latest one and never opens an alert.
Also from your AI assistant
The Measurebase MCP connector exposes the same audit to Claude, Cursor, ChatGPT and the other clients: read the latest audit, run a new one, list what Measurebase can fix and, with a read and write token, apply the operations you choose. The rules, the limits and the workspace are the same as in the dashboard, so it never publishes either.