Attribution Lab
  • in the demo
  • GA4
  • GTM
  • sGTM
  • Google Ads

Cookie consent in Europe: what your ads lose and how to lose less

Updated 30 September 2026
Go to the demo

If you have a company, branch or office in the EU or the UK, the law applies to you directly; see the section for companies in the EU and the UK for what it requires.

What is wrong

Under EU and UK law, the site has to ask visitors from those countries whether they agree to cookies, and may not collect their data until they answer. A visitor who clicks "Reject", or clicks nothing and moves on through the site, is lost to your ads. For each of them your ads lose:

  1. Audiences. The visitor does not enter remarketing lists and does not get personalized ads. Google has enforced this since March 2024 (Consent Mode v2).
  2. Conversions. The purchase is not tied to the ad. Google's automated bidding learns from the purchases it sees, and this one never reaches it. In the reports this looks like a drop in conversions, and the reports cannot tell you whether demand fell or tracking broke.
  3. The first touch. If the visitor accepts only on the third page, the source they came from is already gone by then.
  4. The journey between domains. If you have several domains, say the site and a separate booking or payment platform, without consent the visitor's journey breaks at the hand-off, and the purchase on the second domain has no source. More in the cases "Several sites of one network" and "Booking takes visitors to an external platform".

If there is no banner, or it does not pass a consent signal to Google, Google treats every visitor from the EU, the UK and Switzerland as not consenting, including those who would have clicked "Accept". If you have a banner, your banner provider's dashboard shows what share of visits end without "Accept".

The opposite mistake is to treat everyone as consenting: setting cookies before consent, filing ad cookies under "strictly necessary", or telling Google by default that consent was given. Your reports keep their numbers, but on European traffic this breaks Google's rules for advertisers, and Google may restrict or suspend the ad account. A company in the EU or the UK can also be fined for it by its regulator.

What is mandatory

Google's requirements. Google's rules for advertisers require you to get consent from visitors from the European Economic Area (the EU plus Norway, Iceland and Liechtenstein), the UK and Switzerland, wherever the business itself is based, to keep records of consent and to tell visitors how to withdraw it. These rules apply whatever the law of your country says. Since March 2024 Google also expects a consent signal from the site (Consent Mode v2): without it, these visitors do not enter audiences and conversion tracking is limited.

The banner sets the consent signal: with it, Google tags send every event with a flag saying whether the visitor agreed to ads and analytics. Most consent management platforms (CMPs) do this out of the box (Google lists certified ones in its CMP Partner Program). You can check that the signal goes out in Google Tag Assistant: the Consent tab shows the consent state before and after the visitor clicks. If there is no banner or no signal, start there.

The law, if your company is not in Europe. On paper, the European cookie rules cover any site with visitors from there. Fines are issued by the regulators of individual countries, and enforcing one against a company with no presence in Europe is hard. Assess your own situation with a lawyer.

If your company is in the EU or the UK

The regulator of the country where your company operates can fine you for breaking the cookie consent rules. In short, the law and regulators' guidance expect you to:

  1. not set or read any cookies or other identifiers in the browser before consent, except those strictly necessary for the site to work;
  2. make refusing as easy as accepting: a "Reject" button on the first screen of the banner, next to "Accept"; the banner must not nudge the visitor or suggest the site cannot be used without consent;
  3. ask for consent separately for each purpose – analytics, ads – with a clear description and no boxes ticked in advance; banners usually do this with a "Settings" button;
  4. keep a record of when and to what the visitor consented;
  5. on request, show the visitor what is stored about them, and delete it;
  6. let the visitor withdraw consent at any time, as easily as they gave it: for example, with an icon in the corner or a link in the footer on every page.

Regulators also advise against asking again soon after a refusal: the UK regulator considers around six months reasonable.

For the data on your own server, points 4 to 6 are covered by a "Your data on this site" page. There the visitor sees their journey, the source, the consent history and the identifiers stored in their browser, and can export the record and delete it. The "Your Privacy Choices" link in the footer of every page lets them reopen their privacy choices. If they withdraw consent, the record of their visits is deleted at once, and the history of decisions stays as proof that consent was given. Banner services keep consent logs too: Cookiebot, CookieYes (CSV export), iubenda (Consent Database). Data already sent to Google, to the booking system or to a CRM has to be deleted in each of those systems separately.

In the demo: the "Your data on this site" page, reopening the privacy choices and withdrawing consent.

The exact requirements differ between countries; assess your own situation with a lawyer. Some fields, healthcare for one, have their own data requirements that this page does not cover. Sources: the report of the European regulators on cookie banners (EDPB, 2023), guidance from the UK regulator, the ICO, the GDPR (Articles 7, 15 and 17) and the ePrivacy Directive (Article 5(3)).

How to lose less

1. Get an answer from every visitor

Most data is lost from visitors who miss the banner and move on. You can dim the page and disable links and buttons until the visitor picks "Accept" or "Reject". Refusing opens the site just as accepting does. Then the decision is made on the first page, and the first touch is not lost.

"Accept all" may stand out in color, as long as "Reject all" sits next to it, reads well and takes one click. European regulators judge button colors banner by banner; what they treat as a breach is a refusal that is hidden or barely readable.

If your business is in the EU or the UK, check the current requirements for such a banner with a lawyer.

In the demo: the dimming, links that stay inactive until the visitor chooses, and a highlighted "Accept all". Open in the demo.

2. Show the banner only to visitors from Europe

Only visitors from the EU, the UK and Switzerland are asked for consent up front. Visitors from other countries are tracked from their first page and are not lost.

Downside: the country is guessed from the IP address, so it is approximate.

Where to find it: Cookiebot, CookieYes, Complianz and iubenda let you show the banner by the visitor's country.

If your business is in the EU or the UK, check with a lawyer: the rules of your country may apply to visitors from other countries too.

3. Advanced consent mode: recover part of the conversions through modeling

Before consent, Google tags load anyway and send cookieless pings – no cookie, no visitor identifier. Google uses them to model the missing conversions, and part of the losses comes back into the reports as an estimate.

Downside: the estimate appears only at large volumes. Google Ads fills in conversions once there are at least 700 ad clicks from one country over 7 days (Google Ads conditions), GA4 once there are at least 1,000 events a day without consent for at least 7 days and at least 1,000 consenting users a day on at least 7 of the previous 28 days (GA4 conditions); most small sites never reach these thresholds. The demo does not use this mode.

Where to find it: Cookiebot, CookieYes and iubenda support this mode.

If your business is in the EU or the UK, this is a decision to make with a lawyer: regulators view these pings differently, and some read the rules as banning even them before consent.

Vendor examples are based on their documentation as of September 2026. Features and plans change, so check your own vendor's documentation; some vendors offer banners by country only on paid plans.

Open the demo

The demo opens in "Consent first, as in the EU" mode with a clean slate each time, so you always see the banner. The hints walk you through it: the banner and what the law asks of it, the dimming, the links that stay inactive until you choose, your choice and what it changed, the "Consent" tab, the "Your data on this site" page, withdrawing consent and what stays after it.

Consent regime

This case opens the demo in the EU regime: it is about the consent banner.

Required here: without it the banner does not appear if you have chosen before.

Open the demoLink the demo opens withhttps://alpha.nexusnode.ru/?utm_source=GAds&utm_medium=CPC&utm_campaign=case_consent&demo_click_id=GADS-11111&al_case=consent-regimes&al_lang=en&al_transport=server&al_regime=eu&al_guide=1&al_reset=1

About the author

Anton Kozhanov

I used to be a design engineer in the power industry. In 2013 I traded that for an online store, a loan from friends and ads that sold nothing. Things improved from there, mostly. Clients' businesses grew several times over, and a few even asked me to pause the ads so they could get a break from the phone. Thirteen years in, I still enjoy this more than is probably professional.

The long version, awkward bits included →

Book a call

Bring your site, your consent banner if you have one, and the drop you cannot explain. We'll check what your setup stores and sends to Google before the visitor decides, after "Accept" and after "Reject", and decide what is worth fixing first. If you walked through the demo, I'll open your journey record on the call: what waited for the visitor's decision, what was saved, what was blocked.