How do I make the Meta pixel wait for cookie consent on a B2B website?
Call fbq('consent', 'revoke') before fbq('init') on every page, then fbq('consent', 'grant') once the visitor accepts advertising cookies. These are the two commands Meta's developer docs give to pause the pixel and let it send again. A tag manager or consent tool can do the same job by loading the pixel only after consent. Meta's docs describe no consent mode with modeling like Google's. Whether your B2B visitors must opt in is a legal question. Meta's terms put consent on you where the law requires it, so ask your legal team.
Ask Tofu next
Pick a question and Tofu Ads Agent answers it in chat.
- Is my Meta pixel firing before visitors accept our cookie banner?
- Set up Google Tag Manager so my Meta pixel and Lead tag fire only after ad_storage consent
- Compare the Meta leads reported from EU countries with our CRM since we added the cookie banner
- Should I send CRM lead stages to Meta with the Conversions API when visitors decline cookies?
- Will turning on Limited Data Use hurt my Meta retargeting in California?
As of November 2026.
What do the pixel's consent commands do?
revoke pauses the pixel and grant lets it send again. Meta's pixel page on the GDPR says to use them "to pause sending Pixel fires to Facebook, and once cookie consent is granted, send Pixel fires to Facebook," and adds: "You need to call revoke on every page." Its example calls revoke before init:
fbq('consent', 'revoke'); // on every page, before init
fbq('init', 'YOUR_PIXEL_ID');
fbq('track', 'PageView');
// when the visitor accepts advertising cookies
fbq('consent', 'grant');
Because revoke runs on every page load, your banner has to remember the visitor's choice and call grant again on each page for people who already said yes. If someone withdraws consent later, call revoke to pause the pixel again.
Does Meta have a consent mode like Google's?
Not one that Meta documents. In Google's advanced consent mode, Google's tags load before the visitor chooses and, when consent is denied, send signals without storing cookies, which Google uses for conversion modeling. Meta's pixel docs describe only revoke and grant, with nothing about cookieless signals or modeling. Some consent tools call their Meta setup "Meta Pixel Consent Mode," CookieYes among them, but CookieYes's version runs the same two commands. Google's consent mode changes how Google's own tags behave; for the Meta pixel you add the check yourself.
Can Google Tag Manager or our consent tool hold the pixel instead?
Yes. Meta says the consent code can be optional if "you already have a system in place that addresses this need, such as a tag manager." In Google Tag Manager, open each Meta tag (the base code and any event tags, such as Lead), go to Advanced Settings > Consent Settings, and under Additional Consent Checks choose Require additional consent for tag to fire. Add the consent type your banner uses for advertising, such as ad_storage. Google says the tag then fires only if every type you list is granted "when the tag is triggered," so check what happens on the page where a visitor clicks accept.
Our site runs on HubSpot. How do we connect the pixel to HubSpot's banner?
Use HubSpot's consent banner API. Its addPrivacyConsentListener callback runs when the visitor clicks accept or decline, and right away if they already answered (once the banner code has loaded). consent.categories.advertisement tells you whether they accepted advertising cookies. Keep revoke before init in the base code, then add:
var _hsp = (window._hsp = window._hsp || []);
_hsp.push(['addPrivacyConsentListener', function (consent) {
fbq('consent', consent.categories.advertisement ? 'grant' : 'revoke');
}]);
Because the callback also runs for visitors who answered on an earlier page, this covers the "call grant on every page" step.
Does revoke stop my Meta conversions?
For visitors who don't accept, yes for pixel events. While consent is revoked, the pixel doesn't send their page views or leads, so Meta can't count those conversions or add those visitors to website audiences through the pixel. Meta's page doesn't say whether events fired before a later grant on the same page are sent then or dropped, or whether the pixel sets its cookie while paused. Test it on your own site (see the last question). If many of your visitors come from places where most people decline, expect fewer reported website leads.
Does the Conversions API need consent too?
The commands above run in the browser, so they don't control events your server sends. Meta's GDPR help article says "If you use Meta Business Tools (such as Meta Pixel or Conversions API), you must follow the Meta Business Tools Terms," which call for clear disclosures and a lawful basis, including consent where it applies, before you send data to Meta. So your server setup should check the same choice your banner records. Meta's consent page doesn't say how revoke affects the Meta-enabled Conversions API, which Meta's comparison of setup options lists as free and one click ("a web-only setup that automatically creates a server-side connection"), so test that too. For setup options, see how to set up the Meta Conversions API without a developer.
What is Limited Data Use, and is it the same as consent?
No. Limited Data Use (LDU) is Meta's data processing option for US state privacy laws. When it's on for people in the states it covers, Meta says it processes their data "as a service provider or processor" and limits its use under its State-Specific Terms. For the pixel, add fbq('dataProcessingOptions', ['LDU'], 0, 0); before init; the zeros ask Meta to work out the location. Meta lists 14 states, including California, Texas and New Jersey, and warns that "retargeting and measurement capabilities will be limited" with LDU on. Whether you need it is a question for your legal team.
Do B2B websites need cookie consent for the Meta pixel?
Ask your legal team; Meta won't decide it for you. Its Cookie Consent Resource says "Facebook cannot provide legal guidance on compliance" and recommends you "talk to your Legal representative." What Meta's own documents say:
- GDPR: Meta's help center says the GDPR "may apply to your business if you collect or use personal data about people in the EU or EEA," and that the UK GDPR covers people in the UK.
- Meta Business Tools Terms (effective November 3, 2025): where the law requires informed consent for cookies, such as in the EU, you must "ensure, in a verifiable manner, that an end user provides all necessary consents" before Meta's tools store or access Meta cookies on their device. The terms also ask for "a clear and prominent notice on each web page where our pixels are used."
Your legal team can say how these apply to your visitors and what your banner has to do.
How do I check that the pixel waits?
Use Meta's Test events tool. In Events Manager, click Data sources, select your pixel or dataset, click Test events, enter your site's URL and click Open website. Decline the banner and go to your demo form: no events should arrive. Then accept and check that PageView appears. Meta notes that website activity is recorded only while the test events page is open. Also look at your base code: Meta's version ends with a <noscript> image tag that sends a PageView when JavaScript is off, and the consent commands, being JavaScript, can't hold it. Ask your developer whether to keep it.
Sources
- General Data Protection Regulation, Meta Pixel (Meta for Developers), checked November 7, 2026
- Get started with the Meta Pixel (Meta for Developers), checked November 7, 2026
- GDPR requirements for businesses that advertise on Meta (Meta Help Center), checked November 7, 2026
- Meta Business Tools Terms (Meta, effective November 3, 2025), checked November 7, 2026
- Cookie Consent Resource (Meta for Developers), checked November 7, 2026
- Data processing options for US users (Meta for Developers), checked November 7, 2026
- Test events tool: verify app and web browser events for Meta (Meta Help Center), checked November 7, 2026
- Compare Conversions API setup options (Meta Help Center), checked November 7, 2026
- About consent mode (Google Ads Help), checked November 7, 2026
- Tag Manager consent mode support (Tag Manager Help), checked November 7, 2026
- Consent banner API (HubSpot Developers), checked November 7, 2026
- Meta Pixel Consent Mode (CookieYes, updated May 15, 2026), checked November 7, 2026