Consent management for Magento
Magento gives you a store, not a consent platform. Consent Studio adds the banner once in your design configuration, governs the tools you added around it, and scans every page it can reach each week so you know what is actually running.
- Added once, store-wide
- Consent Mode v2 built in
- Weekly scan of every reachable page
From €10 a month. No credit card, no per-visitor billing.
A cookie banner that works with Magento
Magento exposes no consent interface, so nothing here is handed to the platform. The banner governs what runs, directly.
Magento’s own storage is not the problem
Our scanner recognises eight Magento entries and classifies every one as functional: the cached basket, the language strings, the recently viewed and compared lists. All of it is local storage rather than cookies, and all of it is there to make your storefront work. What needs consent is what you added around it.
- Eight entries recognised
- Classified functional
Google Consent Mode v2, however you install
Most of what needs governing on a Magento store is Google: Analytics, Ads, the Google tag. Consent Studio sets the denied defaults before any of them run and sends the update the moment your customer chooses, and none of that depends on the platform underneath.
- Denied then updated
- Built in
Extensions and embeds wait, once you mark them
A live chat, a review widget, a remarketing pixel an agency added two years ago. Mark it in your template with the category it belongs to and Consent Studio releases it only once that category is granted. It is a change you make rather than something that happens on its own.
- Per-category release
- You mark the embed
CCPA and CPRA on a Magento store
Selling into California changes what the banner has to ask rather than adding a second one. Consent Studio runs both regimes from one configuration.
A notice for US visitors, consent for EU ones
The two regimes want opposite defaults: the EU needs permission before anything runs, and US state law generally needs an honest way out. Consent Studio switches between asking and informing by region, from the same banner, so a shopper in Rotterdam and one in Sacramento each get the correct one. Essential includes one regional rule, which is exactly this case; further ones are charged rather than blocked.
Global Privacy Control, honoured three ways
CPRA made the browser-level opt-out signal binding in California, and plenty of platforms still ignore it. Consent Studio reads it and you decide what it means: ignore it, use it to pre-select the opt-out toggles, or treat it as a refusal outright and never show the banner. On every plan, including the cheapest.
Proof of what each shopper was shown
An opt-out regime still asks you to show your work. The consent log records what each visitor saw and what they chose, exportable and filterable, so a request about a single order has an answer rather than an assurance. That is the half a cookie banner on its own never gives you.
One answer controls every tool on your site
A banner that only governs the platform leaves everything you added on top of it running. Consent Studio speaks to the tools around it as well, and by default holds anything it does not recognise until the visitor says otherwise.
Discover All Integrations
Choose how to install the cookie banner
Every route ends with the same banner and the same consent record. Pick the one that fits how your site is built.
Direct code
Recommended RouteAdd the snippet in Content, Design, Configuration, then the HTML Head section of your store view. It applies to every storefront page at once, and no template file has to be edited.
- Full control
- No dependencies
Google Tag Manager
Already running a container? Add our official tag from the Community Template Gallery on the Consent Initialization trigger, and nothing goes into Magento at all.
- Official tag template
- No site deploy
How to set up cookie consent for Magento
One field, once, and the whole storefront is covered. You need access to your Magento admin and nothing else.
Add your store in Consent Studio
Create the site and the banner is generated for your domain, with your categories, your text and your styling. All of that lives in Consent Studio rather than in Magento, so changing the wording or the colours later never means going back into the admin.
Paste the snippet into your design configuration
In the Magento admin, open Content, then Design, then Configuration, edit the store view you want and paste the snippet into the HTML Head section. It applies to every storefront page from that moment, so there is no template file to edit and no per-page work. Flush the cache afterwards and load your store in a private window to confirm the banner appears.
Mark the extensions you want held back
Anything an extension or an agency added, a chat widget, a review script, a remarketing pixel, will keep loading until you tell it not to. Mark each one with the consent category it belongs to and Consent Studio releases it only once your customer grants that category. This step is the difference between a banner that shows and a banner that governs.
Read the first scan
Within a week Consent Studio has crawled your storefront and listed what it actually loads. Read it once properly. Magento’s own entries will appear as functional, which is correct and needs no action; what is worth your attention is everything below them, because a store that has been running for a few years usually carries more than anyone remembers installing.
A cookie banner alone is not enough
Most sites are leaking before anyone notices. Not through malice, but through a tag somebody added in a hurry, a vendor that changed its script, a plugin that phones home.
- Unconsented tracking
- Unwanted overseas transfers
- Consent records you cannot produce
- Scripts you never approved
The Full Consent Stack.
Three products, one consent record. What a visitor agreed to in the banner is what every downstream tag sees.
Which plan Magento needs, and why
Essential covers this page completely. Nothing here is an add-on or a higher tier, because nothing here depends on a platform integration.
Essential is enough
€10/month
- Google Consent Mode v2 and Microsoft UET
- Consent-gated blocking for your extensions
- Unlimited pages, 200,000 consent actions a month
What Professional adds
€36/month
Worth it once the catalogue outgrows a manual check, or you sell into US states in earnest.
- More depth: HTTP consent cookies, accessibility, re-prompting
- GPP, the signal US ad tech reads
- On-demand scans, right after a change
- Sitemap scanning, for every product page
Every plan includes
Trusted by organisations that care about privacy
Frequently asked questions about Magento
Does Magento set cookies before consent?
Magento stores data locally rather than in cookies for most of its own features, and it is functional data: the cached basket, your language strings, and the recently viewed and compared lists. Consent Studio classifies all eight of those entries as functional. The consent question on a Magento store is about the extensions and tags added around it.
Does Magento have a built-in cookie banner?
Magento ships a cookie restriction mode, and it is a notice rather than a consent platform. It can display a message and set an allow flag; what it does not do is hold a per-visitor record of what was agreed, produce that record on request, or govern the extensions and tags you added yourself.
How do I add a cookie banner to a Magento store?
Paste the Consent Studio snippet into Content, Design, Configuration, in the HTML Head section of your store view. It applies to every storefront page at once, with no template file to edit. Flush the cache afterwards so the change reaches your customers.
Does Consent Studio block Magento extensions automatically?
Not on its own. Each extension or embed is held once you mark it in your template with the consent category it needs, and Consent Studio then releases it when that category is granted. Google tags are the exception: those are governed by Consent Mode v2 without any marking.
Does a Magento store need a cookie banner under the GDPR?
If it sets anything that is not strictly necessary, yes, and most stores do. Analytics, remarketing pixels, embedded video and chat widgets all fall outside the exemption, so consent has to be obtained before they load. The platform does not change the obligation.
Get Started with the Full Consent Stack
Everything you need in one bundle. Consent Studio provides you with a consent banner, scanner and client-side tag manager that guarantees no data ever gets transferred overseas.
Read the documentation
Our help center walks through every integration, plugin and template step by step, with screenshots. It is written and kept current by the people who build Consent Studio.