Item logo image for Pixel Auditor: Tag, PII & Consent Mode Inspector

Pixel Auditor: Tag, PII & Consent Mode Inspector

https://pixelauditor.ratanjhadigital.com/
5.0(

32 ratings

)
ExtensionDeveloper Tools
Item media 3 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 4 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 1 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 2 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 3 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 4 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 1 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 2 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 1 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 2 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 3 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector
Item media 4 (screenshot) for Pixel Auditor: Tag, PII & Consent Mode Inspector

Overview

Inspect every tracking pixel firing on a page: tag IDs, event payloads, consent-mode signals, cookies, and PII leaks.

Pixel Auditor is a real-time tracking pixel auditor and inspector for marketers, analysts, and developers. Open the side panel on any website and instantly see every tracking tag on the page, watch events fire live, and audit your implementation. No separate tools. No DevTools. No technical setup required, no cost. ────────────────────────────────────── SEE WHAT'S FIRING, LIVE ────────────────────────────────────── Live event stream shows every tracking request as it happens: platform, event name, the method used to fire it, full payload, and fire latency. Regex search, platform filters, pause/resume recording, and watched-event notifications (per-site or global) help you focus on what matters. Take a snapshot at any point and see which fires are new since then. ────────────────────────────────────── SUPPORTED PLATFORMS ────────────────────────────────────── Detects tracking tags from the major tag management, analytics, and advertising ecosystems commonly deployed on the modern web. Identification combines script-src scans, inline initialization code, dataLayer configuration, and live network traffic, so tags are caught whether they load synchronously, async, or through a consent-gated injector. ────────────────────────────────────── CONSENT MODE AUDITING AND SIMULATION ────────────────────────────────────── Inject Grant All or Deny All Consent Mode v2 states with one click and watch exactly which tags respect consent. Auto-clicks the real CMP banner across 19 of the most widely deployed consent management platforms, covering enterprise tooling, popular CMS plugins, and newer independent vendors, with a text-based fallback for custom banners. Every fire is classified against Consent Mode v2 semantics so compliant modeling pings are distinguished from real consent violations. A Reset Consent button clears site cookies, localStorage, and sessionStorage so the banner re-prompts for a clean test. ────────────────────────────────────── PII LEAK DETECTION ────────────────────────────────────── Scans every outgoing tracking hit for emails, phone numbers, and more than fifteen named identifying fields such as full name, date of birth, government IDs, and address components. Flags hashed identifiers (SHA-256, SHA-1) when they appear in identity-shaped parameters. Contextual heuristics avoid noise from unrelated platform metadata. ────────────────────────────────────── SERVER-SIDE TRACKING DETECTION ────────────────────────────────────── Catches first-party proxied tracking that standard pixel checkers miss. Supports server-side tag manager implementations routed through custom domains or managed hosts, server-side conversion APIs used by the major social and ad platforms, and enterprise-grade edge-layer tag forwarders. Multi-source detection: inline script scan, runtime dataLayer inspection, container-state probing, and network-level classification of every captured fire. ────────────────────────────────────── AUDIT REPORTS, HEALTH SCORING, AND SAVED RUNS ────────────────────────────────────── Every session includes an A through F health score with prioritized issues such as duplicate installs, pre-consent fires, missing measurement IDs, dormant tags, and funnel mismatches. Save any audit state as a named run and diff it against future sessions to validate deploys. Export a shareable single-file HTML report. ────────────────────────────────────── INTERFACE ────────────────────────────────────── Dark and light themes with a header toggle. Self-hosted fonts so nothing loads at runtime. Every icon is an inline SVG that themes cleanly. The detail drawer is drag-resizable. ────────────────────────────────────── ABOUT THE DEVELOPER ────────────────────────────────────── Pixel Auditor is built and maintained by Ratan Jha. Every detection rule, classifier, and heuristic in this extension is grounded in years of hands-on experience auditing real-world tracking implementations, consent management deployments, and server-side tag setups. The tool reflects how tracking is actually done, and how it typically breaks, in production environments, not textbook examples. ────────────────────────────────────── WHO IT'S FOR ────────────────────────────────────── Digital marketers verifying tag implementations Analysts checking event data quality Developers debugging tracking integrations Conversion and paid media teams auditing pixel setups Agencies auditing client websites before go-live ────────────────────────────────────── PRIVACY ────────────────────────────────────── All audit data stays on your machine in chrome.storage.local. Pixel Auditor makes zero outbound requests of its own and never transmits any data to the developer or any third party. The broad host permission exists solely so detection can run on any site you choose to audit. Full privacy policy: https://pixelauditor.ratanjhadigital.com/privacy.html Not affiliated with any analytics, advertising, or consent management vendor. All trademarks are property of their respective owners. ────────────────────────────────────── What it tells you ────────────────────────────────────── Tag IDs (G-XXXX, AW-XXXX, MC-XXXX, ca-pub-XXXX, pixel IDs, partner IDs, UET ti, etc.) Every event fire — name, payload, timing, dedup-aware grouping dataLayer pushes with a Sent / Silent / Pending state machine Consent Mode v2 timeline + a built-in simulator that injects gtag('consent','update') and shows what fires in the next 5 seconds One-click CMP banner accept / reject for 30+ vendors High-recall PII leak detection: emails, phone numbers, hashed identifiers Cookie audit for 20+ tracking cookies A–F health score with actionable reasons HTML and JSON exports + saved runs for before/after deploy comparison Real-time desktop notifications when a high-severity consent breach fires Everything runs locally in your browser. No data leaves your machine. ────────────────────────────────────── Pixel Auditor 2.7.6 — what’s new since 2.6.0 ────────────────────────────────────── More platforms Five more ad and analytics platforms are detected, 24 tag types in all. The full list is on the Pixel Auditor website. Consent Consent Mode implementation verdict: advanced, basic or none, shown in the audit, the page summary and the report. The cookie-banner click test now works when the banner lives in an iframe. TCF findings name the vendor behind each purpose, so you can see which registered vendor a finding belongs to. Audit tab Findings come first: a findings strip, sections ordered worst first, clean sections folded, and a badge that counts findings. One severity system across rows, badges and the report, with “without consent” named the same way everywhere. A short “Why this matters” on every audit section. Live events Rows and tag cards keep their place and selection while new fires arrive. Triage chips for issues and for the platforms actually present, a worst-badge with “+N”, a hidden-by-filters count, and missing parameters shown as a count. Duplicate detection rebuilt on evidence: a tag loaded by a tag manager, a page reload, or a session recorder’s periodic beacons no longer shows DUPLICATE. The badge now needs two loaders or a duplicate inline init. A dataLayer push is confirmed by the analytics hit that carries its event name, waiting up to 10 s for batched hits. Pushes are no longer marked “no hit” when the hit simply arrived late. Faster on busy pages: windowed stream, debounced search, per-fire work done once. PII A field with a PII-style name is flagged only when its value can be that kind of data. A boolean in a field called “mobile” is no longer a phone-number leak. Export and reports One Export menu. Every file is named by site and date, and shows whether PII was redacted. Saved runs export. The HTML report has an event column, a compliance table with the Consent Mode verdict, and print styles. Clear offers Undo. Pause and snapshot controls read as their current state. Settings and accessibility One settings gear in the header replaces the inline controls. Keyboard-navigable tabs and rows, Escape closes the top layer, live-region announcements, named icon buttons, higher contrast and a visible focus ring. A first-run card, honest empty states, sentence-case copy and abbreviations spelled out on first use. Under the hood One shared vendor table, event-name resolver and deduplication module used by the page agent, the background worker and the panel. No new permissions.

Details

  • Version
    2.7.6
  • Updated
    October 28, 2026
  • Size
    343KiB
  • Languages
    English
  • Developer
    Ratan Jha, Inc.
    C6, Sector 7 Noida, Uttar Pradesh 201301 IN
    Website
    Email
    write@ratanjha.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, please open this page on your desktop browser

Google apps