# Trackers and cookies before consent: how to make the banner actually block them

> A consent banner only counts if analytics and ad tags wait for the click. Check in a fresh browser, then wire the tags to the consent platform or Consent Mode.

Best practices · HTML version: https://getreport.app/learn/trackers-before-consent

## Cookies before consent

Passing looks like: Only necessary cookies are set before consent.

**Why it matters.** Analytics and advertising cookies (_ga, _fbp, _gcl_au, _hjid…) written before the visitor agrees are the most common finding of data-protection audits. Session, security and consent cookies are fine; tracking cookies need a yes first.

**How to fix it.**

1. Block the scripts that set these cookies until consent (your consent platform's script blocking, or GTM consent triggers), then check again in a fresh browser: the tracking cookies should appear only after "Accept".
2. If a plugin or theme sets them directly, look for its "load after consent" option or replace it.

## Trackers before consent

Passing looks like: No trackers load before consent.

**Why it matters.** Analytics, ad pixels and session-recording scripts that run before the visitor answers the cookie banner set identifiers without permission. Under GDPR and ePrivacy that needs prior consent; regulators fine for it, and the banner is worthless if the tags do not wait for it.

**How to fix it.**

1. Load tracking tags through your consent platform (Cookiebot, OneTrust, Complianz, CookieYes, Google Tag Manager with consent triggers) so they run only after "Accept". Test in a fresh incognito window: no tracker request until you click.
2. If you use Google tags, add Consent Mode v2 with the defaults set to denied; the tags then send cookieless pings until consent.

Check your own page: https://getreport.app/