Pixel Auditor/Version history

Version history

Every release of Pixel Auditor, newest first — with the major updates in each. Condensed from the project changelog; the finer-grained engineering notes ship with the source.

v2.7.0current version
50releases since March 2026
387tests passing
24tag types + server-side
v2.7.0 October 28, 2026 Latest Major update

Five new vendors, a findings-first Audit tab, one Export menu & the Consent Mode implementation verdict

The release that makes the panel honest about what matters first: the Audit tab leads with its worst finding, every row and section speaks one severity language, and the vendor table grows to 24 tag types — X, Amazon Ads, Floodlight, HubSpot and Adobe join as single table entries, each proven against the vendor's shipped library.

  • Five new vendors. X Pixel (twq; adsct / adsctp hits on analytics.twitter.com, analytics.x.com and t.co), Amazon Ads Tag (amzn; iu3 hits on the NA / EU / FE hosts), Floodlight (Campaign Manager 360 via gtag('config','DC-…') — its ;-separated path parameters are parsed and the event named after the activity tag; before 2.7 these hits were never reported), HubSpot (_hsq / _hsp, the hs-scripts loaders, __ptq.gif — custom tracking domains caught by request shape) and Adobe Experience Platform (Launch, Web SDK alloy, AppMeasurement, Audience Manager — first-party CNAMEs caught by request shape). Detection, cookies, consent hosts, a filter chip and an abstract mark for each. Universal Analytics stays as legacy detection with its RETIRED warning.
  • One vendor table. The vendor signatures, the fire → tag / ID chain, the event-name resolver and the dedup rules lived in several hand-mirrored copies across the page agent, the service worker and the panel — four 2.5.x defects were one copy drifting from another. Each is now one shared module, and a parity gate replays a corpus of captured fires and library URLs through the 2.6.0 code and the new modules, demanding identical answers on every surface. Every fire now carries a stable id, which the panel keys its rendering on.
  • Findings first. A findings strip under Health lists every finding worst first — critical (raw personal data sent while consent was denied), high, warning, info — with a "Passed (n)" line for the clean sections; clicking one scrolls to its section. Sections reorder worst-first, clean sections fold to a green "passed" pill, and the Audit tab's badge counts findings in red instead of cookies plus consent entries. The cookie table shows 25 rows and the consent timeline 15, each with "Show all".
  • One severity system. Four severities decide the Live events bar, the badges, the PII-list pills and the section-title colours, so a PII row with a missing parameter is red, not yellow. One name per concept: the row badge is NO CONSENT (was PRE-CONSENT), the escalation badge PII · NO CONSENT, the section "Personal data (PII) sent without consent"; the Consent Mode audit groups are High / Warning / Info; an expected Google denied-state ping is info with no bar while a third-party pixel is high. On tag cards Found is blue and No events a yellow outline.
  • Live events triage. Issue chips — No consent · PII · Duplicate · CSP blocked · Missing params — filter by finding type, with counts; platform chips show only the platforms present; "n hidden by filters · Clear" reconciles the badge count with the rows; a filter that leaves nothing gets its own empty state instead of the "Waiting for pixel fires…" reload prompt. Each row shows its worst badge and folds the rest into "+N" (hover lists them); missing params read as a count (2 MISSING), duplicates as DUPLICATE ×N.
  • Stable rendering and a windowed stream. Rows, tag cards and dataLayer rows survive the next fire — an open drawer stays on its event, an expanded card stays open, and rows animate only on entry. The stream materialises the newest 60 rows ("Showing 60 of 2,000 fires · Show 60 more · Show all", extending as you scroll); search is debounced 150 ms over a cached haystack. On a 2,000-fire capture one fire → frame fell from ~58 ms to 4–8 ms.
  • One Export menu. Behind the toolbar icon and the Audit tab's "Export…": Preview HTML report (opens in a new tab; print from there) · Download HTML report · Download CSV · Download JSON, disabled with nothing captured, with a "PII redacted" / "Raw PII included" footer. Every export is named pixel-audit_<host>_<YYYY-MM-DD>.<ext>. Saved runs get their own "Export…" (always redacted). The report gains an Event column, the page URL and a print stylesheet.
  • Undo on Clear, a snapshot pill, a paused line. Clear log keeps the capture for ten seconds behind a "Capture cleared · Undo" line that also restores the service worker's copy. The snapshot control is a camera that becomes a "10:42" pill with its own ×; clicking the pill flashes the diff banner instead of deleting it. "Paused · N fires dropped · Resume" sits above the stream while capture is paused.
  • Settings gear. One popover in the header holds Theme, Hide Linker pings, Hide GTM internals, Redact PII in exports and Live violation alerts; the inline controls are gone from the toolbars, and "Help & docs" links to the help centre. A watch's scope stays in the Add a watch dialog.
  • Accessibility and contrast. ARIA tabs with arrow keys, rows as keyboard buttons, Escape closes the topmost layer with focus restored, dialogs trap and return focus, live regions, a name on every icon button, every text token at 4.5:1 or better in both themes, no type under 10 px, targets of 24 px or more, and the focus ring back.
  • First-run and empty states. The Tags tab distinguishes scanning, nothing found and unavailable (Chrome's own pages) instead of saying "No tracking tags detected" while a page loads; a dismiss-once first-run card explains Load → Act → Open Audit.
  • Copy. A collapsed "Why this matters" under every Audit section; abbreviations spelled out (Meta Conversions API, Content-Security-Policy, IAB TCF); TCF findings name the purpose ("Measure ad performance"); sentence-case labels — Live events, Event details, Saved runs, Add a watch, Grant all, Deny all, Reset consent.
  • Consent Mode implementation verdict. The page summary and the report's compliance table say how Consent Mode is implemented, read off what happened: advanced (Google tags send cookieless pings while consent is denied), basic (Google tags hold until consent is granted), none (Google hits carry no Consent Mode state), not applicable, or unknown with the reason.
  • Cross-frame CMP click. "Accept via CMP" collects every frame's answer before rendering, so a Sourcepoint or TrustArc banner inside an iframe is clicked and reported as such — "Clicked Sourcepoint's accept button in an embedded frame" — instead of the top frame's "no match" winning the race. The long-standing limit for iframe-hosted CMPs is closed.
  • GVL vendor map. The TCF fire audit checks vendor-level consent for every detected vendor registered in the Global Vendor List (v3, 2026-10-22): Floodlight with Google (755), Microsoft Advertising (1126), Amazon Ads (793), LinkedIn (804), TikTok (986), Adobe (565) — and findings name the vendor: "consent denied for Microsoft Advertising (IAB vendor 1126)".
  • Suite grows from 279 to 387 tests; every panel change verified in a browser harness that loads the real panel against synthetic traffic.
v2.6.0 October 14, 2026 Major update

Consent × PII correlation, offline TC-string decoding & Google Tag Gateway

The release that closes the compliance loop: personal data leaving the browser while consent for it was denied — the GDPR-fine scenario — becomes one finding, surfaced everywhere; and the detector learns the difference between a server-side container and Google's first-party gateway.

  • PII under denied consent. Every fire carrying PII is correlated with the consent evidence that governed it — the hit's own gcd / gcs signal first, then the IAB TCF record, then the observed consent state, then the pre-consent flag. Google hits are judged on their governing signal (GA4 on analytics_storage, Ads on ad_storage / ad_user_data). Red PII + NO CONSENT badge, an escalation card in the drawer naming what leaked, to whom, and the fix; an Audit section with a green all-clear when every PII fire was consented; a page-summary sentence; a report stat and table; a CSV column. Health: −15 for raw PII under denial (the steepest single deduction), −7 for hashed.
  • Nested payload decoding. JSON request bodies (TikTok, Klaviyo, Segment, sGTM proxies), {batch:[…]} fan-out, GA4 line batches and JSON encoded inside a parameter value (Pinterest ed=, UET pid=) are parsed properly, and the PII detector walks them. Meta's ud[em], a nested context.user.email and the UET pid blob all produced zero findings before. Redaction follows the same paths, and JSON vendors now reach Conversion Reconciliation.
  • TC-string offline decoder. When a CMP writes euconsent-v2 but exposes no working __tcfapi, the string is decoded in-panel — purposes, legitimate interests, special features, vendor consents in bitfield and range form — verified field-by-field against the official IAB library. A paste-a-string tool in the Privacy Frameworks section decodes any TC string.
  • Google Tag Gateway awareness. A first-party gateway (Cloudflare, Akamai, Fastly, a load balancer) serving gtag.js and the hits from the site's own origin under one measurement path was previously reported as a renamed-path sGTM proxy. Now classified as Google (Tag Gateway) with converging loader and collect signals, the sGTM heuristics standing down, and the late-consent-signal failure mode named.
  • Opening the panel no longer reloads the tab when the extension has already captured state — the half-finished checkout you opened the panel to inspect survives. Reload only for a tab with nothing captured.
  • Payload in the event search. Every flattened payload key=value pair joins the search haystack, plain or /regex/ — find a hit by transaction ID, SKU, or hashed-email fragment.
  • Meta CAPI dedup ID after a Next.js route change. The fbq hook now reads eventID for track / trackCustom / trackSingle / trackSingleCustom, not just Shopify's action — so a loaded page no longer shows a false NO DEDUP ID.
  • Enhanced Conversions wrapper is not a PII finding. Google's em=tv.1~… hashed user data gets its own EC DATA badge and type, no hashed-tier deduction, and is left to the Enhanced Conversions section — while still redacting in exports and still escalating when sent under ad_user_data denial.
  • GTM-managed Google Ads conversions are no longer flagged as missing send_to: the wire form (label= / cl=) now satisfies the rule.
  • Suite grows from 206 to 279 tests; the shared payload parser retires the first of the hand-mirrored code paths.
v2.5.6 August 21, 2026 Major update

Cross-platform Conversion Reconciliation

Every earlier audit section judged one platform in isolation. The question an advertiser actually asks — did all my platforms record the same purchase, once each, with the same order ID and value? — now has its own section.

  • Conversion Reconciliation. One row per platform for the same checkout: conversions, sends, order ID, value, currency, dedup ID, user data. Findings for duplicate conversions, order-ID disagreement, value and currency mismatch, missing order or dedup IDs, and uneven enhanced-conversion coverage. In the Audit tab, the HTML report, and saved runs. Replaying a live export reproduced, automatically, three findings that had previously taken manual payload analysis.
  • Dedup no longer hides a genuine duplicate conversion — two conversions for different orders inside the dedup window are split when both sides carry an order ID and disagree, while a wire twin with no ID still collapses into its JS fire.
  • JSON export carries findings — server-side, Enhanced Conversions, CSP-blocked, privacy signals and the reconciliation verdict, so conclusions no longer have to be re-derived from raw payloads.
  • Enhanced Conversions audit hardened — a dataLayer.push carrying a hash no longer counts as proof the data reached Google; wire user-data evidence is recorded before dedup can suppress it.
  • dataLayer hook survives displacement by a CMP or tag shim that replaces push without chaining; queued UET events surface as silent when bat.js is blocked by an ad blocker, CSP, or consent gate.
  • SPA rescan cost and coverage — inline-script text cached and invalidated by the MutationObserver; route changes now also re-run server-side detection and the cookie scan.
v2.5.5 August 20, 2026 Major update

Enhanced Conversions audit, Bing UET accuracy & Next.js hardening

  • Enhanced Conversions audit. A new Audit section answers "is user-provided data captured and sent?" for Google Ads and Microsoft UET enhanced conversions — reading the tv.1~ wrapper, bare SHA digests and the UET pid blob on the wire, and gtag('set','user_data') / allow_enhanced_conversions / uetq.push('set') in JS. Verdicts: sent · captured but not sent (with a Consent Mode note when ad_user_data: denied is the likely cause) · configured with no data · not detected. Field names only, never values; an empty wrapper is its own tell.
  • Bing UET events correctly named. Three stacked defects hid every named UET goal: an Add-to-Cart with value 25 rendered as "25", custom goals rendered as "custom", and every event on a loaded page was literally named "event". consent / set pushes are no longer shown as events.
  • Next.js / SPA hardening. document_start accessor traps on window.dataLayer and window.uetq hook whatever the page assigns, at assignment time — surviving the client-side re-init that reassigns dataLayer in React apps. pushState / replaceState / popstate trigger a debounced rescan ladder; tracking scripts landing after the initial ladder re-hook.
  • JS and wire twins finally collapse. UET beacons' en=Y flag and gtag pseudo-URLs both broke dedup, so a GA4 purchase and an Ads conversion each showed twice. A live purchase window shrank from 9 rows to 6 — one per platform plus the site's own genuine double-fire.
  • Google Ads conversion-with-cart-data wire hits parsed, so Product IDs appear on Ads conversions that carry an item= param.
v2.5.4 August 1, 2026 Major update

Meta transport capture, Shopify support & the silent-tag audit

The release that closes the "Meta Pixel Helper sees events, other inspectors don't" gap — and turns a tag that's installed but never fires into a first-class finding.

  • Meta form-POST transport capture. Payloads past 2 KB (Advanced Matching, cart contents, CAPI event IDs) go out as a hidden form submission no fetch/XHR/img/beacon hook sees. The form submission itself is now intercepted — so Meta's richest events are captured.
  • Shopify trackShopify support. Shopify's Facebook & Instagram channel routes every Meta event through an undocumented fbq action that was previously dropped. Now fully parsed, including the CAPI dedup event ID.
  • Silent-tag audit. A tag whose library loaded and whose ID was extracted, but which sends nothing, gets a NO EVENTS badge, its own Audit section, and a health deduction.
  • webRequest safety net. Fires from sandboxed and opaque-origin frames — and transports no JS hook covers — are captured observationally, standing down whenever a richer page-sourced capture exists.
  • Early fbq trap. Inline fbq('track','PageView') calls are caught from the moment the page assigns the stub, via a transparent Proxy that never breaks the page's own pixel.
  • Image beacons fully intercepted. createElement('img'), setAttribute('src'), and markup-injected pixels are now covered at the prototype level — previously only new Image() was seen.
  • PII severity calibration. MD5 and base64 digests recognised as hashes, country_code no longer flagged, and pseudonymous IDs (external_id, customer_id) get their own medium tier.
  • Meta event names fixed. Body-carried hits no longer render as tr — rows read PageView / ViewContent / Purchase, and distinct Meta events no longer collapse in dedup.
v2.5.3 July 31, 2026 Correctness patch

Four dead code paths, three state bugs

No new features — nine defects found by auditing the extension against its own intentions, several of them findings that had shipped but never actually counted.

  • Event validation now runs — once per fire, at ingest, in chronological order. The missing-params health deduction, the report's missing: badge, and the CSV column work for the first time, GA4 network hits included.
  • PII now deducts from the health score (raw −10, hashed −5) — previously a page shipping raw emails could still score an A.
  • "Redact PII in exports" toggle (default ON) scrubs JSON, CSV, and HTML deliverables; saved runs no longer retain raw leak values.
  • CSP-blocked tag libraries now scored (−15) — a page whose tag libraries were all refused could previously still score 100.
  • State resurrection fixed — a service-worker cold start could re-insert the previous page's tags over a fresh navigation and persist the corruption.
  • Back/forward no longer blanks the panel — tags repopulate within ~1.5 s after a bfcache restore.
  • Cross-site comparisons flagged — run compare and snapshot diff refuse to silently compare two different sites.
v2.5.2 July 31, 2026 Fix

Google Ads remarketing dedup

One remarketing action fires several beacons (viewthroughconversion, rmkt/collect, 1p-user-list) that derived different pseudo-names and rendered as duplicate rows. Pseudo-names now collapse to one dedup token while real named events keep their own keys.

v2.5.1 July 31, 2026 Fix

CSP library-block detection + PII false positive

CSP refusals of a tag library itself (bat.js, fbevents.js) are now flagged, not just blocked hits; bat.bing.net added as a Bing UET host; and empty placeholder params (external_id=) no longer report a high-severity PII leak.

v2.5.0 July 25, 2026 Major update

Consent ground truth & dedup auditing

  • Per-hit gcd decoding — the consent state each Google hit actually carried, per signal, with default vs. user-update provenance, and a warning when Consent Mode isn't active at all.
  • Meta CAPI dedup audit — when dedup is demonstrably in use, every Meta browser event missing its dedup event ID is flagged: those risk double-counted conversions.
  • Plain-language Page Summary — the paragraph a non-technical client reads first, in the Audit tab and at the top of the HTML report.
  • CSP-blocked fires scored & reported — health deduction, report badge and endpoint table, CSV column.
  • sGTM classifier hardened — Google's closed TLDs (*.goog, *.google) are no longer flagged as server-side proxies.
v2.4.7 – v2.4.9 July 25, 2026 Fixes

CSP-blocked fire detection & classifier fixes

2.4.9 detects tracking requests refused by the site's own Content-Security-Policy — previously shown as delivered when the vendor received nothing. 2.4.8 stops Meta network fires rendering the full request URL as the event name. 2.4.7 stops www.google.com/ccm/collect being flagged as a server-side proxy.

v2.4.1 – v2.4.6 June 28, 2026 Refinements

Google Ads clarity & encoded sGTM transport

  • Encoded sGTM transport decoded — GA4 requests base64-wrapped inside an opaque query param on a first-party path are recovered, with event name and measurement ID (live-tested against a Stape-style custom loader).
  • Conversion Linker handling — Ads setup pings are muted (or hidden with a toggle) so conversion counts read clean, with a fix ensuring only the true Linker is treated as plumbing.
  • Plain-language event summary in the drawer — one consolidated card with identity, value, currency, transaction, and items; packed dynamic-remarketing data= params unpacked.
  • Fully self-contained package — the last remote reference (report fonts) removed for Chrome Web Store compliance.
v2.4.0 June 28, 2026 Major update

New vendors, IAB privacy frameworks, reporting & compare

  • Five new platforms — Segment, Tealium, Hotjar, Criteo, and Klaviyo, each with ID extraction, cookie attribution, filter chips, and pre-consent flagging.
  • IAB privacy frameworks — TCF v2.2, GPP, US Privacy, and Global Privacy Control read from the page's CMP APIs, with an 11-purpose consent grid and a fire audit against denied TCF consent.
  • CSV export of captured fires (RFC-4180) from the Live Events toolbar.
  • Compliance summary at the top of the HTML report — consent pass-rate, pre-consent fires, PII, SST, and a framework table.
  • Cross-run compare — pick any two Saved Runs for a side-by-side delta of stats, tags, and cookies.
v2.3.0 – v2.3.1 May 24 – June 28, 2026 Major update

Unified gtag.js coverage & security hardening

  • Google Ads and Merchant Center via unified gtag.js — ID-driven detection, modern endpoints (/ccm/collect, /pagead/1p-conversion, td/rul), batched-fire fan-out, and Arguments-object dataLayer pushes.
  • Renamed-path sGTM detection — GA4 hits on arbitrary first-party paths (e.g. /kpi/) caught by their Measurement Protocol v2 signature, independent of host and path.
  • Modern GA4 packed item format (pr1=idSKU~nmFoo~…) parsed — ecommerce items render in the drawer.
  • Security hardening — cross-tab state reads locked to the side panel, an authenticated command channel between content scripts, and PII redacted from Saved Runs at the persistence boundary.
v2.0.0 April 22, 2026 Major release

The foundation — first public update since 1.0

The cumulative result of the 1.x development series, shipped to the Chrome Web Store as one release.

  • PII Leak Detector — raw emails, phone numbers, and 15+ named PII fields, with heuristic validation of short-code params.
  • Consent Mode classifier — reads the gcs= parameter and distinguishes denied-state modeling, plumbing, real violations, and inconsistent fires.
  • Consent Mode Simulator — Grant / Deny injection with a 5-second diff, plus one-click Accept / Reject auto-clicks across 19 CMP vendors.
  • Server-Side Tracking detector — script scan, runtime hooks, dataLayer inspection, and network classification against canonical vendor hostnames, with confidence fusion.
  • Saved Runs with side-by-side diff, multi-watch desktop notifications, event search + regex, pause / resume, and a per-fire latency badge.
  • Light + dark themes, a 27-icon SVG system, self-hosted fonts, and an XSS-hardened rendering pipeline.
v1.0.1 – v1.13.1 April 21 – 22, 2026 Development series

The rapid-iteration series

Twenty-seven releases of private development between 1.0 and 2.0 — everything above was built and battle-tested here.

Show the release-by-release list
  • 1.13.0 – 1.13.1 — Server-Side Tracking detector rebuilt (TikTok / Pinterest / Snap / Zaraz / Stape coverage), then a false-positive hotfix with anchored paths and payload verification.
  • 1.12.0 – 1.12.3 — SVG icon registry replacing every emoji, Chrome Web Store compliance audit, Live Events regression hotfix, and the store listing renamed to "Pixel Auditor: Tag, PII & Consent Mode Inspector".
  • 1.11.0 — Watches became per-site scoped with cross-tab firing.
  • 1.10.0 — Six usability fixes from in-use feedback.
  • 1.9.0 – 1.9.2 — Pause/Resume, search + regex, multi-watch, Saved Runs, and the tag latency badge.
  • 1.8.0 — CMP auto-click coverage grew from 12 to 19 vendors.
  • 1.7.0 – 1.7.1 — The tiered Consent Mode classifier replaced the binary pre-consent flag.
  • 1.5.0 – 1.6.0 — The Consent Mode Simulator: Grant/Deny injection, CMP auto-click, storage reset, no-op advisory.
  • 1.4.0 – 1.4.1 — Duplicate-detection overhaul; dark theme became the default.
  • 1.3.0 – 1.3.2 — The PII leak detector shipped, with phone false-positive and stream-regression fixes.
  • 1.1.0 – 1.2.0 — The zinc + violet theme system, light mode, brand-safe platform icons.
  • 1.0.1 — Security & compliance: XSS hardening, bridge message validation, memory caps, self-hosted fonts.
v1.0.0 March 6 – 8, 2026 Initial release

The initial build

  • Core detection engine — 9 tag types across the Google stack (GTM, GA4, Ads, Merchant Center, UA), Meta Pixel, LinkedIn Insight, Bing UET, and Microsoft Clarity.
  • Four capture layers — global-variable scanning, script scanning with MutationObserver, network interception (fetch / XHR / Image / sendBeacon), and JS API hooks (dataLayer.push, gtag, fbq, uetq.push, clarity).
  • Four-tab side panel — Tags, Live Events with detail drawer, Audit with A–F health score and consent timeline, and a searchable dataLayer inspector.
  • Consent Mode tracking, pre-consent flagging, cookie audit, event watches, snapshot/diff, and a self-contained HTML report export.

Running an older version?

Chrome updates extensions automatically, but you can force it: chrome://extensions → Developer mode → Update.