Checklist
Cookie audit: which test to run first
Cookie audit map: choose a before-Accept, Reject versus Accept, EU three-way, or GPC test. A free US scan is not an EU or California result.
In brief
Use the free cookie audit tool, then match the claim. Use a before-Accept audit when tags may fire before a choice, Reject versus Accept when Reject looks ignored, EU fresh, Reject, and Accept for an EU or UK region, and a GPC pair for a California opt-out. Label cookies, requests, and screenshots. A banner image is not a cookie audit. A free US-baseline scan is not an EU or California conclusion. This hub is a testing map, not legal advice.
Not legal advice
This hub maps which cookie audit to run for a given claim. It is not legal advice, not a compliance certificate, and not a guarantee that any site meets GDPR, CPRA, ePrivacy, CIPA, or any other rule. ConsentProbe reports are technical observations. Observation is not counsel permission.
Last updated September 28, 2026. Each branch below stops after the choice of test and points at the guide that owns the steps.
Short answer
A cookie audit is a labeled runtime check of cookies, storage, and network requests under Fresh, Reject, Accept, or GPC-on. Pick the cookie audit that matches the claim you need to defend. If tags may fire before any choice, start with a before-Accept audit. If Reject All may be ignored, run Reject versus Accept. If a California sale or share opt-out is the claim, run GPC-off versus GPC-on. EU or UK claims use the fresh, Reject, and Accept guide.
Attach cookies, requests, and screenshots so engineering or counsel can reproduce the finding. A banner screenshot alone is not a cookie audit. ConsentProbe is a cookie audit tool, not a CMP. A free US-baseline scan is not an EU or California or GPC conclusion. This hub maps which guide to open next. It is not legal advice and not a compliance certificate.
Decision tree
Read the row that matches the sentence you will actually defend. That row is the cookie audit, and it names which test to run for the claim. Then open the deep guide. Do not run every scenario because the table lists them. When the row is Reject All or GPC, open free checks for the short page.
Swipe to see more
| Your situation | Run this first | Deep guide |
|---|---|---|
| Pixels or cookies before any click | Pre-consent checklist | Pre-consent checklist, then the storefront checklist or the Shopify pre-consent list |
| Banner present, and Reject may be ignored | Reject versus Accept, and a fresh visit | Reject All leftovers; on Shopify, the Reject All storefront guide |
| EU or UK regional conclusions | EU fresh, Reject, and Accept | EU three-state audit |
| A CMP line that says the shop honors GPC | GPC off versus GPC on | GPC test, then the claims mismatch guide; on Shopify, the GPC honor test |
| Counsel or engineering need a reproducible pack | Evidence pack | Evidence pack, then how to read the report |
| Unsure whether you need an audit or another banner | Positioning | Cookie consent audit versus banner |
| California lawsuit-theory context, at a high level | A theory map, then a storefront test | CIPA pen-register versus wiretap, then SB 690, then back to the pre-consent checklist |
If tags may fire before a choice
Start with the pre-consent checklist. Load a clean profile, do not click Accept, and record cookies, storage, and third-party requests.
The storefront checklist is the longer pass for the same moment. On Shopify, the Shopify pre-consent checklist covers pixels, theme embeds, and app scripts. An unclicked banner does not show that those scripts waited, so before a sale, run the Black Friday consent checklist.
If Reject All looks ignored
Run Reject versus Accept, with a fresh visit beside them and a clean profile per state. The Reject All leftovers guide is the network check. On Shopify, use the Reject All storefront guide, which also notes the Customer Privacy API limit. For that Reject visit, follow the steps in that guide. The free Reject All tracking page explains what a free scan covers and what it does not.
If the question is whether Reject is as easy to reach as Accept, open the reject-ease guide and still check the network. The button and the request list are separate rows.
If the claim is an EU or UK region
Use the EU fresh, Reject, and Accept guide. Three labeled visits are the comparison. A free US-baseline scan is one non-California pass for report format, and it does not stand in for that trio.
A locale or a timezone is not a regional IP. The free versus paid guide says when the paid EU scenarios are the file you show.
If the claim is California or GPC
Run GPC off and GPC on. The GPC test guide covers Sec-GPC: 1. The GPC signal present but marketing still loads page covers a detected message that arrives after pixels have fired. After the header and the host list are on the file, run the free GPC honor check.
On Shopify, open the Shopify GPC honor test for theme Liquid, app embeds, customer events, and pixels. The Customer Privacy API records a preference and does not by itself block scripts. Paid California or GPC scenarios are the regional ConsentProbe path.
If you need a pack, a banner decision, or a theory map
When engineering or counsel asked for files they can reproduce, build the evidence pack: one URL, one state name, cookies, request URLs, and screenshots. Reproducible artifacts live on the cookie consent evidence pack guide. The report-reading guide walks scope, scenario, finding, and evidence number.
When the banner text and the network disagree, open CMP claims versus runtime evidence. A CMP stores a choice. An audit records what the browser did. ConsentProbe does the second job.
For California website-tracking theories, read the CIPA pen-register versus wiretap page and the SB 690 note, then return to the pre-consent checklist. This hub does not restate those pages.
What every serious run shares
The scenario changes. The file shape does not. A reviewer should be able to line two states up without guessing which click produced which export. Open the browser cookie audit product when you want that record from a product run.
- One clean profile per consent state. Do not reuse the Accept profile for Reject or for GPC on.
- The exact button text, or the GPC enable method, written on the file.
- A cookie table, a third-party request list, and screenshots from that same state.
- A finding sentence that points at one of those surfaces. The evidence pack guide is the field list.
- Region honesty. A free US-baseline visit is not an EU or California conclusion. See the free versus paid guide.
When is a free US scan enough?
Start free when you are learning the report shape or hunting an obvious pre-consent load. The free US baseline versus paid EU or California page says which sentence each scan can support. Use a paid scenario when the sentence you will show names the EU, the UK, or California, or when you want the labeled pack without building a HAR by hand.
Findings stay linked to a request, a cookie, or a screenshot. A regional scenario name does not turn the report into a certificate, and the audit does not replace a CMP.
The button below still starts a free US-baseline audit. The cookie audit product page is the browser recording of cookies and requests before Accept.
Swipe to see more
| Claim you want | Free US-baseline | Paid path |
|---|---|---|
| Learn the report format, or spot an obvious pre-consent load | Useful | Optional |
| EU Reject All compared with Accept | Not enough | EU fresh, Reject, and Accept scenarios |
| California or GPC behavior | Not enough | California or GPC scenarios, with the GPC guides |
| A shareable pack for engineering or counsel | You can build the folder by hand | Labeled findings tied to a request, a cookie, or a screenshot |
Shopify shortcut
Pre-consent on Shopify is the Shopify pre-consent checklist. Reject All is the Shopify Reject All guide. If someone calls the Customer Privacy API a firewall, read the Shopify Customer Events versus the Privacy API page: the API records consent, and theme or pixel scripts still load unless their own code waits. GPC is the Shopify GPC honor test, two clean visits with Sec-GPC confirmed on the second file.
Does an easy Reject button mean tags stop?
If Reject is harder to reach than Accept, open the reject-ease guide and screenshot the controls. That page reads a public CNIL note about design. It does not decide that a banner meets French or EU law.
Then compare cookies and requests after Reject with the same surfaces after Accept. The Reject All guides own that network half. UI ease and runtime blocking stay in different files.
FAQ
What is a cookie audit?
A labeled runtime observation of cookies, storage, and requests under a consent state. A banner screenshot alone is not a cookie audit.
Which cookie audit should I run first?
Follow the decision tree on this hub. Start with a before-Accept cookie audit when tags may fire with no click.
Is a cookie banner enough?
A banner collects a choice. An audit keeps labeled cookies, requests, and screenshots. Read the CMP claims guide and the evidence pack guide.
When is the free US scan enough?
When you are learning the report format or spotting an obvious pre-consent load. It is not an EU Reject conclusion or a California or GPC conclusion. See the free versus paid guide.
When do I need paid EU or California scenarios?
When those regional claims are what you will show counsel, a partner, or engineering. A locale setting does not replace that scenario.
Where do Shopify merchants start?
The Shopify pre-consent checklist, the Shopify Reject All guide, and the Shopify GPC honor test. Open the Shopify Customer Events versus the Privacy API page if someone treats Customer Privacy as a script blocker.
Is this hub legal advice?
No. It is a testing map. It is not a compliance certificate and not a substitute for counsel.
Limits of this page
This hub maps which cookie consent test to run, and which guide owns the steps. It is not legal advice, not a compliance certificate, and not a guarantee that any site meets GDPR, CPRA, ePrivacy, CIPA, or any other rule. ConsentProbe reports remain technical observations tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU or California conclusion.
Related guides
Open the first-party versus third-party cookies page and the SB 690 lawsuit FAQ from this list, then the EU audit, the evidence pack, and the pre-consent checklist.
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.
Save a US-baseline technical record
After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.