Tracking Pixel Checker

See which analytics, ad pixels, session replay and chat tags are in a page's source.

What This Tool Does

It loads the page's HTML as the server sends it and looks for the script, iframe, image and link URLs and inline snippets of known analytics, advertising, session replay, chat, marketing automation, A/B testing and monitoring tools. Each one found is listed by vendor and category, with the URL or ID that gave it away. A consent manager in the source is reported too.

What It Does Not See

Many sites load their pixels through a tag manager such as Google Tag Manager. Those tags are added after the page loads and never appear in the source, so this page cannot see them. The SEO Score API's GET /trackers endpoint also loads the page in a real browser and records every request it makes, which finds injected tags as well.

It does not say whether a tag fires before or after a visitor gives consent, and it is not legal advice.

More Free Tools

Check a page's tags with the meta tag checker, or see all free tools.

Frequently Asked Questions

What does this tracking pixel checker detect?

Known analytics, advertising, session replay, chat, marketing automation, A/B testing, error monitoring and tag manager tools, matched by the URLs in script, iframe, image and link tags and by inline snippets in the page source. Consent managers are listed separately.

Why does it find fewer tags than my browser shows?

It reads the HTML as served and does not run JavaScript. Tags that a tag manager such as Google Tag Manager loads at runtime are not in the source, so they are not seen here. The API's GET /trackers endpoint also records the page's network requests in a real browser.

Does it tell me whether my site is compliant with privacy laws?

No. It lists what is in the page source. It does not check whether a tag waits for consent, and it gives no legal conclusion.

Does it detect every tracking tool?

No. It recognises a fixed list of common vendors. A tool that is not on the list, or one served from your own domain under an unfamiliar path, is not reported.