检查清单
Does Reject All stop marketing pixels?
Check whether Reject All stops marketing pixels by comparing Reject and Accept network and cookie runs. A banner screenshot does not show the script gate.
In brief
Marketing pixels in a category the visitor rejected should stop after Reject All, Decline, or Essential only. Confirm that with a Reject versus Accept comparison of cookies and third-party hosts on the same URL. A banner screenshot shows the button and leaves the network unchecked. ConsentProbe can store that labeled comparison. A free US-baseline scan is not an EU Reject conclusion. This page is testing guidance, not legal advice.
Not legal advice
This FAQ explains how to observe whether a Reject All, Decline, or Essential only control stops marketing pixels and similar non-essential third-party requests. It is not legal advice, not a compliance certificate, not a fine-amount page, and not a guarantee that any site meets GDPR, ePrivacy, CPRA, or any other rule. ConsentProbe reports are technical observations. They do not replace counsel.
Last updated September 24, 2026. The Reject All leftovers guide owns the full diagnosis. The Shopify Reject All guide owns the Shopify pass. This page answers the question and gives a short check.
Short answer
If the banner offers Reject All, Decline, or Essential only for marketing and advertising cookies, the marketing pixels in those categories should stay off after that click. An Accept run is the comparison. You only know the result for a given URL after you diff the two.
Use a clean profile, click Reject All, navigate once, and compare cookies and third-party marketing hosts with an Accept All run on the same URL. When the Reject network matches the Accept network, the control is not gating those pixels. A banner screenshot shows the button. The request list shows whether the scripts stopped. ConsentProbe can store a labeled Reject versus Accept pack tied to the request, the cookie, and the screenshot. A free US-baseline scan is not an EU Reject conclusion. ConsentProbe does not install a CMP. This page is testing guidance, not legal advice and not a fine-amount guide.
What stop means in a test
Stay with what you can see in Network and in the cookie list. Record the exact button text, because Essential only and Decline are not always the same control as Reject All. This page does not set a legal threshold for how quiet a host must be.
| After the reject control | Quieter pattern | Red flag |
|---|---|---|
| Ad or marketing pixel hosts | Absent, or limited to hosts the shop treats as essential and you can see why | The same host fan-out as the Accept run |
| Marketing cookies | Not newly set for advertising | A cookie in the _fbp class, or a similar ad cookie, still appears |
| Analytics the CMP lists as marketing | Follow the category label, then still read Network | The category says blocked while the host still loads |
Five-step check
Open the Reject All leftovers guide for the longer diagnosis. Open the Shopify Reject All guide when the shop is on Shopify.
- Use a clean browser profile. Turn off an ad blocker that would hide the request you are trying to see.
- Load the storefront and click Reject All. Write down the exact button text, including Decline or Essential only when that is the control.
- Navigate once, for example from home to a collection or a product.
- Record cookies and third-party requests, and screenshot the banner state after the click.
- Repeat with Accept All on a fresh profile, then diff the two runs for marketing hosts and marketing cookies.
Why the click and the network diverge
The button can change the banner while the tag keeps loading. The reject-as-easy page covers whether the control is as reachable as Accept. A reachable Reject button still needs its own network comparison.
- Theme or app scripts ignore the consent state the banner stored.
- Pixels are installed outside the CMP, so the CMP never gates them.
- A server Set-Cookie path writes the cookie without a browser tag the CMP can see.
- The Reject control is hard to find, which is a separate check from whether Network goes quiet after the click.
- A pre-consent load already sent the request before any click. The pre-consent checklist is that pass.
When Reject matches Accept
When marketing hosts on the Reject run match the Accept run, keep both files and hand engineering the host names. The ticket guide is the field list for that handoff.
ConsentProbe runs labeled Fresh, Reject, and Accept scenarios and ties each finding to a request, a cookie, or a screenshot. Use the free US-baseline visit for the report format. Use a paid EU scenario when the file you will show is an EU Reject comparison. The free versus paid guide states that limit. ConsentProbe does not install a CMP.
FAQ
Does Reject All stop marketing pixels?
It should for the marketing categories the visitor rejected. Verify with a Reject versus Accept diff of Network and cookies. A banner screenshot does not show the gate.
Why do pixels still load after Reject?
Theme scripts, app embeds, or tags outside the CMP can ignore the banner state. The Reject All leftovers guide is the longer diagnosis.
Is Essential only the same as Reject All?
Button labels vary. Record the exact text, then test which hosts and cookies still load.
Does a free US scan prove EU Reject All behavior?
No. A free US-baseline scan is not an EU Reject conclusion. See the free versus paid guide and the EU three-state guide.
What about Shopify stores?
Use the Shopify Reject All protocol: fresh, Reject, and Accept on a clean profile, with the Customer Privacy API treated as a consent record rather than a script blocker.
Is this legal advice or a fine guide?
No. These are technical observations. This page is not legal advice, not a compliance certificate, and not a fine-amount guide.
Limits of this page
This page explains how to observe whether Reject All, Decline, or Essential only stops marketing pixels. It is not legal advice, not a fine-amount page, and not a compliance certificate under GDPR, ePrivacy, CPRA, or any other rule. ConsentProbe reports stay tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU Reject conclusion. ConsentProbe does not install a CMP.
Related guides
Open the Reject All leftovers guide for the full diagnosis, the Shopify guide when the shop is Shopify, and the pre-consent checklist when the request already left before the click.
- Reject All Still Tracking: What to Check After You Say No
- Meta Pixel and CAPI before Accept: what to check
- Does Reject All have to be as easy as Accept?
- Pre-consent audit checklist: what to verify before Accept
- How do you test a Shopify cookie banner's Reject All button?
- How do you audit cookies across EU fresh, reject, and accept visits?
- What belongs in a cookie consent audit evidence pack?
- What does a free US-baseline cookie audit prove vs paid EU or California scans?
- What is the difference between a cookie consent audit and a cookie banner?
- How do you turn a cookie audit finding into an eng ticket?
- 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.
保存一次美国基线技术记录
完成自行检查后，可以跑一次免费美国基线审计：在加州以外做一次浏览器访问，把 Cookie、请求和截图存成证据。这次访问不会跑欧盟拒绝/接受，也不会跑加州 GPC。欧盟、加州和 Global 2 可在登录后的账单页购买。