Feed
Every event as a card
Latest on top, with the value and IDs on each card. Open one to read every parameter and copy it as JSON.
Chrome side panel for the Meta Pixel
A radar for your Meta Pixel
Open the side panel and get a live health score, every event as it fires and a clear fix for each problem.
Runs in your browser. No account, no tracking.
Debug Radar Scanning
0Healthy
Errors 0Warnings 1Tips 0
alderandoak.shop · Events 6 · Pixels 1
How it works
Three steps from a page to an answer
- 1
Open the panel
Click the toolbar icon on any website. The radar starts listening before the page loads its pixel.
- 2
Use the page
Browse, add to cart and check out. Each pixel event appears the moment it fires.
- 3
Read the radar
The ring shows the health of the page. Open Issues to see what to fix and where.
The three views
Feed, Setup and Issues, one tap apart
Issues
Problems with fixes
Errors, warnings and tips sorted by severity. Each has a one-line fix and a button that jumps to the event.
Setup
Setup at a glance
Pixel IDs, library, consent, limited data use, cookies and whether customer fields are hashed.
What the radar checks
Twelve groups of checks, each with a plain fix
Severity is error, warning or tip. Together they set the score in the ring.
Purchase value and currency
Missing, not a number or not a valid code.
Catalog events
Product IDs and content type are present and well formed.
Parameter names
Misspelled keys and look-alikes that Meta will ignore.
Standard against custom
A custom event that should have been a standard one.
Double fires
The same event sent twice within two seconds.
Event IDs
Missing or reused, so server matching stays possible.
Customer details
Emails and phone numbers in parameters or in the page address.
Hashing
Customer fields that were sent without hashing.
Pixel setup
Odd pixel IDs, a pixel started twice or two pixels at once.
Page views
A page that sent events but never a PageView.
Cookies
The browser cookie missing, or a click ID without its cookie.
Consent
Consent and limited data use, and events sent while consent was revoked.
Private by design
Your data never leaves the browser
The extension reads pixel requests on the page you have open and shows them to you. It makes no network requests of its own, has no account and no analytics.
Read the privacy policy- 14 days of history, kept on your device and cleared on request
- Customer fields reduced to a name and a hashed yes or no
- Export as JSON or CSV, safe to open in a spreadsheet
- Error notifications are off until you turn them on
Speaks 15 languages
The panel follows your browser language, including a full right-to-left layout.
ENESPTFRDEITTRIDVIARHIJATHPLNL
Light and dark
Follows your system or set it yourself in the settings sheet.
FAQ
Questions people ask
How do I test and debug my Meta Pixel?
Open your site and click the toolbar icon to open the side panel. Use the page like a visitor: browse, add something to the cart and go through checkout. Each event appears live. Open the Issues view for the fixes and reload the page to catch events that fire while it loads.
Is it private?
Yes. Everything is processed in your browser. The extension makes no network requests of its own, has no account and no analytics. History stays in extension storage on your device for 14 days and you can clear it at any time. Customer details are never stored: only the names of the fields and whether they were hashed.
Does it check events sent from my server?
No. It only reads what the page sends from the browser. It does not connect to Meta and it cannot see your Events Manager.
Why does a call show as not seen?
The page called the pixel, but no request was observed. The browser, an ad blocker or the consent setting may have stopped it, or it may have been sent in a way the extension cannot see. Treat it as a prompt to look closer.
Which pages work?
Any regular website. Browser pages and the Chrome Web Store are not available to extensions.
Put the radar on your pixel
Add Meta Pixel Debug Radar to Chrome and open it on any page.