Meta Pixel events not showing in Events Manager
Leads or purchases are happening on the site, but Events Manager shows no events for the Pixel, far fewer than expected, or a gap that started on a specific day.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
Most missing Pixel events come down to the Pixel not loading on the page where the conversion happens, or a consent tool holding it back. Start by opening the conversion page with Meta Ads Data Advisor (the extension formerly called Meta Pixel Helper) and the Test Events tool in Events Manager, then complete a real test conversion and watch whether the event arrives and under which Pixel ID.
1. The Pixel is not loading on the page where the conversion happens
The base code was left off a template, removed in a redesign, or lives in a Google Tag Manager container that was never published. This is the most common cause and usually affects one page type, often the thank-you page.
How to check
- 1Open the conversion page in Chrome or Edge with Meta Ads Data Advisor installed. No badge on the icon means no Meta Pixel was found on the page.
- 2In Events Manager, go to
Data Sources, select the Pixel, openTest Events, enter the site URL and complete a test conversion. Note which events arrive. - 3If the Pixel runs through Google Tag Manager, open
Preview, repeat the conversion and confirm the Meta tag shows underTags Firedon the right page or event.
How to fix
- 1Install the base code on every page. Meta's Data Advisor documentation lists Pixel code missing from the page head as a common setup issue.
- 2If you use Google Tag Manager, check the trigger matches the page or event that actually confirms the conversion, then publish the container.
- 3Repeat the test conversion and confirm the event appears in
Test Eventsbefore closing the ticket.
2. The consent tool is pausing the Pixel and never releasing it
Meta's consent API pauses Pixel fires after fbq('consent', 'revoke') and resumes them after fbq('consent', 'grant'). If the consent platform never sends the grant, or puts Meta in the wrong category, events stay paused even for visitors who accepted.
How to check
- 1Open the site in a fresh private window, accept all cookies, and complete a test conversion while watching Data Advisor and
Test Events. - 2Repeat in another private window and decline. You should see no Pixel events in the decline path and events in the accept path.
- 3In the browser developer tools, filter the Network tab for
facebook.com/trto see whether Pixel requests leave the browser at all. - 4In Google Tag Manager, check the Meta tag's consent settings and which consent type it waits for.
How to fix
- 1Make sure the consent platform calls
fbq('consent', 'grant')(or updates the tag manager's consent state) as soon as the visitor accepts, on the same page, not only on the next page load. - 2Put Meta in the consent category your banner actually asks about, usually marketing or advertising.
- 3Expect fewer events from visitors who decline. That is consent working as intended, not a bug to work around.
3. Events are going to a different Pixel or dataset
Agency accounts often carry an old Pixel, a client's second Pixel in another business portfolio, or a Conversions API integration that was set up with a different dataset ID. The events exist, just not where you are looking.
How to check
- 1In Data Advisor, look at which Pixels it found on the page and compare each ID to the Pixel open in Events Manager.
- 2For Conversions API events, compare the Pixel ID in the request endpoint with the dataset ID in Events Manager.
- 3Check the Pixel's
Settingspage for any domain allow list or block list that excludes the client's domain.
How to fix
- 1Point every browser tag and server integration at the one Pixel the ad account optimises for, and remove stray Pixels from the site.
- 2If the Pixel belongs to a different business portfolio, share it properly rather than installing a second one.
4. The event fires before the Pixel is ready, or at the wrong moment
A fbq('track', 'Lead') call that runs before fbq('init') has nothing to send through. Forms that submit by AJAX and never load a thank-you page, or redirects that leave the page instantly, cause the same silence.
How to check
- 1In Google Tag Manager
Preview, check the order: the base Pixel tag must fire before the event tag on the same page. - 2Watch Data Advisor on the thank-you page or after an AJAX submission. If the base Pixel loads but no
LeadorPurchaseevent shows, the event trigger is the problem. - 3Confirm the event name is a standard event spelled exactly as Meta lists it, such as
Lead,PurchaseorCompleteRegistration, or a custom event you have actually set up.
How to fix
- 1Use tag sequencing in Google Tag Manager so the base Pixel tag fires first, or fire both from one tag.
- 2Trigger the event on a confirmed successful submission (a thank-you page, a success message or a data layer event pushed by the form), not on a button click.
5. Browsers and ad blockers stop the Pixel, and there is no Conversions API
Meta's own checklist warns that browser settings and privacy tools can block the Pixel. A browser-only setup will always miss some conversions, which is why Meta recommends using the Conversions API in addition to the Pixel.
How to check
- 1Run the test conversion with an ad blocker on and off. If the event only appears with the blocker off, the setup is browser-only.
- 2In Events Manager, open the Pixel's
Overviewand look atConnection Methodto see whether any events arrive through the Conversions API.
How to fix
- 1Add the Conversions API and send the same events from the server, with a shared
event_idfor deduplication. - 2For website events, send
action_sourceset towebsite,event_source_url,event_timeandclient_user_agent. Meta listsclient_user_agentandevent_source_urlas required for website events.
6. Conversions API requests are rejected, or you are checking too soon
If any event in a request has an event_time more than 7 days old, Meta rejects the whole request and processes none of it. Invalid payloads return a 4xx response with little detail, so failures go unnoticed unless someone logs them.
How to check
- 1Log the HTTP response for each Conversions API request. A 2xx response means the payload was accepted; a 4xx means it was not.
- 2Send a test request with a
test_event_codefromTest Eventsand confirm it appears there. - 3Allow time before declaring events missing. Meta says production events can be verified in Events Manager within 20 minutes, and the
Event Freshnesstab inEvent Detailsshows the typical delay.
How to fix
- 1Fix the invalid fields and resend the batch. Meta says events already stored are dropped as duplicates on a retry, so resending the full batch is safe.
- 2Retry requests that fail for non-client reasons such as timeouts.
- 3Remove
test_event_codefrom production payloads. Meta says those events are not dropped, but the field is meant for testing only.
Stop it happening again
- Run a test conversion with
Test Eventsopen after every site release, form change or consent tool update. - Keep one documented Pixel per client, with its ID and owner, and remove any others from the site.
- Log Conversions API responses and alert on 4xx errors instead of relying on someone noticing a drop.
- Test both the accept and decline paths of the consent banner each time it changes.