Analytics and Tracking

Default Consent State

Also called Consent default, default state

The starting position, usually denied, that tells tags how to behave in the moments before a visitor answers the banner.

Quick facts: Default Consent State

Category
Analytics and Tracking
Also called
Consent default, default state
Level
Advanced
Affects
Cookie behaviour on first load, compliance, reported sessions
Where to see it
Google Tag Manager, Google Tag Assistant, browser DevTools application tab
In this article4
  1. How the default consent state works
  2. Why the default consent state matters
  3. Where the default consent state goes wrong
  4. How to act on it

Every page view begins before the visitor has decided anything. The default consent state is the instruction that covers that gap: it tells each Google tag what it may assume in the moments between the page loading and the person clicking a button on the banner.

It is declared as a small piece of code that runs ahead of everything else, setting each consent signal — advertising storage, analytics storage, advertising data and personalisation — to denied or granted. Denied for all of them is the position that matches how European and UK rules are normally read. When the visitor then makes a choice, a second instruction updates the state, and the tags adjust for the rest of the session.

Two details do the real work. The default must execute before any Google tag, because a tag that loads first has already decided how to behave. And there is a short wait built in, so a tag does not act in the split second before a consent platform has finished restoring a returning visitor’s stored answer.

It is the setting that decides whether your banner means anything. Default everything to granted and tags will read, write and send freely on first load; the choice presented afterwards changes only what happens next, and the cookie was already set. That is the single most common reason a site with a well-designed banner still fails a check.

It also shapes the numbers. A denied default means the first page view of every new visitor is measured cautiously or not at all, which is one reason landing pages and referral sources look thinner after consent goes live. Knowing this is configured as intended lets you attribute the change to consent rather than to a marketing problem.

Loading order is the usual fault. The default sits in a tag manager that itself loads late, or below the analytics snippet in the page source, and the sequence is wrong even though every individual piece is present.

Region settings are the next. Defaults can be set differently by region, which is reasonable, but it is easy to write a rule that leaves everything granted outside a listed set of countries and then forget it — including for visitors whose location the browser reports differently from what you expected.

The third is quieter: a returning visitor whose stored answer is not restored quickly enough, so tags act on the denied default and their earlier acceptance is effectively ignored. That undercounts your most engaged audience, the people who come back.

How to act on it

Test it rather than read it. In a clean browser window with the developer tools open, load a page and do nothing. No advertising or analytics cookie should appear. Then accept, and watch the state update. Then return to the site as a repeat visitor and confirm the stored answer is applied before the tags act. Google Tag Assistant shows the consent state each tag saw, which turns this from guesswork into a definite answer.

Re-run that check whenever the site, the theme or the consent platform changes, because loading order is easy to break and nothing visibly fails when it does. If tags, consent and reporting need to be set up as one coherent piece, that is what a proper Google Tag Manager setup covers.

Do and do not

Do

  • Set every signal to denied before tags load
  • Run the default ahead of any Google tag
  • Retest after theme, plugin or consent platform changes

Do not

  • Default to granted and rely on the banner afterwards
  • Forget the fallback rule for unlisted regions
  • Let stored answers load after the tags fire

Questions people ask about this

Should the default consent state be denied or granted?

Denied is the safe position wherever European or UK rules apply, because it means nothing is stored or sent until the visitor actually agrees. Setting it to granted makes the banner cosmetic: the cookies are already there by the time anyone clicks. If you vary it by region, check the rule carefully and test from each region you have covered.

How can I check my default consent state is working?

Open your site in a fresh private window with the browser developer tools showing cookies and network requests, and do not touch the banner. If an analytics or advertising cookie appears, the default is either granted or running too late. Google Tag Assistant will also show the consent state each tag observed when it fired.

Why do returning visitors sometimes lose their consent choice?

Usually because the stored answer is restored after the tags have already acted on the denied default. The consent platform needs to run and apply the saved decision before Google tags fire, and there is a short wait setting designed for exactly that. When it is misconfigured, your most loyal visitors are the ones being undercounted.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.