How to check whether Meta Pixel fires before consent
Your shop has a cookie banner, but Meta Pixel may still load before anyone clicks it. Then the banner guards nothing and the risk sits with the shop operator. Here is how to check it without a developer, and why it happens.
In short
- Meta Pixel is an advertising technology and may run only after consent. If it sends data before the click, the consent is only for show.
- You can see it in a private window: search the network requests for
facebook.com/trand look for the_fbpcookie, both before you touch the banner. - The cause is usually code in the theme, a plugin, or Google Tag Manager without a consent condition. The fix always means tying the pixel to the visitor’s choice.
Why it matters
Meta Pixel sends data about visitor behaviour to Facebook and Instagram and stores a cookie that can link the visitor to their account. It is an advertising technology, so under the ePrivacy Directive (Article 5(3)) and the GDPR it needs prior consent. National data protection authorities and the EDPB guidance on cookies take the same view. See also Consent Mode v2: how to check it on your shop.
A banner that asks for consent while the pixel has already fired is worse than no banner: the site tells the visitor it is asking, and sends the data in the meantime. A few minutes and a browser are enough to check.
Step-by-step check
We use Chrome. Other browsers have similar tools under slightly different names.
Open a private window
Press Ctrl+Shift+N (Cmd+Shift+N on a Mac). A private window has no stored choices or cookies, so it behaves like a new visitor. Turn extensions off, as they can change the result.
Open DevTools before the shop
Press F12, go to the Network tab and tick Preserve log. Only then enter your shop address. Otherwise you miss the first requests.
Do not click the banner
Wait for the page to load and the banner to appear. Choose nothing. In the Filter box type
facebook, and thenfbevents.Look for requests to Meta
The file
fbevents.jsloads fromconnect.facebook.net. Loading the script alone does not mean data was sent; what matters are requests tofacebook.com/trwith the parameterev=PageView. If they appear, the pixel sends data before consent.Check the _fbp cookie
Go to the Application tab, open Cookies on the left and select your shop address. The
_fbpcookie is created by Meta Pixel. If it is there before you clicked the banner, the pixel stored data without consent.Use Meta Pixel Helper
The Meta Pixel Helper extension for Chrome shows an icon with the number of pixels, their IDs and the events sent. Install it and open the shop again in a normal window with cookies cleared. If you see the pixel and a PageView event before any choice on the banner, it is the same finding as in DevTools. Also note whether the pixel is installed twice, for example under two different IDs.
Repeat with reject
Clear cookies, load the shop again, click Reject and browse a category, a product and the cart. Requests to
facebook.com/trand the_fbpcookie must not appear, not even later.
Why it happens
On online shops a pixel that runs before consent almost always comes from one of three things:
- Code pasted into the theme. Someone added the pixel to the header, to the custom code section of the admin or to a theme file, and the banner does not know about it.
- A plugin or app. A Meta, feed or marketing plugin adds the pixel in its own way, with its own settings, and the banner may not control it.
- Google Tag Manager without consent conditions. The Meta Pixel tag fires on “All Pages” with no consent requirement. Consent Mode controls Google tools only; every other tag has to wait for consent on its own.
A combination is common too: the pixel is set up correctly in GTM, but an old copy stayed in the theme. After a reject, one copy disappears and the other keeps sending. The same logic for Google is in Consent Mode v2: how to check it on your shop.
What the fix involves
First find every place the pixel loads from: the theme, custom code sections, apps and plugins, and GTM. Then remove the code from those places and let the pixel load from one place only, which waits for consent in the marketing category. In GTM this is a consent requirement on the tag; for plugins it is the plugin’s consent setting if it has one, or replacing the plugin.
After the fix, check the other side too: after consent the pixel works, and events (ViewContent, AddToCart, Purchase) are sent once, not twice. Otherwise the fix breaks ad measurement.
What to check besides the pixel
Meta’s pixel is often the first technology that runs outside the banner, but not the only one. Check other tags the same way. In the Network tab filter for googleads, doubleclick, tiktok, hotjar and similar. For every request that leaves before you click the banner, note where it was loaded from. For Google, check whether Consent Mode is working and sending only limited signals without cookies, instead of blocking everything. Tags from other vendors must not fire before consent at all.
When you may not need to worry
If the shop uses no pixel, you found neither requests to Meta nor _fbp in DevTools, and nobody added a pixel quietly, there is nothing to fix. Repeat the check after every larger change to the shop, after installing a new plugin and after changing campaigns, because pixels like to return with a new plugin. It also helps to record who added a pixel and when, and to check explicitly that a previous agency or ad vendor left no code behind. Old pixels nobody uses should be removed completely, not just switched off in the ad account. Keep the result of the check, for example as a screenshot, so you can show the state later.
What to do about it
You can have the finding confirmed as part of the free audit. If the pixel runs before consent, we fix it as fixed-price work, described on the cookie banner and Consent Mode page: the fix costs €59 excl. VAT and you pay only after we verify the result with the same steps as in this guide.
Frequently asked questions
Is it enough if the pixel may not send events but the script loads?
What counts is whether data is stored on the device and sent. The safe approach is not to load the script at all until the visitor consents. A script that loads early is also a common source of errors.
What if I use the Meta Conversions API?
Sending from the server is still processing data about the visitor, so consent must be respected there too. It does not replace checking the pixel in the browser.
How often should I check?
After every theme change, plugin installation or GTM change. If you would rather not watch it yourself, monthly monitoring can do it.
Order a free audit
Enter the shop address and your e-mail. We send the report in two working days. We use your details only to answer this request.
- No access and nothing to install
- The report is yours even if you order nothing
- A person answers, not a bot
Thank you, we have your request
We will send the report to your e-mail in two working days.
Sending did not work
Please send us the request by e-mail. The text is ready.
info@lyneon.eu
More guides
- Consent Mode v2: how to check it on your shop5 min read
- How to set up DMARC (and SPF and DKIM) for your shop5 min read
- European Accessibility Act: what it means for online shops5 min read
- Why GA4, Google Ads and your shop admin show different conversions6 min read
- Disapproved products in Google Shopping: the most common reasons5 min read
- Core Web Vitals for online shops: LCP, CLS and INP explained5 min read
- Why Google does not index your shop pages and what to do6 min read
- Why e-mails from your shop go to spam6 min read