Analytics breaking? Stop finding out from a client
Lead Recorder's one-line script tag guarantees zero lost lead attribution — no separate pixel debugging required.
Try Lead Recorder free“It's installed” and “it's working” are different claims
Placement decides what gets missed
A tag added lower in the page, or injected late by another plugin, can miss early page views and above-the-fold clicks — the exact moments a fast-bouncing visitor generates.
Site rebuilds silently drop snippets
A theme change, page builder migration, or a well-meaning "cleanup" of the header often takes tracking scripts out with it. Nothing errors. The data just quietly stops.
Nobody checks until a report looks wrong
Broken tracking doesn't page anyone. It shows up weeks later as an unexplained dip in conversions, once there's no way to recover the lost data.
Read why tracking scripts silently break, and how to catch it sooner →
Script checker, explained
What does this tool actually check?
It fetches the live HTML of the URL you enter — the same way a browser would on first load — and scans it for the script signatures of Google Tag Manager, Google Analytics 4, Meta Pixel, and the Lead Recorder snippet. For each one it reports whether it was found, and whether it's placed in <head> or lower down the page.
Why does it matter whether a script is in <head>?
Google's own Tag Manager documentation recommends placing the container snippet as high in <head> as possible, so it can start listening before anything else on the page loads. A script placed lower, or injected late by another plugin, can miss early events — page views on a fast bounce, clicks on above-the-fold buttons — before it's even registered.
Will this see tags that only load after someone accepts a cookie banner?
No, and that's expected. If your consent management platform correctly blocks tags until a visitor accepts cookies, a plain HTML fetch won't see them either — the tool isn't clicking "accept" on your behalf. That's correct, compliant behaviour, not a false negative on our end.
What about single-page apps that inject tags with JavaScript?
This scans the initial server-rendered HTML, not the fully hydrated, client-side-rendered page. If your site is a React, Vue, or similar SPA that injects tracking tags purely via client-side JavaScript after load, this tool may not see them even though they work fine in a real browser. Treat a "not detected" result on a JS-heavy site as a prompt to double-check manually, not a definite failure.
Do you store the sites I scan?
No. The HTML is fetched, scanned in memory, and discarded — nothing is saved on our servers. The "recent scans" list you see is saved to your own browser's local storage only.
Why did my scan fail or time out?
Some sites block automated requests behind bot protection (Cloudflare, WAFs) or take too long to respond within our request window. A failed scan usually means the site refused or was too slow to answer — not necessarily that anything is wrong with its tracking setup.
One scan tells you it's broken.
Lead Recorder tells you the moment it happens.
A single script tag captures every visitor's source and ties it straight to the lead — no separate pixel to babysit, no silent gaps to discover later.
Free plan available · No credit card required