How to set up the Meta Pixel with Cookiequiet

Option 1: mark the base code

Meta recommends placing the pixel base code in the head of every page. With Cookiequiet, paste it right below the snippet and change only the opening tag:

html
<script type="text/plain" data-cq-category="marketing">
  /* the base code from Events Manager, unchanged: it loads fbevents.js, then */
  fbq('init', 'YOUR_PIXEL_ID');
  fbq('track', 'PageView');
</script>

Cookiequiet runs the script when the marketing category is granted: immediately on later visits where the stored choice includes it, and at the moment of the click when the visitor accepts during the visit. Until then, nothing is loaded from connect.facebook.net and no _fbp cookie is set. Tags marked data-cookiecategory="marketing" or data-cookieconsent="marketing" for CookieYes or Cookiebot work as they are; see switching from CookieYes.

Remove the noscript image. The base code ends with a <noscript> block containing a 1x1 image that requests Meta's servers with your pixel ID. It is plain HTML: it fires in browsers with JavaScript disabled, before any banner, and no consent script can hold an image. Delete it.

Events. Standard events in page code (fbq('track', 'Purchase', ...)) must not run before the pixel: put them in scripts marked the same way, or, in your own JavaScript, check that window.Cookiequiet.get() returns a choice whose c array includes marketing before calling fbq.

Option 2: fire it from Google Tag Manager

In Tag Manager, use the Meta Pixel tag (Meta's template from the community gallery, or a Custom HTML tag with the base code) and give it a Custom Event trigger: event name cq_consent, Some Custom Events, condition cq_marketing equals true, with Tag firing options set to Once per page. Cookiequiet pushes cq_consent with the cq_marketing flag on every page load where a choice is stored and after each choice. For event tags that fire on form submissions or purchases, add Require additional consent for tag to fire with ad_storage under Advanced Settings, then Consent Settings: Cookiequiet sets ad_storage granted with the marketing category, so the check holds. The Tag Manager guide describes the variables and triggers in detail.

Option 3: Meta's consent calls

Meta's pixel has its own consent switch for sites where the pixel loads before the banner: fbq('consent', 'revoke') pauses the pixel, fbq('consent', 'grant') resumes it. Meta documents that revoke must be called on every page, before fbq('init'). It is the fallback when a platform loads the pixel for you and gives you no consent API. Place the revoke call before the base code, and grant on consent with the event Cookiequiet dispatches:

html
<script>
  window.addEventListener('cq:consent', function (e) {
    if (typeof fbq === 'function' && e.detail.categories.indexOf('marketing') >= 0) {
      fbq('consent', 'grant');
    }
  });
</script>

Note the difference with option 1: the pixel script is loaded and fbevents.js runs; only its sending is paused. Where you can mark the base code, marking is the cleaner choice.

Pixels loaded by your platform

• Shopify: the Facebook & Instagram app installs the pixel as an app pixel, which follows Shopify's Customer Privacy API; the Shopify guide shows the bridge that passes Cookiequiet's choice to it.
• HubSpot: a pixel added through HubSpot's ads tool follows the advertisement value passed with setHubSpotConsent, see the HubSpot guide.
• Wix and Squarespace: the pixel ID fields of these platforms load the pixel outside your control. Remove the ID and paste the marked base code through custom code, as the Wix and Squarespace guides explain.
• Plugins and tag managers that inject fbevents.js with JavaScript are held by the auto-blocker, which lists connect.facebook.net under marketing, until that category is granted.

How to test

1. Install the Meta Pixel Helper extension, open the site in a private window and click Reject all: the helper finds no pixel, the network tab shows no request to connect.facebook.net or facebook.com/tr, and there is no _fbp cookie.
2. Clear the cookies, click Accept all, reload: the helper shows the PageView event and _fbp is set.
3. Complete a test conversion and check that the event appears in Events Manager's test events.
4. Open the consent log in the Cookiequiet dashboard.

Details worth knowing

• Cookies. The pixel sets _fbp (a browser identifier, 90 days) and, after a click on a Meta ad, _fbc. Both are marketing cookies in the banner's cookie table.
• Conversions API. Sending the same events from your server does not remove the need for consent; the server events must follow the same choice, which the consent log documents.
• Advanced matching sends hashed customer data with the events and is part of the pixel's marketing purpose.
• Consent rates. Expect pixel data to cover the share of visitors who accept marketing; the article on consent rates gives orders of magnitude.