What a tracking audit actually checks (all 13, explained)

TagEasy's free auditor grades any URL out of 100 across 13 checks. Here is what each one looks for and why it matters — so the score means something to you, not just to us.

Detection — is the tracking even there?

• GA4 measurement ID — is a G- ID loading at all?
• GTM container — is a container installed?
• Meta Pixel — is a pixel firing, with a real ID?
• TikTok Pixel — present for stores that spend on TikTok?
• Google Ads conversion — is the AW- conversion tag on the page?

Correctness — is it done right?

• Consent Mode v2 — are the gtag consent defaults present before tags load?
• Single GA4 property — or is more than one GA4 firing and double-counting?
• GTM debug mode — did gtm_preview / gtm_auth params leak to production?
• DataLayer initialised — is the dataLayer set up before GTM reads it?

Hygiene & privacy — is it healthy?

• PII in URL — are emails or phone numbers exposed in tracked URLs?
• Consent banner — did we detect a consent management platform?
• Tracking script weight — how much JS the tracking stack adds to the page.
• HTTPS — are tags loaded securely, with no mixed content?

💡 Note: Each check on a live report has an "Explain in detail" expander that walks the specific finding for your domain. The /benchmarks page shows the pass rate for every check across our corpus, so you can see which ones most sites fail.

Why 13, and why public

Because these are the checks that separate "we have tracking" from "our tracking is correct" — and the gap between those two is where lost orders and wasted ad spend live. Publishing the score turns a silent failure into a visible one. Run it on your own site at /check, then on a competitor's.