Skip to main content
Troubleshooting

Investigate cookies that appear before consent

A cookie being present does not by itself tell you when it was created or what it does.

1. Start with a clean test

Use a fresh browser profile or clear data for your test website. This can sign you out of that site. Load the page without choosing anything in the banner.

2. Identify the cookie

In Chrome DevTools, open Application, then Storage > Cookies and select the relevant origin. Record the cookie name and domain. Avoid copying cookie values, which can contain identifiers.

3. Check its purpose and loading order

Compare the cookie with your scan results and the provider's documentation. Check that the Passiro script is installed before the tracker and that Auto-block scripts is configured as intended.

4. Test the service, not just the banner

Ask your developer to inspect requests before consent and after each choice. Google Consent Mode Advanced can allow cookieless Google pings before acceptance. Investigate unexpected optional tracking separately instead of treating every request as a cookie.

Placeholder[SCREENSHOT PLACEHOLDER HC-44-1: Chrome's cookie list on a dummy site; show names and domains, but hide all cookie values. Use only dummy website details, names and branding.]
Placeholder[SCREENSHOT PLACEHOLDER HC-44-2: Implementation > Behavior showing Auto-block scripts and Google Consent Mode in a demo configuration. Use only dummy website details, names and branding.]

Further help from Chrome: View, add, edit, and delete cookies