Meta Pixel on your website.
Does it send before anyone is asked?
The Meta Pixel (formerly Facebook Pixel) loads fbevents.js, sets the _fbp cookie and reports every page view to facebook.com/tr. Whether that happens before the choice depends only on how it is built in.
Your account after the first check

Sample shop. Every point opens its fix with the steps for your tool.
Where the pixel loads past the banner
The banner only holds the pixel back if it knows the code. Often it sits in a second place the banner does not cover.
- 01
Pixel code hard-coded in the theme
The base code with fbq('init', …) sits in the theme header or a custom code field. It loads with every page, regardless of the banner.
Art. 5(3) Directive 2002/58/EC
- 02
A plugin or app adds it again
The Meta plugin for WooCommerce, a shop app or a marketing plugin adds the pixel a second time. One waits for consent, the other does not.
Art. 5(3) Directive 2002/58/EC
- 03
Pixel tag in Tag Manager without a condition
If the Meta tag in Google Tag Manager fires on all pages without a consent check, it sends before the choice, even when the banner is set up correctly.
Art. 5(3) Directive 2002/58/EC
- 04
Facebook content next to the pixel
A like box, embedded posts or Messenger chat load from connect.facebook.net. They belong behind consent too, but they are not the pixel.
Art. 5(3) Directive 2002/58/EC
Step by step
Measure
Open the page in a private window, developer tools (F12), Network tab, filter for “facebook” and reload without touching the banner. Under Application, Cookies look for _fbp. The report does this for every page it reads and names where the pixel comes from.
One installation only
Find every place where fbq('init' appears (theme, plugins, apps, Tag Manager) and keep only one, ideally in the banner tool or Tag Manager.
Only after consent
In the banner tool assign the Meta Pixel to the marketing category. If you add the code yourself: fbq('consent', 'revoke') before fbq('init', …) on every page, fbq('consent', 'grant') only after consent. According to Meta this only pauses sending; whether fbevents.js still loads shows in the measurement.
Measure again
Check again without consent and after “Reject”. Only when no request goes to facebook.com/tr and no _fbp appears does the pixel no longer send before the choice.
Questions
Which cookies does the Meta Pixel set?
Mainly _fbp, valid for 90 days according to Meta, and _fbc when someone arrives from a Facebook ad. Before the choice they only appear if the pixel loads without waiting for consent.
Does the scan see the Conversions API?
No. The Conversions API sends from your server to Meta, not from the browser. The scan measures what the visitor's browser loads and sends.
How does this work in my banner tool?
See the guides for <a href="/en/guides/google-tag-manager-consent">Google Tag Manager</a>, <a href="/en/guides/cookiebot-not-blocking">Cookiebot</a>, <a href="/en/guides/usercentrics-not-blocking">Usercentrics</a>, <a href="/en/guides/borlabs-cookie-not-blocking">Borlabs Cookie</a>, <a href="/en/guides/real-cookie-banner-not-blocking">Real Cookie Banner</a>, <a href="/en/guides/complianz-not-blocking">Complianz</a> and <a href="/en/guides/shopify-cookie-banner-check">Shopify</a>.
What a scan shows
It opens your website without consenting, also reads subpages, then clicks Reject and measures again. If the Meta Pixel sends in advance, the report names the page, where it comes from and the fix for your banner tool. Right away for your website: cookie check.
As of 15 November 2026. We name the reference so you can read it yourself; this is not legal advice.
More guides
- Cookies before consent: what ePrivacy requires
- Price information in web shops: unit price and shipping
- European Accessibility Act checker for web shops (WCAG)
- Cookiebot not working or not blocking?
- Usercentrics not blocking?
- Borlabs Cookie not blocking?
- Real Cookie Banner not blocking?
- Complianz not blocking?
- Check your cookie banner yourself in three steps
- Google Fonts self-hosted but still loading?
- Dark patterns in online shops: five patterns and the fix
- EU withdrawal button 2026: what your shop needs
- Unit price and the “order with obligation to pay” button
- GPSR: manufacturer information in your web shop
- OneTrust not blocking cookies?
- CookieYes not blocking or not working?
- Wix cookie banner check: does it really block?
- GTM consent: fire tags only after consent in Tag Manager
- Google Maps embed and GDPR: load the map only after a click
- YouTube embed and GDPR: load the video only after a click
- Google Analytics without consent?
- TikTok Pixel before consent?
- Hotjar before consent?
- Microsoft Clarity consent mode: check what it sends
- Google reCAPTCHA and GDPR: load it only on the form page
- HubSpot cookie banner not showing?
- Shopify cookie banner check: does it really block?
- Google Consent Mode v2 checker: test and set it up
- Cookie checker for websites: free, with the reject test
- Security headers check: free website security checker