Your cookie banner shows, but Meta and Google start collecting before the visitor chooses — and Meta keeps going after “Reject”.
Google Ads and Meta Pixel send data before the visitor makes any cookie choice.Visit 1Problem
Why it matters
In the EU and the UK, ad cookies need the visitor's consent first, and so do most analytics cookies. On your site they start before anyone has said yes.
What to look at
These trackers were probably added outside your cookie tool — in the theme, by another plugin, or in Google Tag Manager without consent settings — so the banner can't hold them back.
After the visitor clicks “Reject”, Meta Pixel still sends data.Visit 3Problem
Why it matters
The visitor said no, and your site still sends their visit to Meta.
How to fix it — in your cookie tool
We found CookieYes on this site. Using something else? Pick it:
Mark the pixel's script with data-cookieyes="cookieyes-advertisement". Or, in Google Tag Manager, fire it on the cookie_consent_update event only when the cookieyes-consent cookie contains advertisement:yes.
Move the Meta Pixel tag off the “All Pages” trigger and onto your cookie tool's marketing-consent trigger.
Change the pixel's script to type="text/plain" data-cookieconsent="marketing" and delete its <noscript> part — otherwise “Reject” doesn't stop it.
Switch on Integrations › Services › Facebook, or add the pixel in Script Center › Add a third-party script under Marketing. Block the pixel's <noscript> image too.
Give the pixel class="optanon-category-C0004", or fire it in Google Tag Manager on OneTrustGroupsUpdated when the groups contain ,C0004,. Then re-publish the OneTrust script.
Add “Facebook Pixel” under Service Settings › Data Processing Services, then mark the script data-usercentrics="Facebook Pixel".
If the pixel comes from PixelYourSite, connect it to your consent plugin. If it's pasted into the theme or a header plugin, remove it and add it in a way your cookie tool controls.
Remove pixel code pasted into theme.liquid and install the pixel through the Facebook & Instagram app. Make sure your banner app passes the choice on to Shopify.
Connect the pixel through Marketing Integrations. If it's pasted as Custom Code, set that code's category to Marketing.
Its built-in banner can't be relied on to stop custom code. Use a consent tool, or Meta's own consent switch.
Call fbq('consent','revoke') before fbq('init', …) on every page, and fbq('consent','grant') only after Accept.
Your site sends Google the old version of the consent signals.Visits 1–3To improve
Why it matters
Since March 2024 Google Ads also needs two newer consent signals for visitors in the UK and the EU. Without them, remarketing and conversion measurement are limited.
What to look at
An old cookie tool version or an old Consent Mode setting. Update it to Consent Mode v2.