Checklist
Does GPC replace Reject All?
GPC and Reject All are different storefront tests. Run Fresh versus Reject, and GPC-on versus GPC-off. Not a second GPC definition.
In brief
GPC does not replace Reject All as a storefront test. GPC is a browser signal, often Sec-GPC: 1. Reject All is a banner click. A clean GPC-on visit does not prove Reject stopped marketing hosts. A clean Reject visit does not prove the storefront honors GPC. Keep separate labeled packs. A free US-baseline scan is not a California GPC conclusion. This FAQ is not a second GPC definition, not a second hub, and not legal advice.
Not legal advice
This FAQ explains how to observe whether a Global Privacy Control signal and a Reject All click are the same runtime test. It is not legal advice, not a second GPC definition, not counsel on whether any business must honor GPC or Reject All, and not a GDPR, ePrivacy, CPRA, or other compliance certificate. ConsentProbe reports are technical observations of what fired under labeled visits. They do not say what counsel would allow. Observation is not counsel permission.
Last updated September 29, 2026. The GPC signal page owns the definition. The GPC-versus-CMP page owns the mismatch framing. The signal-present page owns the protocol when marketing still loads. The prove-honored page owns the checklist. The Reject leftovers guide owns a Reject failure. This FAQ only compares the two tests. It does not open a second hub.
Short answer
GPC does not replace Reject All as a storefront test. GPC is a browser signal, often Sec-GPC: 1. Reject All is a banner preference click. They can both matter on the same URL, and each needs its own labeled evidence.
A clean GPC-on visit that looks quieter than GPC-off does not prove Reject All stopped marketing hosts. A clean Reject visit does not prove the storefront honors GPC. Treat CMP copy such as GPC detected or preferences saved as a claim. Falsify Reject with Fresh versus Reject. Falsify GPC with GPC-on versus GPC-off after you confirm the signal. This FAQ is observational only. It is not a second GPC definition, not a second hub, and not legal advice. Observation is not counsel permission.
Two controls, two packs
The table names the control, the label, and the page that already owns the longer method. Prefer a sentence such as GPC-on still shows host X, or Reject still shows host Y. Leave the legal reading with counsel. The definition stays on the GPC signal page. The Reject runbook stays on the leftovers guide.
| Control | What the browser or UI does | What you label | Where the longer method lives |
|---|---|---|---|
| Reject All | The user clicks banner reject or reject optional purposes | Reject, compared with Fresh | Reject leftovers guide and the reject-as-easy page |
| GPC | The browser sends Sec-GPC and related signals | GPC-on, compared with GPC-off | GPC signal page, signal-present page, and prove-honored checklist |
| CMP GPC detected or saved | A UI claim | Screenshot claim until Network matches | GPC versus CMP claims, and CMP claims versus runtime |
Which test when
Use the control the storefront actually claims. One clean path does not retire the other. If you only tested Accept, open the page that asks whether Accept is enough. If the signal is present and marketing still loads, open the signal-present page.
- If the banner offers Reject All, run Fresh and Reject even when GPC-on looked clean.
- If the storefront or CMP claims GPC honor, or you sell or share to California users and you are testing GPC, run GPC-on versus GPC-off even when Reject looked clean.
- When both claims are present, keep four labeled packs when you can: Fresh, Reject, GPC-off, and GPC-on.
- Write one finding sentence per unexpected match, such as the same ad host on Reject as on Fresh, or the same ad host on GPC-on as on GPC-off.
- Hand engineering an evidence pack when the rows need an owner. The evidence-pack page and the prove-honored page say what to attach.
- If the only completed visit was Accept, run Reject before you treat the banner as checked.
When four labeled visits get slow
Running four labeled visits by hand takes a long time. ConsentProbe runs Fresh and Reject on the storefront URL, and the California path compares GPC-off with GPC-on when that claim matters. 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, including GPC, when those regions are the claims. The free versus paid guide draws that line. A free US-baseline scan is not a California GPC conclusion. ConsentProbe does not configure GPC honor logic or banner Reject wiring, does not install a CMP, and does not issue a certificate.
FAQ
Does GPC replace Reject All?
No, as a storefront test. GPC is a browser signal. Reject All is a banner click. Each one needs its own labeled evidence.
If GPC-on looks clean, can I skip Reject All?
Not when the banner offers Reject and you need to falsify that path. The Reject leftovers guide is the network check.
If Reject All looks clean, can I skip GPC?
Not when you claim or need to observe GPC honor. Confirm the signal, then compare GPC-on with GPC-off. The signal page, the signal-present page, and the prove-honored checklist own that method.
Is this a new GPC definition?
No. The definition stays on the GPC signal page. This FAQ only compares GPC testing with Reject All testing.
Is GPC legally the same as Reject All?
This page does not answer legal equivalence. It is an observational test only. It is not legal advice. Observation is not counsel permission.
Where do I start?
Open the testing hub for which test is next, the Reject leftovers guide when Reject fails, and the signal-present page when Sec-GPC is on and marketing still loads.
Limits of this page
This FAQ says GPC and Reject All are different controls and different labeled packs. It is not legal advice, not a second GPC definition, and not a second cookie-audit hub. Observation is not counsel permission. ConsentProbe does not install a CMP. A free US-baseline scan is not an EU or California legal conclusion.
Related guides
Open the Reject leftovers guide for a failed Reject, the GPC signal page for the definition, the claims page for a CMP mismatch, the signal-present page when marketing still loads, and the prove-honored checklist when you hand the pack to engineering.
- Reject All still tracking
- GPC signal test
- GPC vs CMP claims
- GPC signal present but marketing still loads
- Prove GPC was honored
- Is Reject All as easy to use as Accept?
- Do I need a Reject All test if Accept works?
- Cookie consent evidence pack
- Free US-baseline vs paid EU and California
- Cookie audit hub
- Test GPC in Chrome, Firefox, and Brave
- CMP claims vs runtime evidence
- 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.