If your Meta tracking doesn't work as expected, this article helps you test it and find the cause. Start with the test, then go to the section that matches what you see in Meta.
ℹ️ Haven't set up the integration yet? Follow How do I set up the Meta Pixel integration (Pixel & CAPI) for my funnel? first, or watch the step-by-step video.
TL;DR
Test first: use your live funnel URL, accept all cookies, turn off your ad blocker, and wait 30–60 minutes before you check Meta Events Manager.
No events at all: check your access token, your Pixel ID, the integration toggle, and that you republished your funnel.
Some events missing: visitors who decline cookies send nothing, and Lead only arrives if you mapped it.
Numbers look wrong: check that the same conversion isn't mapped twice.
Only the Pixel or only the Conversions API works: check your access token, your Meta Business verification, and your ad blocker.
How do I test my Meta integration?
Before you test, make sure that:
you use your live funnel URL. The preview doesn't send events to Meta.
you cleared your browser's cookies and cache, reloaded your funnel, and clicked Accept all cookies. Your browser remembers if you declined cookies before, and then the Pixel doesn't fire.
your ad blocker and VPN are turned off. They block your tracking and Meta Pixel Helper.
you give Meta 30–60 minutes. You can see when events last arrived under Last updated in Events Manager.
How do I test with Meta Pixel Helper?
Meta Pixel Helper is a Chrome extension that shows whether a Meta Pixel fires on a page.
Install the Meta Pixel Helper extension in Chrome.
Open your browser's extension settings, click Details next to Meta Pixel Helper, and set Site access to On click. This way, the extension reloads your funnel and detects the Pixel.
Open your live funnel and click the Meta Pixel Helper icon.
Check that your Pixel ID and the Page Viewed event appear. If they do, your Pixel works.
How do I test with Test Events in Events Manager?
In Meta Events Manager, select the Pixel connected to your funnel and open Test events.
Copy the test code, for example TEST64801.
In Perspective, open your funnel, click Apps, and then Meta (Facebook & Instagram).
Open the Account dropdown and click the gear icon next to your account.
Paste the code into Test event code, click Save, and republish your funnel.
Open your live funnel and go through it, accepting all cookies.
Check Test events in Events Manager. The events you triggered appear there.
ℹ️ Important: The test event code is saved on your tracking account, so it applies to every funnel that uses this account. Remove it as soon as you're done testing, and republish the funnels Perspective asks you to.
Why don't any events arrive in Meta?
Test as described above first. If Events Manager still shows no events after 60 minutes, check these points in order:
Access token: without an access token, no events reach Meta through the Conversions API. In Perspective, open Apps → Meta (Facebook & Instagram), click the gear icon next to your account, and check that Access Token is filled in. If it's empty, generate one as described in How do I set up the Meta Pixel integration (Pixel & CAPI) for my funnel?
Pixel ID: in the same window, check that the Pixel ID matches the ID in Events Manager, with all digits.
Integration on and funnel republished: in Apps, the Meta integration needs to be switched on. Republish your funnel after every change to your tracking.
Custom events confirmed: Meta sometimes asks you to confirm new custom events before it lists them.
Meta Business verified: if the Conversions API connection in Events Manager shows Connection pending, your Meta Business account is probably not verified. Meta only accepts Conversions API data from verified businesses. Complete the verification in Meta Business Manager with your legal business name, address, and phone number. Once Meta approves it, the connection leaves "pending".
Only one Pixel: add your Pixel only through the Meta integration. If your Pixel is also in Google Tag Manager or in your funnel's header code, or the AI chat added pixel code to your funnel, remove it. Two Pixels can block each other.
Domain: If you limited your Pixel to certain domains in Meta, add your funnel's domain there. The Meta integration in Perspective links to this under Whitelist your domain. Meta also sometimes blocks tracking on Perspective's standard domain. If your funnel runs on the standard domain, connect your own (sub)domain and verify it in Meta: How can I verify my domain on Facebook?
Why are some Meta events missing?
Visitors who decline cookies: if your funnel has a cookie notice and a visitor declines it, nothing is sent to Meta for that visitor. That's why Meta usually shows fewer events than Perspective.
Lead events missing: Meta only gets Lead events if you mapped Lead. In Apps → Meta (Facebook & Instagram), map Lead to the button that submits your form, then republish your funnel. The Lead event on the button only fires when the form is submitted successfully. Without a mapping, Meta still gets the automatic events, such as Page Viewed.
Button events not in Pixel Helper: events on buttons fire while the next page loads, so Pixel Helper often doesn't show them. Check them in Events Manager instead.
No standard PageView event: if Events Manager shows events like "Page Viewed: page_e3ia8k" instead of PageView, your funnel sends a separate event for each page. That's expected and doesn't mean your tracking is broken. To build audiences or custom conversions from page visits, use these Page Viewed events. See How can I create Meta Custom Audiences from my funnel? and How can I track Custom Conversions in Meta?
Why do events arrive, but my numbers in Meta look wrong?
Duplicate leads: if the same conversion is mapped in two places, for example Lead on the button and on the thank-you page, Meta counts it twice. Map Lead only to the button that submits your form. A Lead on the thank-you page also fires again every time someone reloads or revisits the page.
"Events not deduplicated" warning: this is usually a timing issue and clears on its own within 6–12 hours. See Which warnings in Meta Events Manager are expected? below.
Fewer leads in Meta than in Perspective: declined cookies, attribution windows and delays in Ads Manager can all cause differences. Learn more in Why doesn't the number of leads in Perspective match Meta Ads Manager?
Why does the Conversions API work, but the browser Pixel doesn't (or the other way round)?
Browser events arrive, server events don't: check that your access token is filled in (point 1 above). If Meta shows an authentication error, your Pixel and access token don't match, for example because the token belongs to a different ad account, the Pixel was deleted, or the token is corrupted. Generate a new token in Events Manager for the same Pixel and paste it under Access Token. If the connection shows Connection pending, verify your Meta Business account (point 5 above).
Server events arrive, browser events don't: ad blockers and VPNs block the browser Pixel, while the Conversions API usually still sends events from our server. That's expected for some visitors. When you test, turn off your ad blocker and VPN. Also check that your Pixel isn't installed a second time (point 6 above).
Which warnings in Meta Events Manager are expected?
Meta Events Manager sometimes shows warnings even though your tracking works. With the native integration, these are expected:
Missing IP address: Perspective doesn't collect IP addresses, so Meta matches your events through the other data. Learn more in What data does the Meta integration send to Meta?
Events not deduplicated: browser and server events reach Meta at slightly different times. Meta can show this warning before both copies of an event have arrived. It usually disappears on its own within 6–12 hours.
No standard PageView event: if you see "Page Viewed: <URL ending>" events instead of PageView, that's expected. See Why are some events missing? above.
Low Event Match Quality: the score shows how well Meta can match events to people, not how good your leads or your tracking are. Learn more in What is Event Match Quality in Meta & how to improve it?
If a warning stays longer than 12 hours, contact our support team with the details listed below.
What should I send support if it still doesn't work?
If you've gone through all these points and your tracking still doesn't work, contact our support team and send:
your account email address
your funnel name and the link to your live funnel
whether your funnel runs on Perspective's standard domain or your own domain, and whether that domain is verified in Meta
whether your access token is filled in
which event you mapped, and to which button or page
whether you republished your funnel after your last tracking change
how you tested: live URL or preview, cookies accepted, ad blocker and VPN off
FAQ
Does the preview of my funnel send events to Meta?
Does the preview of my funnel send events to Meta?
No. Only your live funnel sends events to Meta, so always test with your live funnel URL.
How long does it take until events show up in Meta Events Manager?
How long does it take until events show up in Meta Events Manager?
Usually 30–60 minutes. You can see when events last arrived under Last updated in Events Manager.
Why doesn't Meta Pixel Helper show my Lead event?
Why doesn't Meta Pixel Helper show my Lead event?
Events on buttons, such as Lead on the button that submits your form, fire while the next page loads, so Pixel Helper often doesn't show them. Check them in Meta Events Manager instead.









