CMP verification
Verify Big Crunch, Inc. by country and state
Check the Big Crunch, Inc. configuration visitors actually receive, the choice it saves, and what your tags do with that choice. Choose a location below for the regional check, routing requirements, and a reusable worksheet.
Interactive example · no site is scanned
A saved rejection can still leave a tag running
Example policy: optional analytics must stay off after refusal. Change the evidence for a Big Crunch, Inc. visitor in Germany and see what you can conclude. These values are teaching fixtures.
01 · REGIONGermanyIntended rule: de
02 · SAVED CHOICEOptional analytics: deniedBig Crunch, Inc. readback after the example refusal.
03 · BROWSER ACTIVITYOptional analytics cookie appearsExample capture window: 10 seconds after the choice. Server-side processing is outside this fixture.
Investigate the mismatch
The saved choice is readable, but observed activity conflicts with the example policy. Trace the affected integration and retest after deployment.
Build your repeatable test plan
6 worksheet rows. First load, acceptance, and refusal each use fresh sessions. The worksheet records actual region, selected rule, expected policy, saved state, and observed activity.
Read the generated test plan
Independently verify Big Crunch, Inc. on https://example.com for a visitor in Germany. CookieTrail offers a Germany country route (de). Confirm the CMP's selected rule in the evidence before interpreting the result. Trace the first tag before the banner is clicked. Start a new browser session and compare the first nonessential cookie or request with the time the consent defaults were set. A German banner can appear after a tag has already run. Run these paths: first load, accept optional categories, reject / opt out. Use fresh isolated sessions for first load, accept, and reject; withdrawal uses its own earlier acceptance. Record the URL, deployed version, actual visitor region, selected CMP rule, expected policy, saved state, cookies, requests, and capture window. Use the installed CMP's documented readback; missing data is inconclusive. Do not equate a TCF applicability flag or a banner language with geography. Compare saved choices with observed behavior against the team's stated policy. A request alone does not establish a violation; Google advanced Consent Mode may send cookieless requests. Do not assume browser evidence covers server-side tracking. Investigate mismatches in my repository and explain each finding with evidence. After I deploy a fix, repeat the same URL, regional rule, and paths, then compare both evidence sets. CookieTrail can capture its supported country routes through its workspace/API/MCP. State/province routing, browser preference signals, and withdrawal require separate verified manual or external browser tests; do not claim those are built-in automated paths. This is a technical test, not legal certification.
Country-route capture is available for CookieTrail’s supported locations. Precise state/province routing, withdrawal, and browser preference signals need separate manual or external tests.
Read Big Crunch, Inc.’s saved state
Check Big Crunch, Inc.'s TCF identity and the site's purpose mapping.
- Record the Big Crunch, Inc. script or plugin version, configuration identifier, and published regional rule. Check the deployed site rather than a dashboard preview.
- If this installation enables the IAB Transparency and Consent Framework (TCF), compare its returned cmpId with 501, the ID in Google's inventory. An absent TCF API may simply mean TCF is not enabled.
- Map each saved category or purpose to the site's actual tools. Compare those tools' storage and requests before and after the visitor's decision.
Optional TCF identity and purpose snapshot · CMP ID 501
Use this only when TCF is enabled. Run it again after each decision. The CMP ID identifies the platform; it is not an advertising vendor ID. Compare purpose and vendor permissions separately.
(() => {
if (typeof window.__tcfapi !== "function")
return { status: "TCF unavailable or disabled" };
window.__tcfapi("addEventListener", 2, (data, ok) => {
if (!ok || !data ||
!["tcloaded", "useractioncomplete"].includes(data.eventStatus))
return;
console.log({
cmpId: data.cmpId,
expectedCmpId: 501,
identityMatches: data.cmpId === 501,
cmpStatus: data.cmpStatus,
eventStatus: data.eventStatus,
gdprApplies: data.gdprApplies,
purposeConsents: data.purpose?.consents,
purposeLegitimateInterests: data.purpose?.legitimateInterests
});
window.__tcfapi("removeEventListener", 2,
() => {}, data.listenerId);
});
})()A TCF applicability flag does not verify geography. Legitimate-interest fields and consent fields have different meanings; rejection does not imply every field becomes false. This uses the documented TCF event API; getTCData is deprecated.
These procedures use documented readbacks or manual saved-state checks. They do not imply that CookieTrail has an automated native adapter for every installation. Big Crunch, Inc. is identified in Google’s referenced CMP inventory or partner list.
Choose a visitor location
- Verify Big Crunch, Inc. in GermanyTrace the first tag before the banner is clicked.
- Verify Big Crunch, Inc. in FranceSeparate a claimed audience-measurement exemption from advertising consent.
- Verify Big Crunch, Inc. in SpainFollow the reject path from the first banner layer.
- Verify Big Crunch, Inc. in ItalyTest closing the banner separately from granting consent.
- Verify Big Crunch, Inc. in NetherlandsCompare the visible category choices with the saved decision.
- Verify Big Crunch, Inc. in IrelandCheck withdrawal after an earlier acceptance.
- Verify Big Crunch, Inc. in NorwayCheck the EEA rule as well as the EU country list.
- Verify Big Crunch, Inc. in United KingdomCheck whether an EU-only configuration leaves the UK on a fallback.
- Verify Big Crunch, Inc. in SwitzerlandCheck the Swiss rule explicitly; an EU label is not enough.
- Verify Big Crunch, Inc. in QuebecProve that the CMP selected Quebec, rather than Canada generally.
- Verify Big Crunch, Inc. in CanadaKeep the province in the test record.
- Verify Big Crunch, Inc. in CaliforniaTest sale/share opt-out and browser preference signals separately from cookie rejection.
- Verify Big Crunch, Inc. in ColoradoCheck the universal opt-out path independently of the banner buttons.
- Verify Big Crunch, Inc. in ConnecticutCheck how a browser opt-out reaches the deployed tag configuration.
- Verify Big Crunch, Inc. in DelawareCheck a named state rule against the national fallback.
- Verify Big Crunch, Inc. in IndianaCheck that the deployed state configuration matches the approved release.
- Verify Big Crunch, Inc. in IowaKeep a sensitive-data choice distinct from advertising opt-out.
- Verify Big Crunch, Inc. in KentuckyRetest the Kentucky rule after a CMP configuration rollout.
- Verify Big Crunch, Inc. in MarylandInclude the data-purpose inventory alongside the cookie test.
- Verify Big Crunch, Inc. in MinnesotaTest the consumer request link as well as the banner.
- Verify Big Crunch, Inc. in MontanaCheck state-list updates rather than relying on an old regional template.
- Verify Big Crunch, Inc. in NebraskaTrace opt-out through every advertising integration.
- Verify Big Crunch, Inc. in New HampshireTest a browser signal that conflicts with an earlier saved preference.
- Verify Big Crunch, Inc. in New JerseyCheck grouped state rules for a missing New Jersey entry.
- Verify Big Crunch, Inc. in OregonCheck browser preference signals and ordinary opt-out as separate paths.
- Verify Big Crunch, Inc. in Rhode IslandInclude the privacy notice and its request path in the regional test.
- Verify Big Crunch, Inc. in TennesseeCheck the rule on a second page after the visitor opts out.
- Verify Big Crunch, Inc. in TexasKeep consent defaults and targeted-advertising opt-out separate.
- Verify Big Crunch, Inc. in UtahDefine expected opt-out behavior without copying an EU reject-all model.
- Verify Big Crunch, Inc. in VirginiaVerify the selected state independently of the US East route.
- Verify Big Crunch, Inc. in FloridaSet business scope before defining the Florida test expectation.
- Verify Big Crunch, Inc. in United StatesCheck the country fallback separately from each named state.
- Verify Big Crunch, Inc. in SingaporeRecord the purpose and personal data behind each cookie category.
- Verify Big Crunch, Inc. in BrazilCompare the local banner controls with the saved purpose choices.
- Verify Big Crunch, Inc. in AustraliaInspect tracking pixels as well as browser cookies.
- Verify Big Crunch, Inc. in JapanCheck the purpose mapping rather than importing an EU banner expectation.
- Verify Big Crunch, Inc. in South KoreaInclude behavioral-advertising integrations in the evidence record.
- Verify Big Crunch, Inc. in South AfricaTie the browser test to the team's declared processing purposes.
- Verify Big Crunch, Inc. in New ZealandCheck whether the local visitor receives the intended global fallback.