Free Tracking Audit
Find out what your analytics and advertising tags are actually doing. We read your page and your Tag Manager container, then report what is really configured — duplicate pixels, deprecated properties, and consent problems included.
A scan takes a few seconds. Five free scans per hour.
Why we built this
Tracking defects are the most common serious problem we find, and they are the most consequential, because every optimization decision downstream inherits the error. A site can spend a year optimizing against a purchase count that is fifteen percent too high and never know it.
Most free pixel checkers scan the HTML source. That was a reasonable approach a decade ago. Today nearly every tag is injected at runtime by a tag manager, so a source scan reports almost nothing useful. We go one step further and read the tag manager container itself, which is where the real configuration lives.
We are also deliberate about what we claim. Every finding is labelled with how we know it, and anything we could not verify does not count against your grade. A tool that cries wolf on a well-built site is worse than no tool.
What a scanner cannot do is reconcile your reported revenue against your order system, or tell you where in the funnel real users give up. That is the work — and it is where the money is.
Frequently asked questions
- How does the tracking audit tool work?
- We fetch your page and then read the configuration of your Google Tag Manager container directly. That second step matters: almost every tag on a modern site is injected at runtime, so the usual approach of scanning HTML source finds almost nothing. Reading the container tells us which GA4 properties, Meta pixels, and Google Ads conversion actions are configured, without needing to execute anything.
- What can this tool detect?
- Which analytics and advertising platforms are set up, duplicate measurement IDs, pixel IDs, or containers, deprecated Universal Analytics properties that are still configured, Consent Mode configuration, whether a data layer exists, and third-party script weight. Every finding is labelled with how we know it — observed firing, configured but not observed, or unverified.
- What can it not detect?
- It cannot confirm that your reported revenue reconciles with your order system, whether conversions are being double-counted across browser and server, or where in the funnel real users give up. Those need account access. The reconciliation check in particular is the single most valuable thing in a tracking audit, and it is what our free manual audit covers.
- Why does the report say 'configured, not observed'?
- Because we want you to be able to tell the difference. A tag that is configured in your container is not the same as a tag that fires correctly on a real page load, and a scanner that blurs the two produces confident findings that turn out to be wrong. Anything we did not watch happen is labelled as such, and unverified findings do not count against your grade.
- Is it really free?
- Yes, five scans per hour with no signup. We built it because tracking defects are the most common problem we find, and showing you one is a better introduction than a sales call.
- Why did the scan fail on my site?
- Most commonly a bot-protection layer such as Cloudflare Bot Management blocking automated requests. Sites behind a login cannot be scanned either. If your site blocks us, the manual audit is unaffected — we work from your accounts rather than from the outside.