Collect
Consent Mode and Global Privacy Control
Before Accept, analytics storage is denied and a Google ping is cookieless. After Accept, the same tag can send a full analytics hit. A Global Privacy Control signal keeps the denied state.
Before Accept
Cookieless ping
The tag loads with analytics_storage: denied and ad_storage: denied. This site does not push page_view until Accept. Google may still send a ping with gcs=G100: no analytics cookie, no ad cookie. The first-party beacon is also refused.
After Accept
Full analytics hit
Accept sets analytics storage to granted. Advertising storage stays denied, so the hit is gcs=G110, not G111. gtag.js may then write _ga. The first-party /api/collect beacon is stored.
This visit
- analytics_storage
- denied
- Expected gcs
- G100
- navigator.globalPrivacyControl
- false
- Sec-GPC on this request
- …
Use the Consent switch in the header, then send the sample. The log below is Resource Timing for Google and for /api/collect. It does not record form fields.
Request log
No Google or collect requests yet. Send the sample after Accept, or reload with consent already on.
Recommended next
Why these picksReading path transitions…