CookieYes: Reject clicked, but the Meta Pixel keeps firing
Visitors click Reject All on your CookieYes banner, yet Meta Pixel requests continue. How to find what loads the pixel and make it respect the choice.
Lukas Kontur · · 9 min read
A visitor clicks Reject All on your CookieYes banner. The banner closes, but the Meta Pixel keeps sending page views and events to Meta, and a scan reports "trackers still active after reject". In most cases, the pixel is loaded in a way CookieYes does not control. This guide shows you how to find out which way, and how to bring each one under the visitor's choice.
The symptoms
- A scan report lists trackers still active after reject with requests to
facebook.comorconnect.facebook.net, sometimes also cookies still present after reject with_fbp. - In your own browser, the CookieYes consent cookie
cookieyes-consentrecords a rejection, but requests to Meta keep appearing. - Meta Events Manager still receives page views from visitors you expected to be blocked.
You are not alone with this. When we clicked Reject on EU websites, non-essential cookies were still there after the reject on 10,848 sites, 48.3% of the 22,445 sites with a conclusive test (reject button study). That number covers all consent tools, not CookieYes in particular.
How to check it yourself
You need Chrome and about five minutes. Start from a clean visitor every time.
- Open a new private window (three-dot menu, "New Incognito window") and press F12 to open DevTools.
- In the Network tab, tick Disable cache (Chrome DevTools: Network reference).
- Load your site and click Reject All on the banner.
- Clear the Network list with the "clear" icon, type
facebookin the filter box and reload the page. - Open a second page, for example a product page, and watch the list.
- In Application, Cookies, find
cookieyes-consent. Its value lists the categories, for exampleadvertisement:no, so you can confirm the rejection was stored. Look for_fbpnext to it. - If requests to
facebookappear, click one and open the Initiator tab. Note which file started it.
Now read the result:
- No
facebookrequests after Reject All and reload: Reject works for new visitors. Repeat the test for a returning visitor (below). - Requests appear, and the Initiator shows
gtm.jsfromgoogletagmanager.com: Google Tag Manager loads the pixel. See cause 1. - The Initiator is a file under
/wp-content/plugins/: a WordPress plugin adds the pixel. The folder name tells you which one. See cause 3. - The Initiator is your page itself or a theme file: the pixel is pasted into the page. See cause 2.
_fbpis there, but nofacebookrequests: the cookie is a leftover from earlier and nothing is sending data. Find out when it was set (see cause 4).
For the returning visitor, open a new private window, click Accept All, open a second page, then reopen the banner with the CookieYes revisit consent button (often a small icon in a corner), reject the advertisement category, save, and repeat steps 4 to 7. CookieYes describes this button in its guide to changing or withdrawing consent.
Why it happens
In the order we see them most often:
- The pixel runs through Google Tag Manager without a consent rule. CookieYes blocks scripts it recognises, but for tags set up in GTM it documents a separate step: a trigger that fires the tag only after consent (CookieYes: blocking cookies with GTM). A Meta tag on "All Pages" ignores the visitor's choice.
- The pixel is pasted into the theme or a header plugin, and CookieYes does not match it. CookieYes says it blocks "most of the commonly used third-party service scripts" and offers manual blocking for the rest (CookieYes: prior consent).
- A plugin adds the pixel itself. On WooCommerce, plugins such as Meta for WooCommerce add the pixel and can also send events from your server (Meta's Conversions API). Server events never show up in your browser, so a clean Network tab does not prove that nothing is sent.
- The visitor accepted earlier and then changed their mind. A pixel that was already loaded on the page keeps running until something tells it to stop or the page is reloaded. An
_fbpcookie set during the earlier visit can also stay in the browser. - The cookie is in the wrong category, or the category loads before consent. CookieYes blocks by category. Its category settings include a "Load cookies prior to consent" option, and CookieYes warns that with it, "the cookies within that category will load before user consent" (CookieYes: edit a cookie category).
The fix
Test again after each step, in a new private window.
Step 1: give the Meta tag in GTM a consent trigger
CookieYes's GTM guide uses the cookieyes-consent cookie as the switch. Adapted to the Meta Pixel, which belongs in the advertisement category:
- In GTM, go to Variables, User-Defined Variables, New.
- Choose 1st Party Cookie, enter
cookieyes-consentas the cookie name, and save the variable (for example as "CookieYes consent"). - Go to Triggers, New, and choose Custom Event.
- Enter
cookie_consent_updateas the event name and tick Use regex matching. CookieYes notes that if you switched off "Support GCM", you enter.*instead. - Choose Some Custom Events, set the condition "CookieYes consent" contains
advertisement:yes, and save. - Open your Meta tag, remove the "All Pages" trigger and add this new trigger.
- Click Submit, then Publish.
If you use Google Consent Mode in GTM instead, open the Meta tag, Advanced Settings, Consent Settings, choose "Require additional consent for tag to fire" and add ad_storage (Google: consent in Tag Manager). Our GTM Consent Mode v2 guide explains this in detail.
Step 2: block a pasted pixel by its address
- In CookieYes, go to Cookie Manager.
- Open the Advertisement category and click + Add Cookie (or edit the existing
_fbpentry). - In Script URL Pattern, enter
connect.facebook.net. CookieYes listshttps://connect.facebook.netas the pattern for the Facebook Pixel (CookieYes: find the script URL pattern). - Save and click Publish changes.
While you are in the Cookie Manager, check that _fbp is not listed under "Necessary" or "Uncategorised", and click the edit icon next to the Advertisement category name to make sure "Load cookies prior to consent" is off.
Step 3: stop the pixel when a visitor withdraws consent
Meta has its own consent switch for the pixel. fbq('consent', 'revoke') pauses sending pixel events, and Meta says "You need to call revoke on every page" (Meta: Meta Pixel and GDPR). CookieYes publishes code that connects this switch to its banner: it starts every page with revoke, then switches to grant or back to revoke whenever the visitor saves a choice (CookieYes: Meta Pixel Consent Mode). The key lines are:
fbq('consent', 'revoke');
fbq('init', '{your-facebook-pixel-id}');
fbq('track', 'PageView');
function handleConsent(hasConsent) {
fbq("consent", hasConsent ? "grant" : "revoke");
}
Use the complete code from the CookieYes page, including the two event listeners, and hand it to whoever maintains your site. The pixel script itself still loads from connect.facebook.net with this code, so keep the blocking from steps 1 and 2 as well if you do not want any request to Meta before a choice.
Step 4: bring plugin pixels under control
- In WordPress, check Plugins for Meta for WooCommerce, PixelYourSite or other pixel plugins, and for "header and footer" snippet plugins.
- Keep one way of loading the pixel. If GTM and a plugin both load it, remove one.
- For Meta for WooCommerce, the plugin's GitHub repository has a guide that connects CookieYes to its "Hold/Release Signals" feature (Meta for WooCommerce: Hold/Release Signals with CookieYes). It holds both pixel and server events until the visitor allows the Advertisement category. When a visitor withdraws that permission, the integration holds signals and reloads the page. It needs a small extra file on your site, so hand it to whoever maintains your site.
- For other plugins, check the plugin's settings and documentation for a consent option, or ask its support how it reads the visitor's choice.
Our Meta Pixel on WooCommerce guide covers plugin pixels and server-side cookies in more detail.
Step 5: clear caches and re-test
Clear your caching plugin, your host's cache and Cloudflare if you use it. If a speed plugin delays or combines scripts, exclude the CookieYes script, as described in CookieYes not blocking cookies before consent.
How to verify the fix
Use a new private window for each run and keep Disable cache ticked:
- Reject All, then reload, then a second page: no requests matching
facebook. No new_fbpcookie. - Accept All: requests to
connect.facebook.netandfacebook.comappear. Your ads tracking still works for visitors who agree. - Accept All, then reject via the revisit consent button, then reload: no more
facebookrequests. If_fbpstays, its Expires date in the cookie list should not move forward on each reload. A date that keeps moving means something is still writing the cookie. - GTM Preview: in Preview mode, after Reject All, the Meta tag should be listed as not fired.
- Meta Events Manager: your own rejected test visits should not appear as new page views. Allow some time for events to show up.
Re-run this after every plugin, theme or GTM change.
Background: Pre-consent tracking explained. For the same problem with another consent tool, see Cookiebot: visitors click Deny, but tracking continues.
Check your site in 1 minute
Our free scan opens your site in a clean browser, clicks Reject, reloads the page and lists every tracker that is still active, including the Meta Pixel. No signup needed. Run a free scan.
Get alerted when it breaks
A new GTM tag or a plugin update can put the pixel back in front of the banner. With monitoring, we repeat the reject test on a schedule and email you when tracking survives a rejection. The free plan includes one monitored site with a weekly re-scan and email alerts. Create an account and add your site.
Last updated: