Meta Pixel Consent Mode
Connect visitor consent choices with your Meta Pixel. CookieHub grants or revokes the Pixel’s consent from the Marketing category, while your Pixel code revokes consent by default.
Built-in CookieHub support · HTML and GTM compatible- Type
- Pixel consent integration
- Works with
- Meta Pixel, installed separately
- Consent calls
- fbq('consent', 'grant') · fbq('consent', 'revoke')
- Setup
- HTML or Google Tag Manager
- CookieHub support
- Built in, from version 2.8.12
What is Meta Pixel Consent Mode?
Meta Pixel Consent Mode uses the Pixel’s own consent command to tell the Meta Pixel whether the visitor has consented. The command does not load or remove the Pixel code. With consent revoked, the Pixel pauses its fires to Meta; with consent granted, it resumes them and can send data to Meta.
CookieHub supports Meta Pixel Consent Mode from version 2.8.12. Once the integration is enabled, CookieHub calls fbq('consent', 'grant') or keeps fbq('consent', 'revoke') in place, based on the visitor’s choice for the Marketing category. That choice sets the consent state of the Meta Pixel on your site; it does not control how Meta uses data in its own products. CookieHub does not install the Meta Pixel: you install the Pixel code separately and add the default revoke to it yourself.
Installing the Meta Pixel and enabling the CookieHub integration are two separate steps. Your Pixel code revokes consent by default; CookieHub then updates the Pixel’s consent state from the visitor’s choice.
- 01Install the Meta Pixel on your siteseparately · your pixel code
- 02Add fbq('consent', 'revoke') before fbq('init')default revoke · added by you
- 03Enable the integration in CookieHubsettings → integrations
- 04Grant or revoke from the Marketing choiceapplied by CookieHub
From visitor choice to Meta Pixel consent.
Pick a visitor state to see the consent CookieHub applies to the Meta Pixel.
The visitor has arrived and the banner is showing. The default revoke in your Pixel code keeps Pixel fires paused.
The visitor accepted the Marketing category.
The visitor rejected the Marketing category, or changed a previous choice.
Meta’s consent command takes grant or revoke — shown here as granted and denied. The state applies to the Meta Pixel only; Analytics and Preferences are not used by Meta.
How CookieHub categories map to Meta.
Meta Pixel Consent Mode follows one CookieHub category: Marketing. The Pixel receives grant or revoke — shown here as granted or denied.
| Meta consent | What it controls | CookieHub category | Before choice |
|---|---|---|---|
| fbq('consent') | Whether the Meta Pixel on your site may send its fires to Meta. The Pixel code stays installed either way. | Marketing | denied |
Revoke consent before the Pixel initialises.
Add fbq('consent', 'revoke'); to your Meta Pixel code before fbq('init', ...), on every page where the Pixel loads. Pixel fires then stay paused until CookieHub applies the visitor’s choice.
- 01fbq('consent', 'revoke');default · added by you
- 02fbq('init', '<your pixel ID>');pixel initialised
- 03fbq('track', 'PageView');pixel code
- 04Visitor makes a Marketing choicecookiehub banner
- 05CookieHub calls grant, or keeps revokeconsent update
Pixel fires are paused
While consent is revoked, the Meta Pixel holds back its fires to Meta and does not set its marketing cookies. The Pixel code itself stays on the page.
Pixel fires resume
Once the visitor accepts the Marketing category, CookieHub grants consent, and the Pixel resumes its fires and can send data to Meta.
CookieHub does not add the default revoke for you, and it does not load or remove the Pixel. Add the revoke line manually to your Meta Pixel code — in your page HTML, or in the Custom HTML tag that holds the Pixel in Google Tag Manager — before the init call.
Set up Meta Pixel Consent Mode.
Supported from CookieHub version 2.8.12. Installing the Meta Pixel and enabling the integration are separate steps: the Pixel must already be on your site, and CookieHub manages its consent state, not the Pixel code.
- 01
Install
Load CookieHub and add the default revoke to the Meta Pixel code you already use.
- 01HTML: add the CookieHub script to the <head> of your website.
- 02Add fbq('consent', 'revoke'); before fbq('init', ...) in your Meta Pixel code.
- 02
Enable
Turn the integration on in the CookieHub dashboard.
- 03Enable Facebook/Meta Pixel Consent Mode under Integrations in your domain’s Settings tab.
- 04Click Save & publish.
- 03
Apply
CookieHub updates the Pixel’s consent state when visitors accept or reject the Marketing category.
- 05Marketing accepted: CookieHub calls fbq('consent', 'grant'). Otherwise consent stays revoked.
Set up Meta Pixel Consent Mode in GTM.
Load CookieHub with the CookieHub CMP template on Consent Initialization, and add the default revoke to the Custom HTML tag that holds your Meta Pixel, before the init call.
- Add a new tag with the CookieHub CMP template from the Community Template Gallery, and enter your CookieHub domain code.
- Set the trigger to Consent Initialization – All Pages.
- In the Custom HTML tag for your Meta Pixel, add fbq('consent', 'revoke'); before fbq('init', ...), so consent is revoked before the Pixel initialises.
- Save and publish the container, then enable Meta Pixel Consent Mode under Integrations in your domain’s Settings tab and click Save & publish.
- Meta Pixel · Custom HTML tagfbq('consent', 'revoke')
- Meta Pixel consentgrant or revoke
Works with your Meta Pixel and CookieHub installation.
CookieHub manages Meta Pixel consent through the installation method you already use.
- Meta Pixelfbq consent
- Meta Pixel codedefault revoke · manual
- CookieHub scriptintegrations setting
- Google Tag Managercmp template
Built for Meta Pixel Consent Mode.
CookieHub supports Meta Pixel Consent Mode from version 2.8.12. Once the integration is enabled and your Pixel code revokes consent by default, CookieHub grants or revokes the Pixel’s consent from each visitor’s Marketing choice.
Meta Pixel Consent Mode documentation.
Last reviewedNovember 2026- Meta Pixel Consent Mode in CookieHubCookieHub’s setup guide for HTML and Google Tag Manager installations, with the category mapping.docs.cookiehub.com
- Domain settings: IntegrationsWhere Meta Pixel Consent Mode is enabled for a domain.docs.cookiehub.com
- Meta Pixel and the GDPRMeta’s guidance on revoking consent before the Pixel initialises and granting it once the visitor consents.developers.facebook.com
Meta Pixel Consent Mode questions.
Yes, from CookieHub version 2.8.12. Enable Facebook/Meta Pixel Consent Mode under Integrations in your domain’s Settings tab, and CookieHub updates the Pixel’s consent state when visitors accept or reject the Marketing category.
No. The Meta Pixel must be installed on your website separately, in your page HTML or through Google Tag Manager. CookieHub manages the Pixel’s consent state; enabling the integration does not add, load or remove the Pixel code.
The default revoke pauses Pixel fires from the moment the Pixel initialises until CookieHub applies the visitor’s choice. Add fbq('consent', 'revoke'); before fbq('init', ...) in your Meta Pixel code. CookieHub does not add it for you.
Marketing. When a visitor accepts the Marketing category, CookieHub calls fbq('consent', 'grant'). Otherwise consent stays revoked. This applies to the Meta Pixel integration only: Analytics and Preferences are not used by Meta, and necessary cookies are always allowed.
Yes. Add the CookieHub CMP template from the Community Template Gallery with the Consent Initialization – All Pages trigger, add the default revoke before the init call in the Custom HTML tag for your Meta Pixel, then enable Meta Pixel Consent Mode under Integrations in your domain’s Settings tab.
When you use the Meta Pixel for visitors in the EEA, the UK or Switzerland, or want the Pixel to send data to Meta only after visitors accept marketing cookies. Which rules apply to your site, such as the GDPR or Meta’s own policies, depends on your visitors and your setup.
Disclaimer
This page describes how CookieHub passes consent choices to the Meta Pixel. It is technical guidance, not legal advice. Enabling Meta Pixel Consent Mode does not by itself make a website compliant — what is required depends on your visitors, your Meta setup and the regulations relevant to your site, such as the GDPR.
Keep your Meta Pixel in step with consent.
Enable Meta Pixel Consent Mode in CookieHub, add the default revoke to your Pixel code and let each visitor’s Marketing choice decide whether the Pixel can send data to Meta.
- 14-day trial
- No card required
