Checklist
Consent Mode cookieless ping vs real tracking after Reject All
After Reject All, a Google collect row can be a cookieless Consent Mode ping or a cookie-bearing hit. Label the row before escalating. Not legal advice.
In brief
After Reject All, a Network row to a Google collect endpoint can be a Consent Mode cookieless ping or a measurement path that still sets cookies or identifiers. Label the visit Reject. Record the URL, consent-state parameters such as gcs when present, whether _ga appears, and the time relative to the click. A ping with no storage cookies is a different finding from Reject leaving marketing cookies set. This page is observational and not legal advice.
Not legal advice
This page explains how to observe a Google Consent Mode cookieless ping versus a fuller measurement request after Reject All, or on a Fresh visit when the default state is denied. It is not legal advice, not a Consent Mode setup tutorial, not a GA4 install guide, and not a ruling that any ping is allowed. ConsentProbe reports are technical observations of cookies, storage, and Network on a labeled visit. Observation is not counsel permission.
Last updated October 1, 2026. Consent Mode versus runtime cookie evidence covers signals versus cookies. GA4 cookies before Accept covers identifiers before a choice. Reject All still tracking covers a Reject that left marketing cookies set. The evidence pack covers the handoff. This page only labels a Network row after Reject.
Short answer
After Reject All, a Network row to a Google collect endpoint can be an expected Consent Mode cookieless ping, a consent-state signal without storage cookies, or a measurement path that still sets identifiers or cookies. Label the visit Reject. Capture the request URL and query parameters, including consent-state fields such as gcs when they are present. Also record whether _ga or related cookies appear, and the time relative to the Reject click. A cookieless ping alone is a different finding from Reject leaving marketing cookies set.
Open Consent Mode versus runtime cookie evidence for signals versus cookies, GA4 cookies before Accept for cookies before a choice, Reject All still tracking when Reject left marketing cookies set, and the evidence pack for the handoff. A free US-baseline scan is not an EU or California legal conclusion. ConsentProbe does not install a CMP.
What the row often means
Use the table as a label for the row you can see. Write the finding as the report has no Reject label, or _ga was written after the Reject click. A gcs value, when the query string includes one, is a consent-state field to record. This page does not turn that field into a legal ruling.
| What you see after Reject | Often means | Still check |
|---|---|---|
| g/collect or an Ads ping with denied-state parameters, and no _ga written | Possible Consent Mode cookieless ping | Payload, client id, and storage |
| The same host, with _ga or other analytics cookies set | A stronger check on whether Reject held | Reject leftovers guide and GA4 before Accept |
| A marketing pixel host with an event payload | A marketing path after Reject | Marketing pixels FAQ and the Meta Pixel page |
Label the row in DevTools
These steps separate a cookieless ping from a cookie-bearing hit on one URL. They do not install Consent Mode or replace the before-Accept audit.
- Use a clean profile. Load the storefront once. Do not click Accept. A Fresh capture is optional.
- Click Reject All. Label the visit Reject. Note the timestamp.
- In DevTools Network, filter collect, google-analytics, googleadservices, and the tag hosts this store actually uses.
- For each row, record the URL, any consent-state parameters that are present, cookies sent on the request, and whether Application under Cookies gained _ga or a sibling.
- Write one finding sentence per row class. One class is collect with denied-state parameters and no new _ga. The other is the same host after _ga was set.
- Hand engineering the evidence-pack surfaces. When Reject left marketing cookies set, use the Reject All still tracking guide.
When the Network tab is hard to sort by hand
Sorting collect rows across templates by hand takes a long time. Run Fresh and Reject on the storefront URL in ConsentProbe. Use the free US-baseline visit for the report format, and paid EU or California scenarios when those regions are the claims. ConsentProbe does not install a CMP. A free US-baseline scan is not an EU or California legal conclusion.
FAQ
Consent Mode cookieless ping vs real tracking after Reject All
A cookieless ping carries a denied consent state and does not write storage cookies. A real measurement path still sets cookies, durable identifiers, or a fuller event payload. Label the visit Reject, then record the URL, parameters, cookies, and timing.
Is a Google collect request after Reject always a failure?
A collect request after Reject is not always a failure. It can be a Consent Mode cookieless ping. Check cookies and identifiers before you file the row as a Reject failure.
What is a cookieless ping?
Google's consent mode documentation says that when consent is denied, tags can send pings without storing cookies. When consent is granted, tags can use cookies for fuller measurement. Record the request and the cookie jar on this URL. That documentation is a vendor description, not a result for the store.
How does this page differ from Consent Mode versus runtime cookie evidence?
The Consent Mode versus runtime page treats Consent Mode signals as separate from cookie proof. This page labels a Network row after Reject as a cookieless ping or a cookie-bearing event.
Does this prove compliance?
No. The rows are technical observations. Observation is not counsel permission.
Is this legal advice?
No. It is not legal advice. Observation is not counsel permission. ConsentProbe does not replace counsel, and it does not install a CMP.
Limits of this page
This page labels a Network row after Reject as a possible cookieless ping or a cookie-bearing event. It is not legal advice, not a Consent Mode install guide, and not a second write-up of Reject All still tracking or GA4 before Accept. 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 Consent Mode versus runtime cookie evidence, GA4 cookies before Accept, Reject All still tracking, the evidence pack, and the marketing-pixels FAQ. Server-side GTM before Accept stays on its own page. The product landing is the cookie audit page.
- Consent Mode v2 vs runtime cookie evidence
- Do GA4 cookies fire before Accept?
- Reject All still tracking
- Cookie consent evidence pack
- Does Reject All stop marketing pixels?
- Meta Pixel and CAPI before Accept
- Do Server-Side GTM tags fire before Accept?
- Free US-baseline vs paid EU and California
- Cookie audit product: what ConsentProbe records before Accept
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.