Shopify's banner governs Shopify-managed tooling only, and its app pixels ignore any consent state that is not written into the Customer Privacy API. Cookifi writes into it, and runs GTM as a custom pixel so checkout is covered.
Any Shopify plan — you can edit the code of a theme you own. Checkout pages are not editable except on Plus through Checkout Extensibility, which is why GTM has to be a custom pixel.
Shopify admin → Online Store → Themes → ⋯ → Duplicate as a backup, then ⋯ → Edit code.
Under Layout open theme.liquid and paste the Cookifi integration script at the very top of <head>, above {{ content_for_header }}. Add defer if Shopify's editor prompts for it.
Below {{ content_for_header }} add {% render 'cookifi' %}, then create Snippets → cookifi and paste the snippet from the Cookifi Shopify guide. It maps Cookifi's choices onto Shopify's setTrackingConsent.
Settings → Customer privacy → Cookie banner → More actions → Remove cookie banner.
GTM goes in Settings → Customer events → Add custom pixel, not in theme.liquid. The pixel is sandboxed and is the only way to fire on checkout and thank-you pages; the Consent Mode default and update commands belong inside it.
In the Cookifi admin click Add, enter a name and your domain — a sitemap URL is optional — and click Create.
Open the property and copy the script under General → Integration script.
Click the Google icon in the script toolbar to include the Consent Mode default command. The defaults themselves are set under Regions, together with URL Passthrough and Ads Data Redaction.
Paste it as high in the <head> as the platform allows, on every page. Save, reload, and confirm the banner appears.
If the platform strips data- attributes and the banner does not load, switch to Query string mode in the Installation script section and copy the script again.
Cannot touch the head at all? Use the GTM Installation script in a Custom HTML tag with the Consent Initialization – All Pages trigger. Direct installation is still the recommendation, because ad blockers can suppress GTM.
On Shopify, consent lives in the Customer Privacy API (analytics, marketing, preferences, sale_of_data), and Shopify or app pixels ignore anything that is not written there — which is exactly what the snippet in step 3 does. GTM must run as a custom pixel: it is sandboxed with no DOM access, and it is the only way to fire on checkout and thank-you pages, so the Consent Mode default and update calls have to be pasted into the pixel itself.
Shopify cookie banner (Settings → Customer privacy)
One script in the head, a scan that suggests the categories for you, and a 14-day trial that needs no card.
One monthly base from €10 plus usage on read events — the first 10,000 each month are free. Subdomains and team members are unlimited, so a second site is not a second plan.
Live chat and email on every plan, with a human response within one business day on Enterprise. We are a small team, which is why the things customers ask for tend to ship quickly.
Google and Microsoft Consent Mode v2 are first-class, GA4 and GTM are the default path, and Cookifi is a Google-certified CMP partner.
Because Shopify's own tooling and every app pixel read consent from that API and nothing else. Without the snippet, the banner would collect a choice that Shopify's pixels never see.
Theme code does not run on checkout, so the banner itself does not appear there. What matters is that tags on checkout fire through the custom pixel, which respects the consent state Cookifi wrote into the Customer Privacy API.
No — two banners mean two answers to the same question. Remove it under Settings → Customer privacy once Cookifi renders.
Every fact on this page comes from the pages linked below. Spotted something out of date? Tell us and we will correct it.
Last reviewed November 2, 2026
14 days, no credit card. If the install takes you longer than ten minutes, tell us — on our side that counts as a bug.