Universal Pixel Debugger

Chrome side panel · 49 networks · runs on your computer

What did the pixel actually send?

Universal Pixel Debugger decodes what Meta, Google, TikTok and 46 more ad and analytics networks receive from any page: event names, values, currencies, order IDs and products, exactly as sent, each with the key it came from.

Signalslive0 events · 7 networksthis page · simulated

Simulated in your browser from what you do on this page: load it, scroll, hover “Add to Chrome”, place the test order below. Nothing is sent. Click a dot to decode it.

Cross-network checks

One order. Three networks. Two different values.

A store sends the same purchase to several networks, and they don't always agree. Pixel Debugger lines up events that share an order ID and shows what each network actually received, with the key it came from.

A test order. The recorder above logs what each pixel would send.

Linen pillow cover79.00 USD
No order yet. Place the test order to compare what each network received.

Exactly as sent

Nothing renamed. Nothing guessed.

Names stay as sent

Pinterest calls a purchase “checkout”. It stays “checkout”: no invented categories, no tidy renaming.

event = checkout

Missing stays missing

If GA4 got a value but no currency, you see that. The currency isn't borrowed from Meta.

Value 79.00 from epn.value
Currency Not observed

What the network supports, and what it got

Each event lists the parameters its network defines, sent and not sent, grouped by what they do.

TikTok parameters · 8 of 59 known fields sent
▸ Not sent (51)

Unknown keys stay visible

Anything the request carried outside the known format is listed with its exact path. Nothing is dropped for looking unfamiliar.

Other sent fields (4)
context.library.version = 2.1
properties.content_type = product
_dbg = 0
sdkid = W3D8…

Decoded natively

49 networks, each read in its own format.

Browser pixels, first-party collectors and Google tag gateway paths. Every decoder is checked against real traffic from live stores, not only against documentation.

Ads & social 18

  • Meta
  • Google Ads
  • TikTok
  • Pinterest
  • Snapchat
  • Reddit
  • X Pixel
  • LinkedIn
  • Quora
  • Microsoft UET
  • Amazon Ads
  • OpenAI Ads
  • Nextdoor
  • Spotify Ad Analytics
  • LINE
  • Kwai
  • VK Ads
  • Yahoo! JAPAN

Programmatic & native 17

  • Floodlight
  • Google Merchant Center
  • The Trade Desk
  • Criteo
  • RTB House
  • AdRoll
  • StackAdapt
  • MNTN
  • Quantcast
  • Yahoo DSP
  • Claritas
  • Adform
  • Xandr
  • Teads
  • Taboola
  • Outbrain
  • AppLovin

Affiliate 4

  • Awin
  • Impact
  • CJ Affiliate
  • Rakuten Advertising

Messaging & CRM 3

  • Klaviyo
  • Attentive
  • Insider

Analytics 7

  • GA4
  • Mixpanel
  • Amplitude
  • Plausible
  • Umami
  • Yandex Metrica
  • AppsFlyer

Also detectsShopify, WooCommerce, WordPress, Magento, BigCommerce, Wix, Squarespace, Webflow, Salesforce Commerce Cloud, Shopware, PrestaShop and VTEX.

What it will never do

This website has no pixels.

Open Pixel Debugger on this page and the board stays empty. Everything the recorder showed was simulated in your browser. The extension works the same way: it watches, and keeps what it sees on your computer.

Signals · 0 events · listening
  1. It never blocks or changes a request.It only observes. Sites behave exactly as they do without it.
  2. It never sends what it sees anywhere.No server, no account, no analytics of its own. Captures live in Chrome's session storage; recordings stay on your disk until you delete them.
  3. It never guesses.A currency that wasn't sent reads “Not observed”, not USD. A request without an event name says so.
  4. It never hides a value.What the network received is what you see, hashed emails and click IDs included. Share exports with that in mind.

Debug the pixel, not the dashboard.

Free. Works on any site you open. Lives in Chrome's side panel next to the page, so you see each event as it fires.

Add to ChromePrivacy policy