Cookie consent, platform by platform

Where the field for the script is, where the native banner stops, and what to switch off. One guide per platform, written against the admin screens as they ship.

  • Joomla

    Joomla core has no banner, no Consent Mode and no consent log — tags go in through the head and run unconditionally. One free system plugin puts Cookifi there instead.

    Read the guide
  • JTL-Shop 5

    In Deutsch

    Der Consent Manager im Core kennt keine Kategorien, keinen Consent Mode v2 und kein Einwilligungsprotokoll pro Besucher. Cookifi kommt über das Header-Feld hinein und steuert die Google-Tags über GTM.

    Read the guide
  • Magento 2

    Cookie Restriction Mode is a single Allow notice with no decline, no categories and no consent log. Cookifi goes into the HTML Head field, loads before the RequireJS bundle, and governs every tag.

    Read the guide
  • PrestaShop

    PrestaShop's official GDPR module handles data requests and form checkboxes, not cookies — there is no banner and nothing blocks a tag. A ten-line module puts Cookifi first in the head.

    Read the guide
  • Shopify

    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.

    Read the guide
  • Shoptet

    In Čeština

    Shoptet má vlastní cookie lištu, ta ale řídí jen kódy, které spravuje sám. Cookifi vložíte do HTML kódu šablony, nativní lištu vypnete — a souhlas od té chvíle platí pro všechny skripty v e-shopu.

    Read the guide
  • Shopware 6

    Shopware's cookie consent manager sets and clears cookies, but it blocks nothing: every plugin has to gate its own scripts. Cookifi loads first from a Twig override and governs the lot.

    Read the guide
  • Squarespace

    Squarespace's own banner knows two tiers — essential and non-essential — and does not block the scripts you injected yourself. Cookifi goes in the same header field and gives you real categories, a consent log and Consent Mode v2.

    Read the guide
  • TYPO3

    In Deutsch

    TYPO3 bringt kein Banner, keinen Consent Mode und kein Einwilligungsprotokoll mit. Cookifi kommt per TypoScript in den Head — mit einem Detail, das viele Stunden kostet: ohne external = 1 rendert gar nichts.

    Read the guide
  • Upgates

    In Čeština

    Nativní lišta Upgates podle dokumentace neukládá statistiky souhlasů a vlastní konverzní kódy neblokuje. Cookifi vložíte do pole pro hlavičku a souhlas začne platit pro všechny skripty v e-shopu.

    Read the guide
  • Webflow

    Webflow gives you wf.allowUserTracking and nothing else — no banner, no categories, no Consent Mode, no consent log. Cookifi is one paste into site-wide Head code and a publish.

    Read the guide
  • Webnode

    In Čeština

    Nativní lišta Webnode neblokuje nic, co jste si do hlavičky vložili sami — vaše skripty poběží bez ohledu na volbu návštěvníka. Cookifi vložíte do stejného pole a souhlas začne platit pro všechny.

    Read the guide
  • Wix

    The Wix cookie banner controls Wix's own cookies and integrations — anything you added through Custom Code is outside it. Cookifi goes in through the same Custom Code panel and governs the lot through GTM.

    Read the guide
  • WooCommerce

    WooCommerce has no cookie banner of its own and no Consent Mode defaults, so GA4 and Ads fire the moment a visitor lands. Cookifi goes in the head through WPCode and gates them.

    Read the guide
  • WordPress

    WordPress core ships no banner and no Consent Mode defaults. Cookifi is one script in the header, ahead of every analytics tag — and the only thing to watch is a caching or optimization plugin moving it.

    Read the guide

A guide exists only in the markets it was written for, because the admin labels and the law it cites are local. Where your language is missing, the card says which one it links to.