← Back to Features
Pro

Tracker & Pixel Scanner

Tracker & Pixel Scanner lists what is watching the visitor — analytics, advertising pixels, session recorders, tag managers, chat widgets and consent tools — grouped by category, with the evidence for each one shown next to it.

Nobody adds trackers on purpose, exactly. A marketing tag goes in for a campaign, a chat widget for support, a session recorder for a redesign, and a tag manager quietly loads three more. A year later nobody can say what the site sends to whom, which is awkward when a privacy policy has to list it or a cookie banner has to be accurate.

This tool answers that question for the page in front of you. It recognises around 110 vendors across eleven categories — analytics, advertising and retargeting, session recording, tag managers, social embeds, error and performance monitoring, chat and support, marketing automation, A/B testing, consent management and everything else — and groups what it finds so the shape of the page is obvious at a glance: four analytics tools and two session recorders is a different story from one first-party counter.

What makes the report trustworthy is that every row names its evidence. A finding comes from one of five places, and the row says which: a network request matched against the vendor list, a script, iframe or tracking pixel in the page, a global the snippet leaves behind such as gtag, fbq or dataLayer, a tracking cookie such as _ga or _fbp, or a verification meta tag. Nothing is inferred from a vendor's reputation, and the summary counts ad-tech vendors, session recorders and tracking cookies separately, because those are the ones that tend to matter in a privacy review.

Third-party hosts that match no signature are not dropped. They are listed as unidentified, with how many requests they made and how many bytes they cost, so the report never looks cleaner than the page really is — some will be a CDN or a font host, and some will be a tracker the list has not learned yet. Scripts that only load after a consent banner is accepted appear once they have loaded, so accepting the banner and pressing Re-scan shows the difference consent actually makes.

Live Preview
shop.example.com
Tracker Scanner 9 trackers across 23 signals
9
Trackers
4
Ad tech
2
Recording
11
Tracking cookies
all 23 Analytics 7 Advertising 8 Session recording 3 Consent 2
Analytics (3)
Google Analytics request www.google-analytics.com 28 KB
Google Tag Manager global window.dataLayer
Google Analytics cookie _ga 1st
Advertising (2)
Meta Pixel script tag connect.facebook.net 94 KB
TikTok Pixel pixel analytics.tiktok.com
Key Features

Around 110 Vendors Recognised

Google Analytics and GTM, Meta Pixel, TikTok, LinkedIn, Microsoft UET, Hotjar, Clarity, FullStory, Segment, Mixpanel, Amplitude, Sentry, Intercom, HubSpot, Optimizely, OneTrust and many more.

Grouped Into Eleven Categories

Analytics, advertising, session recording, tag managers, social embeds, monitoring, support, marketing, A/B testing, consent and other — so you see the shape of the page, not an undifferentiated list.

Every Row Shows Its Evidence

Each finding says whether it came from a network request, a page tag or pixel, a page global, a cookie or a meta tag. No guesses, and nothing attributed to a vendor without proof.

Finds Pixels You Cannot See

Picks up 1x1 and hidden tracking images, iframes and inline snippets, including off-site pixels that match no vendor, which are reported with their dimensions.

Tracking Cookies Identified

Names the cookies behind the tracking — _ga, _fbp, _clck, _uetsid, hubspotutk, OptanonConsent and more — including the first-party ones that a third-party script sets.

Unknown Third Parties Listed, Not Hidden

Hosts that match no signature appear as unidentified with their request count and transfer size, so a tracker the list does not know yet is still visible to you.

Common Use Cases

Writing an accurate privacy policy

List exactly which third parties a page contacts and which cookies they set, so the policy and the cookie table describe what the site actually does.

Checking that a consent banner works

Scan before accepting, accept, then re-scan. Anything that was already loading before consent is a problem worth fixing.

Auditing a site you inherited

Find the forgotten tags: an old analytics property, a retargeting pixel from a finished campaign, a session recorder nobody remembers installing.

Explaining a slow page

See how many third parties the page loads and what they transfer, which is often the real answer to why a page feels heavy.

Competitive and market research

Look at which analytics, testing and marketing stack another site runs, as a quick read on how they measure and optimise.

How to Use
1

Open Tracker Scanner

Click the Tracker Scanner icon in the DevSuite Pro dock. The scan runs straight away and the tiles summarise trackers, ad tech, session recorders and tracking cookies.

2

Read the grouped findings

Findings are grouped by category with a count each. Every row names the vendor, the evidence it came from, the host or cookie involved, and the transfer size where it is known.

3

Narrow it down

Use the category chips to show only advertising, only session recording, or only consent tools — whichever part of the picture you are reviewing.

4

Re-scan after consent

Accept the cookie banner and press Re-scan. Anything that only loads after consent now appears, which is the comparison that shows whether the banner is doing its job.

5

Export the evidence

Copy report gives a grouped text summary by category; Export JSON copies every finding with its evidence, host, size and timing for an audit or a ticket.

Ready to Try

Install DevSuite Pro for free and unlock 71+ developer tools for your browser.

Add to Chrome Add to Edge Add to FireFox