Quick facts
- Price
- $249.00 USD
- magento_2 versions
- —
- Setup time
- 20 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
GDPR / Cookie Consent Compliance
A build-to-order Magento 2 / Adobe Commerce extension that blocks cookies until consent, supports Google Consent Mode v2 and Microsoft UET, and handles GDPR/CCPA data subject requests with full consent logging. Built, installed, and supported by ECOSIRE on your store.
$249.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
True prior blocking — cookies and tracking tags are suppressed until the visitor gives consent, not merely notified after the fact
Google Consent Mode v2 integration setting ad_storage, analytics_storage, ad_user_data, and ad_personalization based on the visitor's choices
Microsoft UET consent signaling for Bing Ads / Clarity tag gating
Right-to-be-forgotten workflow with a cron-driven anonymization queue over customer, quote, and sales_order data
Data Subject Access Request (data export) packaging customer and order data into a downloadable archive
Consent logging to a dedicated table via an observer on consent events — timestamp, categories, banner version, IP, and user agent
Configurable banner templates per store view and locale via system.xml/config.xml with phtml template overrides
Cookie categorization (necessary, analytics, marketing, preferences) with granular per-category toggles
Service contracts and REST/GraphQL endpoints for consent state and data requests, usable by headless/PWA frontends
Admin ACL resources so only authorized roles can view the consent log or process erasure requests
RequireJS deferral so Magento's own cookie-dependent JS components honor the consent gate
Re-consent prompting when the policy version or cookie set changes
About this Product
GDPR / Cookie Consent Compliance is a custom Magento 2 module that ECOSIRE builds, installs, and supports on your own Adobe Commerce or Magento Open Source store. It is not an instant Marketplace download — we tailor it to your theme, your third-party scripts, and your legal posture, then deploy it into app/code/Ecosire/GdprCookieConsent (or your preferred vendor namespace) on your infrastructure.
Why Choose GDPR / Cookie Consent Compliance
True prior blocking — cookies and tracking tags are suppressed until the visitor gives consent, not merely notified after the fact
Google Consent Mode v2 integration setting ad_storage, analytics_storage, ad_user_data, and ad_personalization based on the visitor's choices
Microsoft UET consent signaling for Bing Ads / Clarity tag gating
Right-to-be-forgotten workflow with a cron-driven anonymization queue over customer, quote, and sales_order data
Data Subject Access Request (data export) packaging customer and order data into a downloadable archive
Consent logging to a dedicated table via an observer on consent events — timestamp, categories, banner version, IP, and user agent
The core difference from a banner-only notice plugin is true prior blocking. Cookies and tracking tags do not fire until the visitor consents. We achieve this with a layout/JS layer that gates tags through Google Consent Mode v2 (ad_storage, analytics_storage, ad_user_data, ad_personalization) and Microsoft UET consent signals, plus requirejs-config.js deferral so Magento's own cookie-dependent components respect consent state.
On the data-rights side, the module exposes service contracts for right-to-be-forgotten and data-export (Subject Access Requests). Requests route through admin-ACL-protected controllers and are fulfilled against customer, quote, sales_order, and newsletter data, with a cron-driven anonymization queue so erasure runs safely off-request.
Every consent decision is written to a dedicated consent log table via an observer on consent events, giving you a timestamped, versioned audit trail (banner version, categories, IP, user agent) for GDPR Article 7(1) accountability. Banners are configurable from system.xml / config.xml with template overrides per store view and locale.
We deliver via setup:upgrade + setup:di:compile, validate on a staging copy of your store, and hand over with documentation. Built honestly, installed by us, supported after launch — no fabricated compliance guarantee, just a solid technical foundation your DPO and developers can stand behind.
What you get
- A custom Magento 2 module installed under app/code on your Adobe Commerce or Magento Open Source instance
- Installation and deployment on your store via setup:upgrade, setup:di:compile, and static content deploy, validated on staging first
- Consent log database schema (declarative db_schema.xml) plus admin grid to review consent records
- Admin configuration section (Stores > Configuration) with banner text, categories, and Consent Mode v2 / UET toggles
- Theme and locale integration so the banner matches your store design across all configured store views
- Technical handover documentation covering configuration, the data-request workflow, and the consent audit trail
- A defined warranty/bug-fix window plus an optional ongoing support and update arrangement
- Source code ownership — the module lives in your repository, no per-seat licensing lock-in
Who this is for
EU/UK merchant facing regulator scrutiny
A store selling into the EU/UK that needs genuine prior consent blocking and a defensible audit trail for ICO or DPA inquiries — not just a cosmetic banner that fires tags anyway.
Marketing team running Google & Microsoft Ads
A growth team that must keep Google Ads and Bing/Clarity measurement working under Consent Mode v2 and UET consent rules, recovering modeled conversions while staying compliant.
Data Protection Officer / compliance lead
A DPO who needs documented consent records, a working right-to-be-forgotten process, and SAR data exports they can produce on demand within statutory deadlines.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the GDPR / Cookie Consent Compliance module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for GDPR / Cookie Consent Compliance, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How GDPR / Cookie Consent Compliance Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Blocks cookies before consent (true prior blocking) | ||||
| Google Consent Mode v2 + Microsoft UET integration | ||||
| Right-to-be-forgotten & data-export workflow | ||||
| Timestamped, versioned consent audit log | ||||
| Tailored to your theme, scripts & legal posture | ||||
| Installed & supported on your store by the vendor | ||||
| Source code ownership, no per-seat license lock-in | ||||
| Instant availability / zero lead time |
Frequently Asked Questions about GDPR / Cookie Consent Compliance
+Is this an instant download from the Adobe Commerce Marketplace?
No. This is a build-to-order extension. ECOSIRE builds the module to fit your theme, your specific third-party scripts, and your legal requirements, then installs it on your Magento 2 / Adobe Commerce store. There is no instant Marketplace download — you get a tailored module and a real deployment.
+How long does delivery take?
Typical lead time is about 2 to 4 weeks from kickoff, depending on how many tracking scripts need gating, the number of store views and locales, and the complexity of your data-request workflow. We confirm a firm timeline after a short scoping call and validate on a staging copy of your store before go-live.
+What ongoing support and updates do I get after launch?
Every build includes a warranty/bug-fix window after handover. Beyond that, we offer an optional ongoing support and update arrangement covering Magento version upgrades, Consent Mode / UET API changes, and new cookie categories. The source code lives in your repository, so you are never locked into per-seat licensing.
+Does it actually block cookies before consent, or just show a banner?
It blocks. Tracking tags are gated through Google Consent Mode v2 and Microsoft UET consent signals, and Magento's cookie-dependent JS is deferred via requirejs until the visitor consents. The banner is the visible layer; the real work is preventing tags from firing until a choice is made and logging that choice.
+Will it work with my headless / PWA Studio frontend?
Yes. The module exposes consent state and data-request operations through service contracts backed by REST and GraphQL endpoints, so a PWA or custom frontend can read and write consent and trigger SAR/erasure requests against the same backend logic the Luma storefront uses.
+Does the extension make my store legally compliant by itself?
No tool can promise legal compliance on its own — compliance also depends on your privacy policy, your processing practices, and your DPO's guidance. What this module gives you is a solid technical foundation: genuine prior blocking, consent logging for Article 7 accountability, and working data-subject-request handling that your legal team can build on.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
GDPR / Cookie Consent Compliance
A build-to-order Magento 2 / Adobe Commerce extension that blocks cookies until consent, supports Google Consent Mode v2 and Microsoft UET, and handles GDPR/CCPA data subject requests with full consent logging. Built, installed, and supported by ECOSIRE on your store.
- True prior blocking — cookies and tracking tags are suppressed until the visitor gives consent, not merely notified after the fact
- Google Consent Mode v2 integration setting ad_storage, analytics_storage, ad_user_data, and ad_personalization based on the visitor's choices
- Microsoft UET consent signaling for Bing Ads / Clarity tag gating
- Right-to-be-forgotten workflow with a cron-driven anonymization queue over customer, quote, and sales_order data