Meta Pixel Event Debugger
Overview
Debug your Meta Pixel in a side panel. See every event and parameter as it fires, spot errors fast and get a clear fix for each one.
Is my Meta Pixel firing? What is it actually sending? Why does the Purchase event look wrong in Events Manager? Meta Pixel Event Debugger answers these questions while you browse, in a side panel that stays next to the page you are testing. Open the panel on any website that uses the Meta Pixel, also known as the Facebook Pixel. Every event appears the moment the page sends it, grouped by event name with a counter and a clear OK or error mark. Open an event to read its parameters in a simple two-column list and copy it as JSON to share with a developer or a client. WHAT YOU SEE Events: every pixel event of the page you are on, from page load to checkout. Search them, filter to problems only, group them by event or by page, and look back at earlier visits to the same site. Pixels: each pixel ID found on the page, whether its format is valid, how often it was initialised, which events it sent and which customer fields were passed along. A second card shows the library status, consent state, the Limited Data Use flag and the pixel cookies. Issues: all problems on the page sorted by severity. Each one has a plain sentence that says what is wrong and one line that says how to fix it. A red badge on the Issues icon shows the count. WHAT IT CHECKS The panel looks for missing or malformed values and currencies, product lists that are not in the shape the catalog expects, misspelled parameter names, event names with the wrong capitalisation, events that fire twice, reused event IDs, a missing PageView, a pixel that was never loaded, consent that was revoked and personal data that should not be in the request. Email addresses and phone numbers are masked before anything is saved, so they never reach the history. WORKS WITH THE WAY SITES REALLY SEND EVENTS Pixel requests are caught however the page sends them, including image requests, beacons, fetch calls and the form posts that Meta uses for larger payloads. Single page apps are followed as the address changes, so every route gets its own place in the list. MADE FOR A WORKING DAY History for each site is kept for 10 days on your device and can be cleared for one site or for everything. Download events as a JSON or CSV file for your team. Choose light, dark or follow your system. Turn on optional notifications to hear about new errors without keeping the panel open. The panel speaks 15 languages and follows your browser language. PRIVACY Everything stays in your browser. The extension makes no network requests of its own, has no account, no servers and no analytics. Read the full policy on our website. FREQUENTLY ASKED QUESTIONS How do I test and debug my Meta Pixel? Install the extension, open the page you want to test and click the toolbar icon. Reload the page once so the panel can record it from the start. Then click through the steps you care about, such as adding a product to the cart, and watch the events arrive. Anything the panel finds is listed under Issues with a fix. Does it work on every page? It works on regular websites. Browser pages and the Chrome Web Store cannot be inspected by any extension. Does it check my server events? No. It shows what the pixel sends from the browser, which is the part you can see in the page. Is it affiliated with Meta? No. Meta Pixel Event Debugger is an independent tool. It is not affiliated with, endorsed by or sponsored by Meta Platforms, Inc. Meta and Meta Pixel are trademarks of their owners.
0 out of 5No ratings
Details
- Version1.0.0
- UpdatedNovember 14, 2026
- Offered byMeta Pixel Event Debugger
- Size438KiB
- Languages15 languages
- Developer
Email
gtcvtakmb@gmail.com - Non-traderThis 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
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