Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Developer Tools extension

Tracking Auditor

Records GA4, Google Ads and other marketing pixel requests in DevTools.

by mbaersch · 3 listings

Add to RadarChrome Web Store Free plan tracks 1 extension · no card
extwatch.com/extensions/tracking-auditor-cngpoecoknpgfjfaafnekjoaeohaejpb
Tracking Auditormbaersch · Developer ToolsLow access
Users
166
#5,142 of 31,330 in category
Rating
5.00
1 rating · median 4.63
Version
1.2.0
123 KiB · Manifest V3
Access
Low14/100
2 permissions
From the store listing

Screenshots

4 images from the publisher · use the arrows or pick one · swipe or pick one

Tracking Auditor screenshot 1Tracking Auditor screenshot 2Tracking Auditor screenshot 3Tracking Auditor screenshot 4
1 / 4

Description

As written by the publisher on the store

Yet another debugger extension. Tracking Auditor is a lightweight Chrome DevTools extension that records and shows requests of the inspected tab, including GA4 transports that common debuggers might miss. The goal is narrow: "detect requests, read parameters, even if a Google Tag Gateway, Stape custom loader or custom path is used".

As a focused "gap-filler" (not a replacement for David Vallejo's excellent Analytics Debugger) it started as a personal tool for quick debugging in those edge cases where no typical request format / path is used for GA4 requests. But as most marketing setups include other client-side tags, I added more formats instead of switching between several "Pixel Helpers" (see list of services and monitored request types on the "Extension homepage").

This Extension adds a "Tracking Auditor" tab to DevTools when installed.

How To Use

Hit Start & Reload — the page reloads and every hit is listed in blocks per navigation, in order, with event name, parameters, a user-data summary and (where present) the consent state decoded.

A collapsible "Record" settings row switches services on/off (capture), and an independent
"Show" filter row (service pills + fulltext) narrows the displayed log. A pill starts pulsing

once its service has actually sent something, so you can see what a site really uses without

unhiding anything.

---

  • Changelog:
  • ----------------
  • v1.2.0
  • Hits that were missed entirely are now recognized: Meta events sent as multipart POST (e.g. a Purchase with user data), Reddit's newer POST to /rp, LinkedIn /wa/ beacons without gzip, and the short Google Ads conversion path of a Google tag gateway.
  • GA4 and Meta now show value, currency and transaction / order id like the other services.
  • Dedup keys are read more precisely: LinkedIn's eventId is shown, a Snapchat cdid generated by the pixel itself no longer counts as a dedup key, and Reddit's conversion and transaction ids show whether they arrive hashed.
  • Meta advanced matching in the nested aud[em][0][v] form is read as well.
  • Stape Data Client: its JSON format is flagged as an info strip above the page's cards (a transport, not a service).
  • Floodlight: a Google tag with a DC- id that only sends its measurement ping (no activity tag) now shows as a card instead of nothing.
  • v1.1.0
  • New service: the OpenAI ads pixel (default "on"). Its requests arrive batched, so they are split into one card per event, and the pixel's own diagnostic event gets a card too — it states the consent the SDK acted on and names any events it rejected before sending.
  • For that pixel, user data is separated by where it came from: what the site handed over on purpose, versus what automatic advanced matching picked up from the page's forms, scripts and markup.
  • The panel now takes its font size from the browser instead of forcing a small fixed one, and every size scales with it. If you had to zoom to read comfortably, you no longer should.
  • Filter pills show which services are actually firing: a pulsing dot appears the moment a service sends something, and stays until you stop recording — regardless of whether its cards are currently shown.
  • v1.0.2
  • fixed decoding of batched GA4 events. Now renders multiple cards correctly.
  • v1.0.1
  • first "complete" release also includes Floodlight (to fill the gap in the Google stack; default "on"), Criteo, Taboola, and Outbrain (default "off") and also Awin (probably the only affiliate network in this tool; default "off") as new services. If you want to debug any of them (except Floodlght), switch recording on first once.
  • taggrs Custom Loader detection and decryption
  • Optimized handling for first-party detection
  • new option to switch off background color-coding for different vendors
  • v0.9.0
  • added Hubspot tracking
  • PII / user-data block in request details
  • Service-worker notice: detects the Google Tag Gateway first-party service-worker loader and shows a compact per-block strip — hits may be dispatched from the worker and stay invisible to the page-scoped DevTools network. UI-only (not a card), with a "mute for session" link
  • Deep Capture (service-worker / edge hits): an opt-in mode that adds a second capture source via `chrome.webRequest` (in a new background service worker), catching tracking hits dispatched from a service worker's own scope — first-party Google Tag Gateway, Cloudflare edge, and Bing UET
  • Newest-first ordering: new hits and page-load blocks are inserted at the top instead of the bottom, so the freshest hit stays in view and Chrome's scroll anchoring keeps whatever you're reading in place. The "follow" auto-scroll toggle is removed as redundant
  • Meta silent-pixel warning: a pixel can initialise yet send no tracking events occur — a silent tracking failure, typically caused by Meta's traffic-permission settings
  • GA4 e-commerce items: product params are decoded into readable fields
  • v0.7.2
  • Service-worker de-duplication: when a service worker (e.g. Cloudflare Zaraz) intercepts a page's `fetch()`, DevTools surfaces the hit twice — the aborted page-side request that never reached the network, plus the worker's real outgoing request. The aborted phantom (network error and no server connection) is now dropped, so each logical hit counts once
  • v0.7.1
  • Added Reddit Pixel and Snapchat Pixel
  • The `/wa/` enhanced-conversions POST from LinkedIn is now decoded asynchronously into its own card with hashed email, Signal Type and collected IDs.
  • UI improvements

Ratings and reviews

Split of the 1 written reviews we hold
Reviews on the store
5.001 rating on the store
1 written review we hold
5 ★100.0%1
4 ★0.0%0
3 ★0.0%0
2 ★0.0%0
1 ★0.0%0
Katharina

Vielen Dank für das super hilfreiche Tool. Das hat mir im letzten Projekt einiges an Zeit gespart!

Radar

Track Tracking Auditor on Radar

This page shows the listing as it is today. Add it to Radar and get one email when it changes.

  • Users and rating
  • Store text and screenshots
  • Permissions it asks for
Free plan tracks 1 extension · no card
Ext Watch Radar watchlist cards showing tracked extensions with users, rating, version and latest store change
Guide

Tracking Auditor, in plain words

What it is, what to use instead, what it can access and how to fix it.

At a glance

Tracking Auditor at a glance

Tracking Auditor is a Developer Tools extension by mbaersch with 166 users. Chrome Web Store users rate it 5.00 out of 5 from 1 rating, which is still a small sample. By users it sits in the top 25% of Developer Tools extensions.

By users
#5,142of 31,330 in Developer Tools
Rating
5.00category median 4.63
Access
Low14 of 100

Tracking Auditor alternatives

Closest by what they do · users as the store shows them · bars on a log scale
Tracking Auditor1665.00 ★
Google Ads Match Type Helper™5K4.7 ★Usability Booster for Google Ads2K5.0 ★Google Ads Competitor Analysis1K5.0 ★Google Ads Keyword Optimization Tool4264.6 ★Pixel Auditor1095.0 ★
Permissions

Is Tracking Auditor safe?

Tracking Auditor asks for 2 permissions. One of them gives wide access.

Permissions show what it could do, not what it does. See the full permission list.

14/ 100Low access
Tracking Auditor2 permissions · 1 wide
  • webRequestWatch the web traffic your browser sends

Every permission Tracking Auditor asks for

2 permissions · 1 sensitive · Low access overall

Browser permissions · 2

  • Watch the web traffic your browser sendswebRequest
  • Save its own settingsstorage

Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.

Troubleshooting

Tracking Auditor not working?

What recent reviews say

Store reviews from the last 90 days
1recent reviews, none with 1 or 2 stars
1–2 stars 3–5 stars

Common fixes

Try them in this order
  1. 1Update Chrome and the extension
  2. 2Turn it off and on in chrome://extensions
  3. 3Reload the page
  4. 4Turn other extensions off in case two clash

Still stuck? Contact the maker or try an alternative.

298,549 Chrome extensions in one place

Know when a listing changes

Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.

No credit card neededFree ExplorerAsk Claude about any extension