Guide for pros · Tracking and analytics
How to diagnose a broken Meta Pixel in 10 minutes: a checklist for tracking pros
By The Microployed teamUpdated 5 min read
The short answer
Start with Meta Ads Data Advisor, the extension formerly called Pixel Helper, on the page that's failing, then confirm what Meta actually received in Events Manager's Overview and Test events. Those two views usually tell you within 10 minutes whether the pixel is missing, installed twice, sending events without value and currency, or double counting because browser and server events aren't deduplicated.
The steps, about 10 minutes
Step 1: Open the failing page with Data Advisor
Turn off your ad blocker for the site, load the page where the problem shows up and click the Meta Ads Data Advisor icon. No badge means no Meta pixel loaded on that page.
Step 2: Check the pixel ID and how many copies load
Confirm the pixel ID matches the one in the client's Events Manager and that it loads only once. A second ID or a duplicate copy explains most inflated numbers.
Step 3: Trigger the conversion
Do the action that should fire the event, such as adding to cart or submitting the form, and watch which events appear and with what status.
Step 4: Read the event parameters
Open the event and look for value, currency and content_ids. Data Advisor flags missing parameters as warnings or errors.
Step 5: Confirm what Events Manager received
Open the pixel's Overview and the Test events tool to confirm the event arrived, and check its Connection Method to see whether it came from the browser, the server or both.
Step 6: Check deduplication
If both the browser and the server send the event, open Event Details and the Event Deduplication tab. A low rate points to missing or mismatched event IDs.
Step 7: Note the Event Match Quality score
Record the score from the Overview page and the recommendations behind it, so the client can see whether tracking works but matches poorly.
Why a fixed diagnostic order saves you time
Checking causes in the same order every time keeps a small pixel job small. When a client says their pixel is broken, they usually mean that Ads Manager shows no conversions, shows too many, or stopped matching the store after a theme or app change. Each of those has a short list of causes, and working through them in a set order keeps you from spending 40 minutes in theme code on a problem that Events Manager would have explained in two. The steps above move from what the browser sends, to what Meta receives, to how well Meta can use it, which is also the order in which problems tend to pile up.
Ten minutes is enough to find the cause, though not always to fix it. Treat the diagnosis as its own small deliverable: a short note that says what you checked, what you found and what the fix will take. A client who sees that note before anything changes understands what they're paying for, and it gives you a clean point to requote if the job is bigger than the brief suggested.
What to ask the client for before you start
You need a URL where the problem shows up, the pixel ID the client expects to see, and access to Events Manager for that pixel. Ask to be added as a partner or user on the pixel through Business settings instead of accepting anyone's login, and make a note to have that access removed when the job is approved. If the issue involves purchases, ask whether you may place a test order and how it should be cancelled or refunded, because a real confirmation page is often the only place the Purchase event can be seen firing.
How to read what Data Advisor shows
Meta has renamed Pixel Helper to Meta Ads Data Advisor, and it still runs as a free extension in Chrome and Microsoft Edge with the same diagnostic features. A badge with a number means a pixel is present and shows how many events fired on that page, while no badge means no Meta pixel loaded at all. Each pixel and event gets a status of Active, Warning, Inactive, Error or Auto-detected. Turn off your ad blocker for the client's site before you trust any of it, since a blocker can make a healthy pixel look absent.
The findings that matter most on a first pass are a pixel ID you don't recognize, two copies of the same pixel, base code that sits outside the page's <head>, and events missing value, currency or content_ids. An unfamiliar ID usually belongs to an old agency or an app that installed its own pixel, and it explains a lot of complaints that the numbers look wrong. Turn on Show all events when you walk through a funnel such as product page, cart and checkout, because it keeps events from the whole browser session instead of resetting on each page.
One limit is easy to forget: Meta notes that button-click events and custom conversions may not show in Data Advisor even when they track correctly, so if the client's main conversion is one of those, confirm it in Events Manager before you call it broken.
How to check what Meta actually received
Events Manager is the record of what arrived, whatever the browser seems to show. Open the pixel's Overview to see events received before deduplication, events processed, and the Connection Method for each event, which tells you whether it came from the browser, the server or both. Meta says events normally appear there within 20 minutes of being sent, so a test you ran a minute ago may only be visible in the Test events tool for now.
If an event arrives through both the browser and the Conversions API, open Event Details and then the Event Deduplication tab. A low deduplication rate usually means the browser's eventID and the server's event_id don't match, or one side sends no ID at all. Meta only merges pairs that share the same event name and ID and arrive within 48 hours of the first one, so a mismatch here quietly doubles every conversion the client reports.
What to check when the pixel works but results still look wrong
Sometimes every event fires once with full parameters and the client is still unhappy with the numbers. Look at the Event Match Quality score on the Overview page, which runs from 1 to 10. Meta recommends aiming for 6.0 or higher, and clicking the score lists the customer information that would raise it. A low score means Meta can connect fewer events to people, which weakens ad delivery even though tracking technically works.
Also look at the landing pages behind the ads. Meta's pixel support docs point out that URL shorteners and vanity URLs can break when the click ID is added, sending visitors to a 404, and that some sites reject unexpected query parameters such as fbclid. Clicking through from a live ad, or adding ?fbclid=test to the landing page URL yourself, takes a few seconds and rules out both.
How to write up what you found
Finish with three or four lines the client can read without knowing what a pixel is: what's broken, why it happened, what you'll change and how long it will take. If the fix is a one-line change you can make on the spot, say so and quote it. If it means removing an app's tracking or adding the Conversions API, quote that as a separate job using your per-minute rate, with a larger buffer for anything that needs a deploy or a test order. When double counting turns out to be the cause, our guide to Meta Pixel purchase events firing twice explains it in plain terms, which makes it a useful page to send along with your note, and the tracking checker gives the client a quick way to see the result for themselves.
Get small jobs without writing proposals
Microployed sends small jobs in your skill when you turn on availability. There are no proposals to write, and you keep 100% of your quote. Joining is free while we're in beta.
Join free as a proThe next level up
Get tracking jobs at your rate without writing proposals
If you can run this checklist, you can clear a lot of small tracking jobs in a week. On Microployed you turn on your availability or set weekly hours, our team reviews your profile, and jobs in your skill are offered to you without proposals. You keep 100% of what you quote.
Join free as a proQuestions people ask
Is Meta Pixel Helper still available?
Yes, under a new name. Meta now calls it Meta Ads Data Advisor, and it runs as an extension in Chrome and Microsoft Edge with the same diagnostic features as before.
How long do events take to show in Events Manager?
Meta says events usually appear on the Overview page within 20 minutes of being sent. Use the Test events tool when you need to watch a test event arrive as you trigger it.
Why does Data Advisor show no pixel when the client says it's installed?
Check your own ad blocker and privacy settings first, since they can block the pixel. After that, the usual reasons are a pixel installed on only some pages or a tag manager rule that didn't fire on the page you're testing.
What Event Match Quality score is good enough?
Meta recommends aiming for 6.0 or higher on its 1 to 10 scale. Clicking the score in Events Manager shows which customer information would raise it.
Should I charge for the diagnosis separately from the fix?
Quoting the diagnosis as its own small job and quoting the fix once you know the cause keeps each quote accurate, and it saves you from guessing at a fix you haven't scoped yet.
Sources
Checked against these pages on .
- Meta Ads Data Advisor, formerly Meta Pixel Helper (Meta for Developers) (opens in a new tab)
- Meta Ads Data Advisor (Meta for Developers) (opens in a new tab)
- Verifying your setup, Conversions API (Meta for Developers) (opens in a new tab)
- Handling duplicate Pixel and Conversions API events (Meta for Developers) (opens in a new tab)
- Meta Pixel support (Meta for Developers) (opens in a new tab)