Checklist
Do I still need a Reject All test if Accept All looks fine?
Accept All looking clean does not prove Reject or Fresh. Separate the three paths, then rerun Fresh and Reject. Not legal advice.
In brief
A clean Accept All visit shows what loads after the visitor opts in. It leaves Fresh, the load before any choice, and Reject All untested. Marketing tags can stay quiet after Accept and still fire on Fresh or after Reject. Keep three labeled packs. ConsentProbe can store Fresh and Reject evidence. A free US-baseline scan is not an EU or California legal conclusion. This FAQ is not a rewrite of the Reject All runbook and not legal advice.
Not legal advice
This FAQ explains why a clean Accept All path does not prove that Reject All, or Fresh before any choice, held. It is not legal advice, not a CMP install guide, 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. Observation is not counsel permission.
Last updated September 28, 2026. The Reject leftovers guide owns a Reject failure. The marketing-pixels FAQ owns the wider pixel question. This page does not rewrite either one. The EU fresh, reject, and accept guide owns the side-by-side scenario set. The retest guide owns what to rerun after a fix. This FAQ answers whether Accept-only is enough.
Short answer
Yes. Still run Fresh and Reject All when Accept All looks clean. Accept, Reject, and Fresh are separate runtime paths. A clean Accept All visit shows what loads after the visitor opts in. It does not show what loaded before any choice, and it does not show what still loads after Reject All.
Marketing tags, analytics cookies, and third-party hosts can stay quiet on the Accept path and still fire on Fresh or after Reject. Treat a clean Accept capture as one labeled scenario. Keep Fresh and Reject as separate runs, each with Network, cookie, and screenshot evidence.
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 install a CMP and does not configure Accept or Reject behavior. This page is not a rewrite of the Reject All runbook or the marketing-pixels FAQ, and not legal advice. Observation is not counsel permission.
Three paths
Accept-only testing never opens the other two columns. Write the finding as a host present on Fresh, or a host present after Reject, when the Accept column stayed quiet. Leave permission with counsel.
| Path | What you label | What Accept-only misses |
|---|---|---|
| Fresh, no Accept or Reject yet | Pre-choice load | Tags that fire before any click |
| Reject All | Post-Reject load | Tags that ignore Reject while Accept stays quiet |
| Accept All | Post-Accept load | The path you already checked |
Why an Accept-only pass leaves gaps
Many CMP and tag setups gate on a marketing-granted state. Accept grants that state. Reject denies it. Fresh is neither. A tag that stays quiet after Accept can still inject on first paint, before the banner choice.
The same tag can stay quiet after Accept and still fire after Reject when the Reject wiring is broken. The Reject leftovers guide is that network check. This FAQ does not replace it.
EU-facing claims often need Fresh, Reject, and Accept side by side. The EU scenario guide owns that comparison. Accept-only is one column of it.
After a fix, retest the path you fixed. An Accept column that still looks fine does not close a Reject ticket. The retest guide owns that rerun. The marketing-pixels FAQ stays the wider pixel question. This page does not paste those bodies.
Fresh and Reject when Accept already looks fine
These steps add the two paths Accept never opened. They do not install a CMP, redesign a banner, or rank vendors. The testing hub and the pre-consent checklist say which pass to run next.
- Use a clean profile. Load the storefront once. Do not click Accept or Reject. Capture Network, cookies, storage, and the banner. Label the pack Fresh.
- Open a new clean profile. Click Reject All. Navigate once. Recapture the same layers. Label the pack Reject.
- Keep the Accept capture you already have as the third column.
- Write one finding sentence per mismatch, such as a marketing host on Fresh, the same host after Reject, and a quiet Accept column.
- If Reject still shows that host, open the Reject leftovers guide and keep the evidence pack.
- After a fix, rerun the path you changed. Do not close the ticket because Accept still looks fine.
When Accept-only is the whole file
Calling the banner done after Accept leaves Fresh and Reject unproven. ConsentProbe runs Fresh and Reject 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 install a CMP and does not certify that Accept or Reject wiring is lawful.
FAQ
Do I still need a Reject All test if Accept All looks fine?
Yes. Accept, Reject, and Fresh are separate paths. A quiet Accept column leaves the other two untested.
Does a clean Accept prove Reject works?
No. Verify Reject on its own clean visit, with its own Network, cookie, and screenshot pack.
Do I still need Fresh if I already tested Accept and Reject?
Yes, when you claim nothing fires before a choice. Fresh is that column.
How is this different from the Reject All runbook?
The Reject leftovers guide is the failure runbook. The marketing-pixels FAQ covers pixels that keep firing. This FAQ answers whether Accept-only is enough. It does not rewrite those pages.
Does a host after Reject prove a legal violation?
No. Runtime shows what fired. Counsel decides permission. Observation is not counsel permission.
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 tells you to keep Fresh and Reject even when Accept All looks clean, and where to open the Reject leftovers guide, the EU scenario guide, and the retest guide. It does not rewrite the Reject All runbook or the marketing-pixels FAQ. It is not legal advice 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 Reject leftovers guide when Reject still tracks, the marketing-pixels FAQ for the wider pixel question, and the EU scenario guide for Fresh, Reject, and Accept side by side. The testing hub and the pre-consent checklist say which test is next. The retest guide covers the rerun after a fix.
- Reject All Still Tracking: What to Check After You Say No
- How do you audit cookies across EU fresh, reject, and accept visits?
- Pre-consent audit checklist: what to verify before Accept
- Cookie audit hub: which consent test should you run first?
- Does Reject All stop marketing pixels?
- How do you re-test after a GPC or Reject All fix?
- How to run a cookie audit before Accept
- What belongs in a cookie consent audit evidence pack?
- What does a free US-baseline cookie audit prove vs paid EU or California scans?
- Does Reject All have to be as easy as Accept?
- CMP claims vs runtime evidence: how do you prove the banner actually works?
- 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.