Analytics detector
What analytics does this website use?
Enter any public URL. The tool reads the page once and lists the analytics, tag managers, ad pixels, session-replay, chat and consent scripts it finds, with property and container ids where they are visible. 42 tools recognised.
What it can detect (42)
Web analytics
- NumberHill
- Google Analytics 4
- Universal Analytics (legacy)
- Plausible
- Fathom
- PostHog
- Umami
- Matomo
- Simple Analytics
- Cloudflare Web Analytics
- Vercel Analytics
- Mixpanel
- Amplitude
- Heap
- Segment
Tag managers
- Google Tag Manager
- Tealium iQ
- Adobe Experience Platform Tags
Advertising pixels
- Google Ads conversion tag
- Meta Pixel
- TikTok Pixel
- LinkedIn Insight Tag
- Pinterest Tag
- X Pixel
- Reddit Pixel
- Microsoft Advertising UET
Session replay & heatmaps
- Hotjar
- Microsoft Clarity
- FullStory
- LogRocket
Marketing automation
- HubSpot
- Klaviyo
- Mailchimp
Live chat
- Intercom
- Crisp
- Drift
- Zendesk Messaging
Consent management
- Cookiebot
- OneTrust
- CookieYes
- Termly
- iubenda
Missing one? Email [email protected] with the vendor and the script host it loads from.
Common questions
How does the detector work?
It fetches the page's HTML once, as a browser would, and matches it against a table of script hosts and initialisation calls for each vendor. It reads the source, not the vendor's name, so a blog post that mentions Google Analytics is not reported as running it.
Why did it miss a tool I know is installed?
Three common reasons. The tag is injected at runtime by a tag manager, so it is not in the HTML. It loads only after a cookie banner is accepted. Or the page is rendered client-side and the HTML the server returns is an empty shell. The result names the tag manager or consent tool when it sees one, which usually explains the gap.
Is any of this stored?
No. The URL is read from the query string, the page is fetched, the result is rendered and the HTML is discarded. The result URL is shareable because the check is repeated when the link is opened.
Can I scan sites behind a login or on my local network?
No. Only public https pages are fetched, every hostname is resolved and checked against private address space before a connection is made, and redirects are checked the same way. That is deliberate: a tool that fetches arbitrary URLs from a server must not be usable to reach things that server can see and you cannot.