By John Cookie · Published 4 October 2026
Seeing a Google Analytics request after clicking Reject raises a useful question, but the request alone does not explain what happened. This guide helps you collect the evidence needed to investigate.
Download the worksheet
A blank, editable text template for recording your test conditions, evidence, findings and retest actions. Open it in your text editor or paste it into your project notes. No sign-up required.
Download ga4 rejection troubleshooting worksheet (TXT)Version 4 October 2026. Blank fields are not a pass; record what was tested and what remains unknown.
Separate three observations
A cookie already present, a new cookie written after rejection and a network request sent without a cookie are different facts. Keep them in separate columns. Google explains that advanced Consent Mode can send cookieless pings while storage consent is denied; basic mode blocks Google tags until consent. A request therefore needs context. See Google’s Consent Mode overview.
Technical behaviour does not by itself settle the legal basis for processing. A “denied” label is also not a blanket approval of everything sent. Describe the observation first and ask your privacy adviser to assess purposes, information and any applicable requirements.
Create a clean baseline
- Record the URL, browser, date, region and banner version. Use a fresh profile or clear the site’s stored choice for an independent run.
- Open Developer Tools before loading the page. Inspect cookies and other storage under Application, and requests under Network. Enable Preserve log if navigation would otherwise hide the sequence.
- Without interacting, note existing cookies, their domain and expiry, the first relevant request and the consent state. Keep a timestamped record.
- Click Reject. Compare what changes immediately, after a page view and after the agreed test event.
- Repeat acceptance in a separate clean run. Test withdrawal after acceptance as a third journey, not as a substitute for the clean rejection test.
Use this investigation matrix
| Observation | Next check |
|---|---|
| A GA cookie exists after Reject | Was it already present? Compare its value and expiry before and after the choice. |
| A new GA cookie appears in a clean rejected run | Inspect the consent state at the moment of the write and trace all Google tag installations. |
| A request occurs with denied storage | Check whether this is the intended advanced-mode behaviour and inspect the actual payload. |
| The banner changes but consent values do not | Check the CMP integration and category-to-signal mapping. |
| Behaviour differs between pages | Compare templates, plugins, hard-coded tags and GTM containers. |
| Only an analytics dashboard shows activity | Run a browser test. Dashboard totals are not evidence for one visitor’s consent journey. |
Trace the source before changing settings
Write an installation map: theme, analytics plugin, CMP, GTM and any directly embedded Google tag. Ask the website team which installation is intended to own GA4. A duplicate installation is a hypothesis until the request initiator or configuration confirms it. Disabling random plugins can hide the symptom without resolving the underlying connection.
Use the Tag Assistant testing walkthrough to compare the consent events. Do not rely on manually decoding a single request parameter: Google’s fields can evolve. Keep the raw observation and the tool’s interpretation together.
Retest the actual fix
Repeat the same URL, browser setup and sequence after the change. Include a second page and the conversion journey, and note the deployed version. A successful preview is not evidence that the live published container works. State what remains untested, including server-side forwarding where configuration access was unavailable.
Read the broader Google Analytics consent guide or request a scoped Consent Mode audit. Our sample report shows how to turn this evidence into an actionable developer finding.
Practical website guidance. Tests are limited to the conditions recorded; this is not legal advice or formal compliance certification.