Cookie Consent for
Miva Stores
B2B, DTC & Multi-Storefront.
Miva powers serious mid-market and enterprise eCommerce — B2B wholesale, DTC retail, and hybrid operations running complex product catalogues across multiple storefronts. Every one of those storefronts fires tracking scripts to visitors in the EU, California, and beyond. Miva has no built-in consent management. ConsentPixel — Privacy · Verified does. One script tag, no module installation, full compliance.
Why Miva Stores Face Elevated Privacy Risk
Miva's strength as a platform — its deep customisability, rich integration ecosystem, and ability to run complex B2B and DTC operations from a single admin — also means that a typical Miva store carries a significantly richer stack of third-party data-sharing relationships than a simpler platform might. ERP integrations, marketing automation, analytics platforms, CRM connectors, loyalty programmes, and advertising pixels all introduce data flows that privacy law increasingly regulates.
The merchants who have built on Miva for years — industrial suppliers, specialty retailers, wholesale distributors — are precisely the businesses that EU DPAs and CIPA plaintiff firms are targeting in 2026. The assumption that "we're B2B, privacy law doesn't apply to us" is incorrect and expensive. GDPR applies to any personal data processed about natural persons. CCPA and CIPA apply to any California resident who visits your store, whether they are buying for business or personal use.
Miva's MultiStorefront capability adds a further layer. A brand running a US wholesale portal, a European retail storefront, and a UK direct-to-consumer channel from one Miva instance must apply different consent rules to each storefront — GDPR opt-in for the EU, UK GDPR for Britain, CCPA opt-out for California. Managing that complexity without a purpose-built consent platform is an operational risk as well as a legal one.
Trackers Commonly Running on Miva Stores
Miva's integration ecosystem connects to a wide range of marketing, analytics, and operational tools. These are the most common tracking integrations on Miva stores — and the specific compliance exposure each creates.
The B2B Privacy Risk Miva Merchants Often Overlook
Miva is specifically built for B2B and hybrid B2B/DTC merchants — it is one of the platform's core differentiators. This creates a compliance blind spot that is worth addressing directly: many B2B Miva merchants assume that because they sell to businesses rather than consumers, privacy law does not apply to them. That assumption is incorrect under every major privacy framework.
GDPR applies to any personal data processed about natural persons — including named purchasing agents, account contacts, and trade account holders on your B2B storefront. The fact that they are visiting for business purposes does not exempt their personal data from GDPR protection.
CCPA and CIPA similarly apply to California residents who visit your store, regardless of whether they are buying for personal or business use. A procurement manager visiting your Miva wholesale portal from California who has session-replay running on their account page is a potential CIPA plaintiff.
🏢 B2B Account Portals
Trade account holders are natural persons under GDPR. Session-replay on login and account management pages carries CIPA exposure.
📋 Quote Request Forms
Form interactions recorded by session-replay tools on quote pages capture personally identifiable business contact information — high CIPA risk.
🔐 Customer Segmentation Data
Miva's account-specific pricing and product visibility features create rich customer profiles. These profiles constitute personal data under GDPR and require lawful basis for processing.
📊 Wholesale Analytics
Analytics tools tracking named B2B accounts by email or user ID process personal data. GDPR consent or legitimate interest documentation is required.
Miva Built-In vs. ConsentPixel
Miva's platform offers deep customisation and a powerful integration ecosystem — but consent management is not part of its native feature set. Here is how the gap looks in practice.
| Capability | Miva Native | ConsentPixel |
|---|---|---|
| Cookie consent banner | ✗ Not included | ✓ Deployed via single script tag |
| Technically blocks scripts before consent | ✗ No | ✓ Always |
| Google Consent Mode v2 (all 4 parameters) | ✗ No | ✓ All plans |
| Global Privacy Control (GPC) detection | ✗ No | ✓ Auto-detected |
| MultiStorefront per-channel consent config | ✗ No | ✓ Full support |
| CIPA session-replay blocking | ✗ No | ✓ Yes |
| US state law opt-out (19 states) | ✗ No | ✓ All plans |
| Consent audit log (timestamped) | ✗ No | ✓ All plans |
| Automatic tracker scanning | ✗ No | ✓ Continuous |
| No Miva module required | N/A | ✓ One script tag in global header |
See every tracker firing on your Miva store before consent
ConsentPixel scans your store — including B2B account pages and checkout flows — and shows you exactly which scripts share visitor data before any consent is given.
How to Install ConsentPixel on Miva
ConsentPixel installs on Miva as a single script tag in your store's global header — no Miva module download, no marketplace installation, no compatibility dependencies. The pixel must load before every other third-party script in your store head. Installation takes under five minutes.
Create your ConsentPixel account and scan your Miva store
Sign up at consentpixel.com, add your Miva store domain, and run the auto-scanner. ConsentPixel maps every tracker and cookie across your storefront — including those introduced through Miva Connect integrations, marketing modules, and third-party scripts in your global header. Copy your unique pixel snippet from the dashboard.
For MultiStorefront setups, create a separate site in your ConsentPixel dashboard for each Miva storefront and configure the appropriate consent rules per jurisdiction before generating its pixel snippet.
Add the pixel to your Miva Global Header — first script in head
In your Miva admin, navigate to Menu → User Interface → Global Header. Paste the ConsentPixel snippet as the very first item inside the <head> tag — before your Google Tag Manager snippet, before Google Analytics, before any other third-party script. This positioning is critical: ConsentPixel must read the visitor's consent state before any tracking tag has a chance to fire.
<head>
<!-- ConsentPixel — must be FIRST script in head -->
<script
src="https://pixel.consentpixel.com/YOUR-SITE-ID.js"
async></script>
<!-- Your existing head scripts follow below -->
<!-- GTM, GA4, Meta Pixel etc. -->
</head>
Register your tracking integrations by consent category
In the ConsentPixel dashboard, register each tracker with its consent category: Analytics (GA4, Hotjar), Marketing (Meta Pixel, Google Ads, Klaviyo, TikTok), Functional (live chat, loyalty tools), and Session Recording (Clarity, Lucky Orange). ConsentPixel will conditionally fire each integration only when the visitor has consented to that category — or suppress it entirely for GPC opt-out visitors and non-consenting EU visitors.
For Miva Connect integrations that inject client-side scripts, review each integration's JavaScript output and register any third-party domains that appear in the tracker scan.
Configure Google Consent Mode v2
Enable Google Consent Mode v2 in your ConsentPixel dashboard. This automatically passes all four GCM v2 parameters (analytics_storage, ad_storage, ad_user_data, ad_personalization) before any Google tag loads — protecting Google Shopping and Google Ads conversion measurement for EU and UK visitors.
For MultiStorefront — repeat per storefront channel
Each Miva storefront has its own Global Header. Install the storefront-specific ConsentPixel snippet in each storefront's Global Header separately, using the correct site ID for that channel. This gives each storefront its own independent consent configuration, consent log, and GPC signal handling — while all remaining manageable from your single ConsentPixel dashboard.
Verify with the ConsentPixel compliance checker
Use the compliance checker to confirm: no scripts fire before consent on a fresh session across all storefronts, GCM v2 parameters are passing correctly, session-replay tools are excluded from B2B account and checkout pages, and consent events are being logged separately per storefront.
What ConsentPixel Does for Your Miva Store
Script blocking across all pages
Every registered tracker is held at page load — product pages, category pages, B2B account portals, quote forms, and checkout. Nothing fires until the visitor's consent state is established, eliminating GDPR violations and CIPA checkout exposure.
MultiStorefront per-channel consent
Each Miva storefront gets its own independent consent configuration and consent log. GDPR opt-in for EU storefronts, CCPA opt-out for US, UK GDPR for British channels — all managed centrally, applied automatically per storefront.
Google Consent Mode v2
All four GCM v2 parameters fire before any Google tag loads. Protects Google Shopping, Google Ads, and GA4 conversion measurement for EU and UK visitors. Non-consenting sessions are modelled by Google rather than lost entirely.
B2B buyer data protection
Consent-gates analytics, session-replay, and marketing automation on B2B account portals and trade pages — protecting personally identifiable business contact data under GDPR and CIPA where session interactions are recorded.
Per-storefront consent audit log
Every consent decision is timestamped with banner version, choices made, and signal source — maintained separately per storefront channel for jurisdiction-specific audit records. Exportable on demand for DPA investigations.
Continuous integration scanning
ConsentPixel scans your store on a schedule and alerts you when new trackers appear — including those introduced through Miva Connect integration updates. Your consent configuration stays current without manual quarterly audits.
Miva Privacy Compliance Checklist (2026)
Run through this checklist for your Miva store. Click each item to mark it complete.
Frequently Asked Questions
Your integrations. Your buyers.
Actually protected.
One script tag in your Miva Global Header. No module. No compatibility issues. Full GDPR, CCPA, CIPA, and 19-state US compliance — with MultiStorefront support, B2B buyer data protection, and Google Consent Mode v2 built in from day one.