Meta Pixel Test Events Verification Checklist

This avoids cached consent, old cookies, and ad-blocker state from a previous session.

Tools such as uBlock Origin, Privacy Badger, or Brave Shields can block connect.facebook.net.

Keep it visible so you can see events arrive in real time as you complete each step.

If fbq already exists, a previous consent state or another Pixel installation may be present. Clear cookies/storage and reload.

Before you click Accept/Accept All, no requests to connect.facebook.net should appear.

The on-page Pixel Debug Panel reads the same consent state as the Pixel loader.

After rejecting, window.fbq must remain undefined and no Meta network calls should be made.

If you choose 'Manage Preferences', turn on the Marketing toggle and save.

This confirms the base code loaded after consent was granted.

In the Pixel Debug Panel, the Pixel ID should match exactly and Initialized should show true.

It can take 5–30 seconds to show up. The event name is 'PageView' and the Pixel ID should match.

Accept Marketing cookies if you have not already done so in this session.

The page content should update without a full white-screen reload.

Because this is a React SPA, a new PageView must fire on every route change after consent.

Each history change should produce exactly one additional PageView, not duplicates.

These funnel events are part of the Europe Jobs portal and should appear after the landing PageView.

The preference center should open and show your current choices.

The Pixel Debug Panel should update to show advertising consent = false.

Test Events should stop receiving PageView or funnel events from this browser.

In Application → Cookies, filter for '_fb'. After withdrawal those values should be cleared.

Use a real phone or Chrome DevTools device emulation. Some mobile browsers block third-party scripts more aggressively.

SPA route changes on mobile must behave the same as on desktop.

Look for messages such as 'Refused to load the script' or 'fbq is not defined'.

Search the page source for the Pixel ID; it should appear only once in the base code and once in the SPA tracker.

It shows initialized status, consent state, event counts, and a timestamped event log.

Include the browser, any extensions active, and what you see in Test Events.