See every analytics and ad tag fire, the data layer pushes that triggered them, and any duplicates or personal data leaking out.
Users
49
+7 in 30 days
Rating
5.0 / 5
unchanged in 30 days
Ratings
6
0 in 30 days
Store rank
#110K
#91K among extensions
Version
1.1.0
updated 27 Aug 2026
Users
monthly, 2 months
Latest, 19 Oct 2026:49 usersMove the mouse over the chart for any month
Ratings count
monthly, 2 months
Latest, 19 Oct 2026:6 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Tag Debugger by Aloola.io
Tag Debugger takes the guesswork out of marketing tag QA. Open DevTools, load a
page, and see exactly which analytics and advertising tags fire, what data each
one sends, and which of them are wrong.
WHAT IT SHOWS
• Every tag, as it fires — grouped by the page it fired on, with a timestamp,
HTTP status and response time. Navigate around and the log keeps its shape
instead of becoming one long stream.
• The data inside each tag — every dimension and metric, sorted into readable
sections rather than dumped as one flat list of query parameters.
• What the tag actually means, not just what it sent — the event name is
translated out of each platform's transport format, so a row reads "Page
View" or "Purchase" instead of the generic verb the wire protocol happens to
use, and a request is attributed to the specific product that sent it rather
than to the container it was deployed through.
PROBLEMS IT CATCHES
• Leaked personal data — emails, phone numbers, credit card numbers (validated
by issuer prefix and Luhn checksum), US Social Security numbers and dates of
birth found inside outgoing tags. Sending these to marketing endpoints
breaches most vendors' terms and creates privacy exposure. Detected values
are always masked; the extension never displays the raw personal data.
• Duplicate tags — the same event fired twice because it is implemented twice,
typically once hardcoded on the page and once again through a tag manager.
• Exit beacons — tags that fire as the user leaves a page. These are correctly
attributed to the page being left, not the page being opened, so you can see
what really happened on the way out.
• Broken requests — 4xx and 5xx responses from tag endpoints.
WHAT IT RECOGNISES
Around 70 built-in signatures, covering the analytics, tag management,
advertising, social, customer data, A/B testing, session replay and consent
platforms in common use. Anything it does not recognise is still listed, with
its host and its parameters, so nothing the page sent goes unaccounted for.
BUILT FOR REAL WORK
• Highlight the parameters you care about — star the page name on one platform,
say, and its value appears on every row for that platform without opening any
of them. Highlights are per vendor and are remembered between sessions.
• Filter by category, or by finding — show only tags carrying personal data, or
only duplicates, or both at once.
• Search across vendor, account and any parameter.
• Big or small rows, light or dark theme; your choice is remembered.
• Export to CSV — one row per tag, with parameters as parseable JSON, so you
can pivot the results or attach them to a ticket.
PRIVACY
Everything stays in your browser. Tag Debugger sends no data anywhere, has no
analytics of its own, and no account to create. Captured requests live in
memory for the tab you are inspecting and are discarded when you close it. The
only thing saved is your interface preferences.
Built by Aloola.io.