The Consent Management Platform Built for CMOs 

It depends on where and how you show it. About half of all visitors ignore or dismiss a consent banner. In opt-in regions like California, ignored visitors stay untracked because consent defaults to false on page load. In opt-out regions, consent defaults to true, so ignored visitors are still tracked normally. The move is geofencing: run opt-in only where the law demands it, opt-out where required, and no banner everywhere else. That keeps your consented traffic as high as possible while avoiding lawsuits.

Yes. You set rules per region using IP-based geofencing. California gets opt-in (blocked on page load until the visitor accepts). States like Colorado or Connecticut get opt-out (consent granted by default, but visitors can withdraw). States with no privacy law default to "don't show," meaning no banner fires and you track normally. 

Opt-in: consent is false on page load. Meta, Google Ads, analytics, attribution tools are all blocked until someone clicks accept. Opt-out: the banner shows, but consent is true on page load. All your tags fire immediately. Visitors can still decline, but they have to actively choose that.

The impact on your ad spend: under opt-in, anyone who ignores the banner generates zero trackable data. Under opt-out, those same visitors flow through to your analytics. California requires opt-in. Most other US state privacy laws are opt-out. The mode you set per region directly controls how much attribution data you keep.

Any tool that runs on a non-essential cookie is subject to consent. If a visitor is in an opt-in region and doesn't accept, that tool won't fire for that session. For Shopify stores, native apps already respect Shopify's Customer Privacy API, which is how we set consent. Tools injected directly into theme code (like North Beam's script) need a custom snippet to bring them into the consent framework. We write that during onboarding at no extra cost. You'll still get sales from opt-in regions. You just won't attribute the campaign source for visitors who didn't consent.

Show an opt-in banner in California with equal opportunity to accept or decline. Set all other regions to "don't show." That means the only visitors you lose tracking on are Californians who decline or ignore the banner. For states that require opt-out, design the banner with just "accept all" and "manage cookies" with no decline button. Consent is already true, so if they do nothing, your tags keep firing. Most of our e-commerce clients run this exact setup.

The consent dashboard breaks traffic into consented and unconsented page views, then tells you why visits went unconsented. Three reasons: someone explicitly declined, someone was in an opt-in region and ignored the banner (so consent stayed false), or a returning visitor had a saved decline from a previous session. You can filter by region, domain, and time period. So when GA4 shows 100K views but you expected 150K, the dashboard tells you whether the gap is from overly conservative regional settings, underperforming banner UX, or returning declines.

For Shopify stores using native apps, no. Banner design, region settings, cookie categorization, and consent rules are all configured in the dashboard. If you use Google Tag Manager, there's a one-time template install, then your marketing ops team manages tag changes directly in GTM without dev tickets. For tools that don't play nicely with GTM, our team handles the custom integration during onboarding. Banner copy, design changes, and A/B tests are all done in the interface without touching code.

Pricing is based on two things: primary root domains and total monthly unique visitors across all of them. Subdomains share consent with their parent and don't count as separate domain slots. Plans include a set number of domains with room to add more. If you spike during Black Friday and temporarily exceed your visitor cap, there's a modest top-up rather than an automatic plan upgrade.