See which tracking pixels are firing on any page: account IDs, events and parameters, in real time.
What it is
Pixel Radar answers one question: is this tag actually working? Open the popup and see who is tracking the page you are looking at, with which account ID, which events it has sent, and what data each request carries. Everything stays in the browser.
Coverage
Why this one
01 · Dual detection
Network requests are observed as they leave the browser, and in parallel the page itself is inspected for the tag objects. So you see both a tag that has loaded but not fired yet, and a tag that fires without exposing anything in the page: Google Ads, Floodlight and Amazon all behave that way.
02 · POST bodies
TikTok sends everything as JSON, and GA4 in batch mode packs several events into a single request. Anything that only reads the query string reports those vendors as silent.
03 · Honest empty state
"No detections" has three different causes and three different fixes. Pixel Radar reads the page and names the real one: which consent platform is in use (OneTrust, Didomi, Cookiebot, Usercentrics, IAB TCF), the state of Google Consent Mode, and whether the Google containers are genuinely loaded or only the placeholders exist.
04 · Readable parameters
Click an event and you get the request's key/value pairs rather than a wall of encoded URL. It handles Floodlight's semicolon format too.
Limits
Worth stating plainly, because it is what makes the rest of the claims trustworthy.
Server-side tracking (Meta Conversions API, server-side GTM, calls made from the site's own backend) never passes through the browser, so no extension can detect it. A page with no detections is not necessarily a page with no tracking.
Header bidding is out of scope as well (Prebid, Xandr, PubMatic, The Trade Desk), but by choice: those are not the advertiser's tags, they are the ad auction brought in by the publisher's sales house.
Under the bonnet
webRequest, storage, tabs, scripting, activeTab<all_urls>chrome.storage.session, key tabshost, vendor, detected_via, account_id, time, event, urleval / innerHTMLQuestions
No. No account, no telemetry, no server. Everything it processes stays in your browser and is discarded when the tab closes. The full detail is in the privacy policy.
Since Chrome 72, the API that observes network requests only reports one to an extension if that extension has permission for both the domain being contacted and the page that originated the request. Since any page can contact a pixel, the permission has to cover any page. The code itself only ever looks at a closed list of 38 tracking-platform domains; requests to anything else are never examined.
Yes, and rather than showing you an empty screen it tells you the tags are being held by consent, and which consent platform is doing the holding.
No, and no extension can. Server-side events never travel through your browser.
Yes.
Privacy
Pixel Radar collects nothing, transmits nothing and sells nothing. No registration, no cookies, no analytics, no telemetry. Detections live in chrome.storage.session, kept separately per tab, and are wiped when the tab changes domain, when it closes and when you close the browser.
The JSON and CSV export buttons write a file on your own device, only when you ask for it. Nothing goes over the network.
Every permission the extension requests, what it does with it, and exactly what stays where. Written to be read, not to be skipped.
Free, open source, and it never phones home. Install it and check the next page you were about to argue about.