Home / Meta Pixel debugger

The Meta Pixel debugger that sees the rest of the page

Knowing the pixel fired is the easy part. The questions that cost money are the next ones: did the server send the same event, under the same ID, and did either of them have consent.

A pixel helper answers one question well — is a Meta Pixel on this page and what did it just send. That question stopped being sufficient the day most advertisers added the Conversions API, because from then on every browser event has a server twin, and whether those two are one conversion or two comes down to a single parameter.

Tag Master decodes the /tr call like any other hit: pixel ID, event name, value, currency and the eid that the Conversions API will or will not match against.

The parameter that decides whether one purchase is one

Meta deduplicates a browser event against a server event when both carry the same event name and the same event ID. Miss the ID on either side and the same order is counted twice: the reported conversion count inflates, the cost per acquisition halves, and the campaign that looks best is the one being double-counted hardest.

The failure is quiet in both directions. An ID present in the browser and absent on the server looks correct here and duplicates in the reports. An ID that is regenerated per page load — a timestamp, a random value — is present on both sides and matches on neither. The longer guide works through what the ID has to be and the five ways it goes wrong.

Test Events, without the copy and paste

Meta's Test Events tool needs a code from Events Manager attached to the traffic you are generating. Getting it there usually means pasting it into a tag, testing, and remembering to take it out — and the forgetting is how a test code reaches production. Switching the mode on for the tab, and off again when you are done, removes that step. TikTok, Snap, Microsoft UET and five others work the same way and are in the same list.

Consent, which the pixel does not read

Meta does not implement Google's Consent Mode. The pixel does not receive ad_storage, does not know what the visitor answered, and fires whenever its tag is on the page. Gating it is entirely the consent tool's job, and when that gating is wrong the Google tags stay impeccable while the pixel keeps sending purchases under a denied answer.

Reading the pixel next to the consent sequence is the only way to see that from the browser. It is also the single most common serious finding on a site that believes it is compliant.

Where a dedicated pixel tool still wins

Anything on Meta's side of the wire. Whether Events Manager accepted the event, whether the domain is verified, whether an event is eligible for a given optimisation, how the matching quality score moved after a change — none of that is in the request, and no browser extension can see it. Send the event, read what left the browser, then confirm in Events Manager that it landed. Different halves, different tools.

Questions

Is there a free Meta Pixel debugger for Chrome?

Yes. Tag Master is free with no account, and decodes the Meta Pixel alongside 61 other platforms rather than on its own. Meta's own Pixel Helper is free too — it answers what the pixel sent, and stops there.

How do I check CAPI deduplication from the browser?

Confirm the browser event carries an eid, and that the value is the order or transaction identifier rather than something regenerated per page load. The server half has to be confirmed in Events Manager; no extension can see it.

Why is my Meta Pixel not firing?

Read the network rather than the tag. The three common causes are a trigger that never matched, a consent tool blocking the tag, and the event firing inside an iframe the page does not control — and all three look identical from the tag setup.

Does the Meta Pixel respect Consent Mode?

No. Consent Mode is a Google protocol and Meta does not read it. If the pixel is meant to be blocked before consent, the consent tool has to be the thing blocking it, and whether it did is visible only in the requests.

Can I turn on Meta Test Events without editing a tag?

Yes. The test mode is switched on for the tab being debugged and off again afterwards, so no test code is left behind in a container to reach production.

Guides

The longer form, on the parts that catch people out.

• Meta Pixel and CAPI: why purchases are counted twice — How deduplication actually works, what eid looks like in the browser request, and the five mistakes that turn a single order into two conversions.
• Test Events for TikTok, Snap, UET and five more — Everyone knows about DebugView and Tag Assistant. Every other platform has the same thing, switched on by a cookie almost nobody documents — here is the full list.
• Finding every tracking tag on a page — Why a tag scanner that reads the HTML misses tags loaded after the page does, and how to get the real list by reading the requests instead.
• Tracking inside an embedded widget — A booking widget or payment step in an iframe has its own dataLayer. Why Preview shows one event where the log shows two, and what crosses the boundary.
• Testing tracking without polluting production analytics — Test purchases end up in real reports. How to stop the hits at the browser, in one tab only, and still see everything that would have been sent.
• Debugging Consent Mode V2: gcs, gcd and the violations nobody catches — Read consent parameters straight from the hits, tell a default apart from an update, and find the vendors that fire regardless of what the banner says.

The other term pages: GTM debugger, GA4 debugger, dataLayer inspector, Consent Mode checker