★ CHYP CONSENT REPLAY · FICTIONAL DEMO + YOUR OWN CAPTURES
Everyone has clicked “Reject all.” Almost nobody has watched what happens next.
Watch what a browser sent after “Reject all”, then flip to “Accept all” and see what changed. Every request has a Show evidence button.
Fictional demo · checkout page on a made-up shop (shop.example) · same actions in every run. Turn on JavaScript to play the replay; this is the summary.
| Request | No choice | Reject all | Accept all |
|---|---|---|---|
| Tag manager loader | 1 | 1 | 1 |
| Analytics event requests | 0 · not seen in this capture | 0 · not seen in this capture | 3 |
| Advertising event requests | 0 · not seen in this capture | 0 · not seen in this capture | 1 |
| First-party requests (destination unknown) | 0 | 0 | 1 |
In this fictional case rejection behaves as expected: the tag manager script loads, but no analytics or advertising event requests are seen until “Accept all”.
How to record the three captures
Use a fresh private window for each capture so earlier choices don't carry over. Open DevTools → Network, tick Preserve log, load your page, then: leave the banner alone (No choice), or click Reject all, or click Accept all. Do the same scrolls and clicks each time, wait a few seconds, then save the HAR (Chrome/Edge: Export HAR (sanitized); Firefox: Save All As HAR; Safari: Export). The Tag Investigator has the full step-by-step.
What the replay shows & its limits
Three different things are kept apart: a tag declared in the page (an ID in the HTML), a script that loaded (the tag's code was downloaded), and an event request the browser actually sent (observed in the capture). It recognizes Google Tag Manager, Google tag, GA4, Google Ads/Floodlight and Meta Pixel requests, plus first-party paths you list. Anything not in the file is labelled “not seen in this capture”. Requests to your own server are labelled “destination unknown”, because a capture can't see where a server forwards them.
Files are reduced as soon as they're opened, using the same minimiser as the Tag Investigator: cookies, headers, request and response bodies and query values (other than recognized tag IDs and standard event names) are dropped, and the raw file is let go. Nothing is uploaded, logged or stored, and the share card contains only the fields you tick.
A capture shows what one browser sent in one visit. It isn't a legal finding and doesn't show what a receiving server did. Requests close together in time are coincidence, not causation, unless the evidence shows the link.
Use captures of sites you own or are authorized to check · informational, not legal advice · independent, not affiliated with any vendor named · ← Tag Inspector · legal