Checklist
What is the difference between a cookie notice and cookie consent?
A cookie notice informs visitors. Cookie consent is a choice you check on Fresh and Reject. Banner text alone does not prove marketing waited.
In brief
A cookie notice tells visitors that cookies or similar tech are in use. Cookie consent is a choice to accept, reject, or manage non-essential categories, with runtime that matches the choice. Banner text alone does not prove marketing waited. Check Fresh, and Reject when that control exists. ConsentProbe can store those packs. A free US-baseline scan is not an EU or California legal conclusion. This page is not a CMP design guide and not legal advice.
Not legal advice
This FAQ explains how to distinguish a cookie notice, which is informational banner text, from a cookie consent mechanism, which is a choice that should gate marketing and other non-essential tags in practice. It is not legal advice, not a CMP design tutorial, and not a GDPR, ePrivacy, CPRA, or other compliance certificate. ConsentProbe reports are technical observations of what fired. They do not say what counsel would allow.
Last updated September 27, 2026. The audit-versus-banner page positions an audit against a CMP. The CMP claims guide compares a written claim with runtime. The before-Accept audit and the pre-consent checklist own the first-load method. The Reject-as-easy page records whether Reject is as available as Accept. This page stays on notice text versus a choice mechanism.
Short answer
A cookie notice tells visitors that cookies or similar tech are used. Cookie consent is a choice mechanism that lets the visitor accept, reject, or manage non-essential categories, with runtime behavior that matches that choice. Banner text such as "we use cookies" does not prove that marketing waited for a choice.
A cookie consent audit asks which cookies, storage entries, and network requests appeared before any Accept, and whether a Reject control, when one is present, stopped marketing fan-out. Treat notice copy as a claim about information. Treat consent UI labels as claims about gating. Falsify both with a clean Fresh visit and, when a Reject control exists, a Reject visit.
ConsentProbe can produce Fresh and Reject packs with request, cookie, and screenshot links. A free US-baseline scan is not an EU or California legal conclusion. ConsentProbe does not write banner copy, does not install a CMP, and does not decide whether consent is valid. Observation is not counsel permission. This page is not a CMP design guide and not legal advice.
Notice, choice, and the audit
Three labels get mixed on a storefront that already shows a bar. Separate them before you write the finding. Write that finding as a marketing request on Fresh under a notice-only bar. Leave legal permission with counsel.
| Term | What it usually means on a storefront | What it does not prove alone |
|---|---|---|
| Cookie notice | An informational bar or footer line about cookies | That marketing waited for a choice |
| Cookie consent mechanism | A UI that offers Accept, Reject, or category choices | That runtime matched the choice. The CMP claims guide is that check |
| Cookie consent audit | A labeled Fresh or Reject observation of cookies, requests, and screenshots | Legal clearance or counsel permission |
Notice-only patterns to falsify
Read each row as something a browser test can catch. A missing Reject control is a record of the UI you saw. This page does not invent a regional legal requirement, and it does not redesign the banner. When an EU or California conclusion is the claim, use those regional paths. The free versus paid guide draws that line.
| What you see | Fresh check | Red flag |
|---|---|---|
| We use cookies, with only OK or dismiss | Marketing hosts stay quiet if non-essential tags claim to wait | Ads or analytics IDs before any clear Accept |
| Accept, and no equal Reject | Document the UI. Capture Fresh, and any buried Reject path | Marketing looks the same on Fresh and after dismiss. The Reject-as-easy page is that UI note |
| Full CMP categories | The screenshot records the category claims | Runtime still fans out after Reject. The CMP claims guide is that mismatch |
Fresh and Reject on the storefront
These steps compare notice copy and choice labels with cookies and requests. They do not design a banner, pick button colors, or decide when consent is valid. The audit-versus-banner page holds the audit-versus-CMP split. The CMP claims guide holds a claim that disagrees with runtime. The before-Accept audit, the pre-consent checklist, and the Reject-as-easy page hold the neighboring checks.
- Use a clean profile. Load the storefront once. Do not click Accept. If a dismiss or OK control is the only button, leave it unclicked and note what it says.
- Capture cookies, storage, and Network. Screenshot the banner. Label the pack Fresh.
- If Reject All or an equivalent exists, open a new clean profile, click Reject, and navigate once more. Label the pack Reject.
- If the page only shows a notice or an OK button, record that UI and keep the Fresh pack for any marketing fan-out.
- Compare Fresh with Reject when both exist. Write one finding sentence per mismatch, such as a marketing host on Fresh under a notice-only bar.
- Repeat the same URL after a tag change, and keep the Fresh and Reject labels on the new packs.
When notice-only bars get slow
Sorting a notice-only bar from a real choice across templates takes a long time when you also need host-level proof. ConsentProbe runs Fresh, and Reject when that control exists, on the storefront URL. Each finding stays tied to a request, a cookie, or a screenshot.
Use the free US-baseline visit when you want the report format. Use paid EU or California scenarios when those regions are the claims. The free versus paid guide draws that line. ConsentProbe does not rewrite the banner, does not install a CMP, and does not issue a certificate.
FAQ
What is the difference between a cookie notice and cookie consent?
A notice informs visitors. Consent is a choice mechanism. Verify the gate with Fresh and Reject runtime, not with banner copy alone.
Is a "we use cookies" bar the same as consent?
No. The text does not prove a marketing choice happened, or that the storefront honored one.
If there is no Reject button, is Fresh still useful?
Yes. Fresh shows what fired before any Accept or dismiss. Record that the Reject control was absent.
Does a CMP category UI guarantee the choice was honored?
No. Category labels are claims. The CMP claims guide is the runtime check.
How is this different from audit versus banner?
That page positions an audit tool against a CMP. This FAQ defines notice text against a choice mechanism.
Is this legal advice?
No. These are technical observations. Observation is not counsel permission. ConsentProbe does not replace counsel, and it does not install a CMP.
Limits of this page
This page defines a cookie notice against a cookie consent mechanism, and it tells you how to falsify a notice-only bar with Fresh and, when present, Reject. It is not legal advice, not a CMP design guide, and not a certificate. Observation is not counsel permission. ConsentProbe reports stay tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU or California legal conclusion.
Related guides
Open the audit-versus-banner page when a banner is treated as an audit, the CMP claims guide for claims versus runtime, the before-Accept audit and the pre-consent checklist for the first load, and the Reject-as-easy page when Reject is harder to reach than Accept.
- What is the difference between a cookie consent audit and a cookie banner?
- CMP claims vs runtime evidence: how do you prove the banner actually works?
- Pre-Consent Cookie Audit: A Storefront Checklist
- Does Reject All have to be as easy as Accept?
- Pre-consent audit checklist: what to verify before Accept
- Reject All Still Tracking: What to Check After You Say No
- What belongs in a cookie consent audit evidence pack?
- What does a free US-baseline cookie audit prove vs paid EU or California scans?
- Which cookie consent test should you run first?
- Does Reject All stop marketing pixels?
- ConsentProbe methodology
- Pricing and listed regional products
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 audit: 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.