ConsentPixel – Privacy · Verified

Supported Platforms

ConsentPixel Platform Integrations

Install ConsentPixel on your website platform in minutes. Follow platform-specific setup guides for cookie consent, privacy compliance, Google Consent Mode v2, and tracking control.

CMS Platform

WordPress

Learn how to install and configure ConsentPixel on WordPress, including Google Consent Mode v2, GDPR compliance, CCPA requirements, and cookie consent management.

Ecommerce Platform

Shopify

Configure ConsentPixel on Shopify stores with support for Google Analytics, Google Ads, Meta Pixel, Consent Mode v2, GDPR, CCPA, and privacy compliance requirements.

Ecommerce Platform

WooCommerce

Your WooCommerce store fires Google Analytics, Meta Pixel, Klaviyo, and session-replay tools on every page — including your checkout.

Ecommerce Platform

BigCommerce

Your BigCommerce store fires analytics, ad pixels, and session replay tools on every page—including for EU visitors who require GDPR consent and California visitors who may trigger CIPA risk.

Ecommerce Platform

Miva

Miva powers serious mid-market and enterprise eCommerce — B2B wholesale, DTC retail, and hybrid operations running complex product catalogues across multiple storefronts.

Magento · Adobe Commerce

Magento

Magento's built-in Cookie Restriction Mode displays a notice bar while every tracking script on your store continues firing in the background. Google Analytics, Meta Pixel, Adobe Analytics, session-replay tools, marketing automation — all transmitting visitor data without consent.

Wix

Wix

Wix's built-in cookie banner handles its own native scripts. But Google Analytics, Meta Pixel, TikTok, Hotjar, and every other tool you connected through Wix's marketing integrations panel? Those fire regardless.

Drupal 7 · 10 · CMS

Drupal

Drupal CMS 1.0 ships with Klaro built in. The EU Cookie Compliance module has been installed millions of times. But both carry the same critical limitation: they cannot block external JavaScript.

Any HTML · Static · Any Host

Any HTML Site

A hand-coded or static site does exactly what you wrote into it — including every analytics tag, pixel, and embed you hardcoded into the head tag. There is nothing in plain HTML to hold those scripts for consent; they fire on load.

Bubble · Page HTML Header

Bubble

Bubble lets you build full no-code apps — and pull in analytics, chat, and pixel functionality through plugins and header HTML. But Bubble has no native consent layer. Every plugin script and every tag in your page HTML header loads when the page renders, with nothing holding it for consent.

Framer · Page HTML Header

Framer

Framer ships beautiful sites fast — but it has no native consent layer that blocks tracking. The GA4, Meta Pixel, GTM, and session-replay scripts you add through Framer's custom code and embeds fire on every page load, with nothing holding them until your visitor consents.

Ghost · Code Injection

Ghost

Ghost is built for publishers and newsletters — fast, clean, and SEO-friendly. But Ghost ships with no native cookie consent layer at all. Ghost's own analytics, any Google Analytics or Fathom you add, and every embed in your posts fire the moment a page loads.

Headless · Composable · API-Driven

Headless & API

In a headless or composable stack — commercetools, Contentful, a custom React or Vue frontend — there is no monolith to bolt a consent plugin onto. Consent has to be enforced at the frontend, before any analytics SDK or tag initialises, and it has to coordinate with server-side tagging.

Joomla 3 · 4 · 5

joomla

In a headless or composable stack — commercetools, Contentful, a custom React or Vue frontend — there is no monolith to bolt a consent plugin onto. Consent has to be enforced at the frontend, before any analytics SDK or tag initialises, and it has to coordinate with server-side tagging.

Kajabi · Custom Code

Kajabi

Kajabi powers course sales, funnels, and checkout for creators — and it has pixel settings for Facebook and Google. But those settings fire the pixels; they do not gate them for consent.

Next.js · Gatsby · Astro · SvelteKit

Next.js, Gatsby, or Astro site

On a Next.js, Gatsby, or Astro site, third-party scripts get injected through next/script, gatsby-ssr, Astro layouts, or a tag manager — and they fire during hydration before any React-based consent provider has mounted.

Shopify Markets · Multi-Region

Shopify Marketse

Shopify Markets lets you sell into many regions from one store — each with its own privacy rules. Shopify's Customer Privacy API and consent banner cover Shopify's own tracking, but custom pixels, scripts in theme.liquid, and many app pixels are not gated by it.

Shopify Markets · Multi-Region

Squarespace

Squarespace's built-in Cookie Banner shows a notice and can defer Squarespace's own analytics — but it does not block the GA4, Meta Pixel, Hotjar, and GTM scripts you add through Code Injection.

Webflow · Native + Custom Code

Webflow

Webflow added a native cookie consent component in 2022 — but it manages Webflow integrations and Google Analytics, not the third-party scripts you embed yourself.

Shopify · EU

Cookie Consent for Shopify in the EU

Most agencies treat Google Analytics as the "safe" tracker — lower profile than Meta Pixel, owned by Google, surely fine. In 2024, a court named Google Analytics specifically in a CIPA claim and let it proceed.

Scroll to Top