Analytics and Tracking

Default Consent State

Also called consent default, consent update

The permissions tags start with before a visitor answers the cookie banner; for UK visitors, analytics and advertising should default to denied.

Quick facts: Default Consent State

Category
Analytics and Tracking
Also called
consent default, consent update
Level
Advanced
Affects
UK GDPR and PECR compliance, GA4 data, Google Ads conversions, remarketing audiences
Where to see it
Google Tag Manager (Consent Initialization trigger), Tag Assistant, your consent management platform, browser developer tools
In this article4
  1. How the default consent state works
  2. Why it matters
  3. Common mistakes
  4. How to act on it

The default consent state is the set of permissions a website’s tags start with before a visitor has answered the cookie banner. In Google’s consent mode it is a short instruction, run before any other tag loads, that marks each type of storage as granted or denied until the visitor makes a choice.

Google’s consent mode uses named consent types. analytics_storage covers analytics cookies and ad_storage covers advertising cookies. Two newer types, ad_user_data and ad_personalization, cover two separate permissions: passing a visitor’s data to Google for advertising at all, and using it to tailor the ads that person sees later, as remarketing does. Other types cover functional, personalisation and security storage, which are usually granted because they relate to cookies the site needs in order to work.

The default command sets each type before the Google tag, GA4 or any ad tag runs. When the visitor clicks Accept, Reject or saves their preferences, your consent management platform sends an update command with the new values, and the tags change their behaviour from that point. On later pages the platform reads the stored choice and sends the update again straight after the default.

Two settings fine-tune this. A region list applies a default only to visitors in certain countries, using ISO codes such as GB for the United Kingdom. A wait_for_update value, in milliseconds, asks tags to hold briefly so a slow banner can send its update before anything fires.

What tags do while consent is denied depends on how they are set up. In basic consent mode, Google tags do not load until consent is granted. In advanced consent mode, they load and send cookieless pings, which Google uses to model the data it cannot collect.

Why it matters

In the UK, the Privacy and Electronic Communications Regulations require consent before non-essential cookies are stored on a visitor’s device, and the ICO treats advertising cookies, and analytics cookies in most set-ups, as non-essential. A default of granted means tags set those cookies as the page loads, before anyone has agreed, which is the very thing the rules forbid. For UK visitors the default should be denied for analytics_storage, ad_storage, ad_user_data and ad_personalization until the person opts in.

The Data (Use and Access) Act 2025 allows some analytics cookies to be used without consent under specific conditions, but it does not extend to advertising cookies. At the time of writing (October 2026), check the ICO’s current guidance against your own set-up before relying on that exemption, and keep advertising types denied by default whatever you decide.

Google also requires valid consent signals for UK and EEA visitors under its EU user consent policy. Without them, Google Ads cannot build remarketing lists from that traffic, and parts of its conversion measurement fall away.

Common mistakes

  • Setting the default after the Google tag has already loaded, so the first page view goes out before any consent rules apply. In Tag Manager, the default belongs on the Consent Initialization trigger.
  • Defaulting to granted and relying on the banner to switch things off later.
  • Writing the region as “UK” instead of “GB”, so the rule never matches a UK visitor.
  • A banner that saves the visitor’s choice but never sends the update command, so people who accepted are still treated as denied and no data arrives.
  • Setting analytics_storage and ad_storage but leaving out ad_user_data and ad_personalization.
  • Running two consent set-ups at once, such as a platform template and a hand-written default with different values.

How to act on it

Open your site in a private window and leave the banner alone. In Tag Assistant or Tag Manager preview, check the consent details on the first event: all four analytics and advertising types should read denied. Accept, and confirm they change to granted; then reject on a fresh visit and confirm they stay denied. Check your browser’s stored cookies too, to make sure no _ga or advertising cookies appear before you have chosen.

Decide between basic and advanced consent mode with whoever advises you on privacy, and record the reasons. Consent set-up decides how much conversion data Google Ads receives from UK visitors, so I review it at the start of any PPC management work.

Do and do not

Do

  • Default analytics and advertising consent types to denied for UK visitors
  • Fire the default before any other tag
  • Test accept and reject in a private window

Do not

  • Default to granted and rely on the banner to switch tags off
  • Write the region as UK instead of GB
  • Leave out ad_user_data and ad_personalization

Questions people ask about this

Does a default of denied mean I lose my analytics data?

You lose data from people who decline and from people who leave without choosing, which is the point of asking them. How much depends on your banner design and your audience. With advanced consent mode Google models some of the missing conversions; with basic mode, declined visits are simply not recorded, so reports describe consenting visitors only.

Can I set a different default for visitors outside the UK?

Yes. Consent mode accepts several defaults, each with its own region list, so you could deny for GB and EEA countries and set something else elsewhere. For a business that sells only in the UK, a single denied default for everyone is simpler. It also avoids mistakes when a UK visitor's location is misread, for example behind a VPN.

Does the default consent state apply to the Meta Pixel and other non-Google tags?

Not automatically, because consent mode is a Google system. In Tag Manager you can make any tag wait for consent through its consent settings, and most consent platforms block or release non-Google tags by category; the Meta Pixel also has its own consent command. Whichever method you use, non-Google marketing tags should wait for consent from UK visitors too.

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.