Meta Pixel Consent CMP
Let the Meta Pixel follow every UniConsent choice. It waits for consent in the EEA and the UK, and stops after a US opt-out or Global Privacy Control.
- Supported
- Yes: with the UniConsent Meta Pixel consent tag
- Consent signal
- fbq('consent', 'grant' / 'revoke')
- Works with
- Google Consent Mode v2, Microsoft UET, IAB TCF, IAB GPP
- Documentation
- Meta Pixel Consent with UniConsent CMP
Meta Pixel Consent from Your UniConsent Banner
The Meta Pixel needs consent before it sets cookies or sends the data of visitors in the EEA and the UK. With the UniConsent Meta Pixel consent tag, the pixel follows the choice each visitor makes in your UniConsent banner, on page load and after every change, through the consent API of the pixel itself.
How the Pixel Follows Each Choice
| Visitor choice | Meta Pixel |
|---|---|
| No choice yet | Waits, with fbq('consent', 'revoke'); in your pixel code |
| Allows advertising | fbq('consent', 'grant'): the pixel sends its events |
| Rejects or withdraws | fbq('consent', 'revoke') |
| US opt-out or Global Privacy Control | fbq('consent', 'revoke') |
The tag grants consent when Google Consent Mode ad_storage, ad_user_data and ad_personalization are all granted, so it works the same with IAB TCF, Consent Categories and the US banners.
One Banner for Every Ad Platform
A single choice in the UniConsent banner updates Google Consent Mode v2, Microsoft UET Consent Mode, Amazon Consent Signal and the Meta Pixel together, with IAB TCF and IAB GPP for programmatic partners.
Frequently Asked Questions
How does UniConsent work with the Meta Pixel?
Add fbq('consent', 'revoke') before fbq('init') in your pixel code, and add the UniConsent Meta Pixel consent tag. The pixel waits until the tag calls fbq('consent', 'grant') for a visitor who allows advertising, and the tag revokes consent again when the visitor withdraws.
Which UniConsent choice turns the Meta Pixel on?
Consent to advertising: Google Consent Mode ad_storage, ad_user_data and ad_personalization all granted. With IAB TCF or Consent Categories, the choice in the banner sets these values.
What happens after a US opt-out?
After a US "Do Not Sell or Share" opt-out or a Global Privacy Control signal, the tag revokes consent, so the Meta Pixel stops sending events.
Do I need to change my Meta Pixel code?
Only one line: fbq('consent', 'revoke') before fbq('init'). Without it, the pixel can send events before the visitor makes a choice.
Does the Meta Pixel consent tag slow down other sites?
No. It is a separate tag that you add only on sites with the Meta Pixel. The main UniConsent tag does not change.
Set Up Meta Pixel Consent
- Sign up at app.uniconsent.com and install the UniConsent tag.
- Hold the pixel until consent: add
fbq('consent', 'revoke');beforefbq('init')in your Meta Pixel code:
// the Meta Pixel base code
fbq('consent', 'revoke');
fbq('init', 'YOUR_PIXEL_ID');
fbq('track', 'PageView');
- Add the Meta Pixel consent tag after the UniConsent tag:
<script async src="https://cmp.uniconsent.com/v2/meta-consent.min.js"></script>
Technical Documentation
Related Resources
Google Consent Mode CMP
Certified Google CMP Gold tier partner for Consent Mode integration.
Learn more →Microsoft UET Consent
Certified Microsoft UET Consent Mode CMP for Microsoft Advertising and Bing Ads.
Learn more →Amazon Consent Signal
Ad storage and user data consent for Amazon Ads tags and pixels, with IAB TCF and GPP strings.
Learn more →Get started to make your website and application compliant for EU GDPR, US CPRA, CA PIPEDA etc
Sign up