Consent behaviour

Category: marketing.

Common cookies: _fbp, _fbc.

Common requests: connect.facebook.net, facebook.com/tr.

Setup steps

Remove hardcoded pixel code if it fires before the CMP.

Start Meta after marketing granted.

Check product and checkout in a clean session.

Example snippet

<script>
window.addEventListener('cookiepilot:consent', function (event) {
  var consent = event.detail || {};
  if (!consent.marketing || window.__metaPixelLoaded) return;
  window.__metaPixelLoaded = true;

  !function(f,b,e,v,n,t,s){
    if(f.fbq)return;n=f.fbq=function(){n.callMethod?
    n.callMethod.apply(n,arguments):n.queue.push(arguments)};
    if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
    n.queue=[];t=b.createElement(e);t.async=!0;
    t.src=v;s=b.getElementsByTagName(e)[0];
    s.parentNode.insertBefore(t,s)
  }(window, document, 'script', 'https://connect.facebook.net/en_US/fbevents.js');

  fbq('init', 'META_PIXEL_ID');
  fbq('track', 'PageView');
});
</script>

Test checklist

No _fbp before consent.

No facebook.com/tr after Reject.

After Accept, the pixel starts once without duplication.

Related integrations

See the setups that most often appear together with this integration.

WooCommerce

Cart and checkout work while tags wait for consent.

WordPress

Plugin, cookie banner and Consent Mode without theme edits.

Google Tag Manager

Consent Initialization, dataLayer and tag rules.

Ready to configure it?

Start CookiePilot, choose the right integration and verify that tags wait for user consent before they run.

Start configuration Documentation

CookiePilot Meta Pixel preset: _fbp and events only after consent