Paid advertising

Cookie banners: Danish rules, consent and Consent Mode

A cookie banner is the box a website shows on the first visit, where the visitor says yes or no to cookies and similar technologies. Under Danish rules, a website may generally only use cookies for statistics and marketing once the visitor has said yes. Technically necessary cookies, e.g. for a shopping basket or a login, don't require consent. The banner also determines what your ads can measure. If the visitor says no, Google and Meta can't use cookies to link the visit to an ad click, and that affects both Facebook advertising and Google Shopping. That's why, at Amplify, the cookie banner is part of the ad setup, just like conversion tracking. Below, you can read what the authorities and Google themselves say, and how we check a banner. This isn't legal advice. If you're unsure about your own setup, read the guidance or ask a lawyer.
Hands around a table with laptops, a notepad and an Amplify badge
→ All articles

What do Danish rules require of a cookie banner?

Danish rules require freely given, specific, informed and unambiguous consent before the website uses cookies for anything other than what's technically necessary. That's what it says in the joint cookie guidance from the Danish Agency for Digital Government and the Danish Data Protection Agency, May 2025. Among other things, the guidance mentions:

  • Consent comes first. The visitor must answer before you set cookies for statistics and marketing.
  • An active choice. Pre-ticked boxes, toggles switched on in advance and acceptance of your terms don't count. Nor does it count when the visitor simply keeps using the site.
  • No must be as easy as yes. The guidance warns against pressure, e.g. a green accept button and a reject button that blends into the background.
  • Each purpose separately. The visitor must be able to say yes to statistics, for example, and no to marketing.
  • The first layer covers the essentials. Who you and your partners are, the purpose, the type of information, whether data goes to third parties, and that consent can be withdrawn.
  • Withdrawing is as easy as consenting. E.g. with a fixed icon or a link on every page.
  • Consent can be documented. What it covers, when it was given, and with which solution.
  • Danish site, Danish banner. In clear and simple language.

The banner is the first thing a new visitor meets on your site. Write it in your own tone, in plain Danish and without pressure.

The rules cover more than cookies

The Danish Data Protection Agency says the rules are technology-neutral. They also cover pixels, fingerprinting and unique IDs such as advertising IDs. The Meta pixel, Google's tags and LinkedIn's Insight Tag are therefore included when they're used for statistics or ads.

Who supervises the cookie rules?

The Danish Agency for Digital Government supervises the cookie rules, and the Danish Data Protection Agency the rules on personal data. Until 15 December 2022, supervision sat with the Danish Business Authority, so older guidance often points there. According to the Danish Agency for Digital Government, breaches of the Danish cookie order can be punished with a fine.

The responsibility lies with you. The guidance says this also applies when a partner or technical supplier handles the cookies and the banner. The Danish Data Protection Agency's page on cookies brings together the guidance and the practical advice.

What is Google Consent Mode?

Google Consent Mode is Google's way of passing the answer from the cookie banner on to Google's tags, so they behave accordingly. Consent Mode doesn't create a banner itself, says Google in its Google Ads help.

Four signals matter most for ads and measurement, according to Google's overview of Consent Mode:

  • ad_storage controls cookies for ads.
  • analytics_storage controls cookies for statistics, e.g. Google Analytics.
  • ad_user_data controls whether user data may be sent to Google for advertising.
  • ad_personalization controls personalised ads, e.g. remarketing.

The last two were added in the version many call Consent Mode v2. For visitors in the EEA, Google requires consent and the signals when data is used for measurement, personalised ads and remarketing (Google's Tag Manager help).

Basic or advanced Consent Mode

Google describes two ways to set up Consent Mode:

  • Basic. Google's tags wait for the answer. If the visitor says no, Google gets no data, not even the answer itself. Google Ads then models conversions based on a general model.
  • Advanced. The tags load with the default you've set and send cookieless measurements as long as consent is declined. Google then builds a model for your account specifically.

The joint guidance doesn't mention Consent Mode. It's technology-neutral and requires consent before you collect data for statistics and marketing. So you need to make the choice between basic and advanced deliberately. At Amplify, we normally set up advanced with everything declined by default across the EEA. We record the choice as the client's decision. If the client wants to play it safest, we run basic and give up the modelling.

Why does cookie consent affect your ad measurement?

Cookie consent affects measurement because the ad platforms use cookies to link a purchase to the click that came before it. With ad_storage declined, Google's tags neither write nor read ad cookies (Google's overview of the signals). The purchase still happens. The ad account just doesn't find out about it in the same way.

It hits in three places:

  1. Bidding. Automated bid strategies in Google and Meta learn from the conversions they see. Fewer measured purchases mean a weaker signal.
  2. Remarketing. With ad_personalization declined, Google's remarketing gets no data from the visit. Your remarketing lists get smaller.
  3. Reports. The numbers in Google Ads, Meta and Google Analytics end up lower than your actual sales.

Google can model the missing conversions when there's enough data. Google Ads requires at least 700 ad clicks over 7 days per country and domain (Google's requirements). Google Analytics requires, among other things, at least 1,000 events a day without consent for statistics for at least 7 days (Google's requirements). Our experience is that most smaller webshops don't reach that threshold. Don't count on the model filling the gap.

The mistakes behind the banner

The mistakes that cost measurement sit in the link between consent and the tags. Four we see again and again:

  • A tag that fires on a no. The pixel waits for the answer and doesn't check whether the answer was yes. So it sets its cookie anyway.
  • Two truths about consent. The webshop platform reports "everything allowed" for Danish visitors, because Denmark is missing from the list of countries with consent requirements. The platform's app pixels see a yes, while the banner has received a no.
  • An app that answers for the visitor. The app sends a yes to Google's tags before anyone has touched the banner. That leads to measurement without consent and visits without a source.
  • Consent Mode switched off in the banner's tag. Then the tag sets no default, and Google Tag Manager treats a missing answer as a yes.

You won't see any of them on the banner itself. They only show up in the requests the site sends. We do that review with AI. The AI runs the test in a clean browser, reads every request and points to the tags that send too early. The specialist decides what we fix.

How Amplify checks a cookie banner

At Amplify, we check a cookie banner in eight steps before we trust the numbers in an ad account:

  1. One banner and one source. The site has only one consent solution. The platform's own banner is switched off, and the platform's consent follows the banner.
  2. Everything declined by default. All four signals are set to declined until the visitor answers, across the EEA.
  3. The categories match the signals. Marketing controls ad_storage, ad_user_data and ad_personalization. Statistics controls analytics_storage.
  4. The tags wait for a yes. Tags outside Google, e.g. from Meta and LinkedIn, only fire after a yes to marketing.
  5. A no that holds. We say no in a clean browser and reload twice. Afterwards, there must be no cookies from Google Ads, Meta or Google Analytics.
  6. Withdrawal works. We withdraw consent and check that the platform and the tags follow suit.
  7. The server follows the same answer. If you use server-side tracking, the server only sends what consent allows.
  8. It's written down. Screenshots of every version of the banner and the choice of Consent Mode, with dates.

No setup measures every purchase. A no has to hold, and that costs data. We'd rather deliver a number that's true than one that looks good.

Frequently asked questions about cookie banners

Does every website need a cookie banner?

No. You need to ask for consent when the site uses cookies or similar for things like visitor statistics or personalised ads. Cookies for a login, a shopping basket or a language choice the visitor has made themselves don't require consent. So if the site uses Google Analytics or ad pixels, you need to ask first.

What happens to Google Analytics when the visitor says no?

It depends on your Consent Mode. With basic, Google Analytics sends nothing. With advanced, the tag sends cookieless measurements, and Google Analytics can model behaviour on sites with enough traffic. Without modelling, you see fewer visits and purchases than there actually were.

How often does cookie consent need renewing?

There's no fixed limit on how long consent lasts. The joint guidance says it will often be appropriate to renew consent once a year. The same applies to asking a visitor who has said no. If you change the purpose, you need to ask for new consent before you start.

Is server-side tracking a way around cookie consent?

No. The Danish Data Protection Agency says the rules are technology-neutral and also cover pixels and unique IDs. Server-side tracking does, however, capture more of the purchases where the visitor has said yes.

Your next step

Open your own site in a new private window and say no in the banner. Reload the page and open the browser's developer tools. Check under cookies whether there's anything from Google Ads, Meta or Google Analytics. If there is, the site is sending data it isn't allowed to. Also save a dated screenshot of the banner. That's the start of the documentation the guidance asks for. If you find something that shouldn't be there, get in touch with us before you change the tags.

Want help with this?

→ Book a chat