Consent Management

Big Crunch ships a built-in Consent Management Platform (CMP) that implements the IAB Global Privacy Platform (GPP) and Transparency & Consent Framework (TCF) in one bundle. It detects the visitor's jurisdiction, surfaces the right consent UI, persists their choices, and exposes the encoded consent string via window.__tcfapi and window.__gpp.

This page is a guide to the Consent Management section of the Big Crunch dashboard — each subsection below corresponds to a tab. For runtime debugging, see Debugging Consent Management.

Overview tab

The Overview tab controls the high-level runtime gates that decide which regional flows activate on the publisher's site. The CMP bundle is delivered the same to every visitor; these settings tell it which regulatory framework to apply based on the visitor's location.

Enable Big Crunch CMP

United States — Activates US GPP sections, the state-by-state opt-out UI, and the "Do Not Sell or Share My Personal Information" trigger link. CCPA / CPRA / VCDPA / CPA / UCPA / CTDPA / FDBR and other state privacy laws are covered through the IAB MSPA (Multi-State Privacy Agreement) usnat section plus per-non-MSPA-state sections.
Transparency & Consent Framework — Activates the EU and Canada TCF 2.3 API, the consent banner ("A note on your privacy"), Google Consent Mode integration (consent signals pushed to gtag('consent', 'update')), and the EU privacy trigger link.

Both toggles can be on independently. Visitors only see the UI for the framework that applies to their location — a German visitor sees the TCF banner, a Texas visitor sees the US opt-out controls, an Australian visitor sees nothing and the CMP self-marks "not applicable" so downstream bidders don't suppress ad serving.

Jurisdiction

The Publisher country dropdown drives the TCF publisher-country fields encoded in the EU TC string. Selecting Switzerland enables the nFADP carve-out: the CMP auto-sets the TCF PurposeOneTreatment flag and adjusts which legal bases the banner exposes.

Set this to wherever your publishing entity is legally established — not where your visitors come from.

Controls how soon the consent banner appears on the page. It doesn't change what the banner does, and it has no effect on ad serving — just when it shows up.

Conservative (default) — the safe choice for every site. Works correctly on modern JavaScript frameworks like React, Next.js, and Vue.
Eager — shows the banner a little sooner, which helps on image-heavy pages. Use it only on simple, static sites (plain HTML, WordPress, and other classic CMS setups).

When in doubt, leave it on the default. Changes take effect on their own — no edits to your site's code required.

US Settings tab

Per-state behavior for the US opt-out flow. Big Crunch's CMP covers every state with a passed privacy law:

MSPA states — California, Colorado, Connecticut, Utah, Virginia. These share the IAB usnat section.
Non-MSPA states with their own GPP sections — Florida (usfl), Texas (ustx), Iowa (usia), Oregon (usor), Montana (usmt), Delaware (usde), New Hampshire (usnh), New Jersey (usnj), Tennessee (ustn), Nebraska (usne).

Configure the default opt-out values, MSPA service-provider mode, sensitive-data treatment, and any per-section banner copy overrides here. The CMP automatically honors the visitor's browser Global Privacy Control signal — when navigator.globalPrivacyControl === true, sale / sharing / targeted-advertising opt-outs are set to 1 before the modal even renders.

TCF Settings tab

EU and Canada TCF-specific configuration. Big Crunch's CMP is IAB Europe registered (CMP ID 501) and supports TCF 2.3.

Common settings here:

Vendor list — which IAB Global Vendor List vendors the publisher works with. The CMP fetches the canonical GVL and renders the configured subset in the "Manage preferences" view.
Non-TCF partners — partners outside the IAB GVL (e.g., Google's Additional Consent string). The CMP encodes their consent into the AC string alongside the TC string.
Banner copy + legal text — publisher-customized consent notice text.

Editor tab

A live visual editor for the consent banner and "Manage preferences" modal — colors, fonts, button styling, banner position, optional publisher logo. The Inspector pane on the right shows every CSS variable the publisher can override; the Preview pane renders the banner exactly as visitors will see it.

Changes here are persisted to the property config and rolled out through the standard CDN — no publisher snippet change required.

Advanced: troubleshooting

Very rarely, on certain JavaScript-framework sites, Big Crunch's early setup can interfere with how the page loads — for example, layout glitches or content briefly disappearing after you add the CMP. If you run into that, add this tag to your page's <head>, before the Big Crunch script tags, to tell Big Crunch to take the safest, slowest approach:

<head>
  <meta name="bc-cmp-hydration" content="conservative">
  <script async src="https://dist.bigcrunch.com/cmp/cmp.js" data-property-id="..."></script>
  <script async src="https://dist.bigcrunch.com/lighthouse/main.js" id="bigcrunchtag" data-property-id="..."></script>
</head>

Most sites never need this. Reach for it only if you actually see a problem after adding the CMP. It doesn't affect consent collection or ad serving.

Debugging Consent Management — inspect the live GPP string, decode sections, read individual fields from the console.
Installation — the publisher snippet that loads cmp.js alongside Lighthouse.

Support

Questions on what to enable, or what a specific GPP value means in production? support@bigcrunch.com.

Search Documentation