Analytics and Tracking

Basic Consent Mode

Also called Basic implementation of consent mode

Implementation in which Google tags do not load at all until the visitor consents, so nothing is sent beforehand.

Quick facts: Basic Consent Mode

Category
Analytics and Tracking
Also called
Basic implementation of consent mode
Level
Advanced
Affects
Reported traffic, conversion modelling, legal position
Where to see it
Google Tag Manager, Google Tag Assistant, your consent platform
In this article4
  1. How basic consent mode works
  2. Why basic consent mode matters
  3. Where basic consent mode goes wrong
  4. How to act on it

In the basic implementation, Google tags are held back completely. Until a visitor makes a choice, nothing loads: no analytics library, no advertising tag, no request of any kind to Google. If the visitor accepts, the tags load and behave exactly as they would on a site with no consent layer at all. If the visitor refuses, they never load, and that visit is silent from beginning to end.

The gating is done by the consent platform or the tag manager rather than by the tag itself, which is the key difference from the advanced implementation. There, tags load for everyone and adjust their own behaviour; here, they are simply not on the page yet.

One practical consequence is worth understanding early. Because the tag was absent for the beginning of the visit, the landing page, the referring source and anything the person did before clicking accept are usually lost. The session that gets recorded starts at the moment of consent, not at the moment of arrival.

It is the most conservative reading of the rules, and that is its appeal. Nothing leaves the browser for Google before permission is given, which is a simple position to explain to a client, a lawyer or a regulator.

The cost is measurement. People who refuse contribute nothing at all, so there is no signal from which anything can be estimated, and Google’s conversion modelling has far less to work with than it does in the advanced setup. Your reported traffic and conversions will sit below reality by whatever share of visitors declines, and you will not know that share from Google’s data alone.

The first mistake is choosing it by accident. Many sites end up in the basic pattern simply because the consent platform blocks scripts by default and nobody configured anything further. That is a legitimate choice, but it should be a decision, with the reporting consequence understood before the first report is questioned.

The second is gating Google while leaving everything else running. A chat widget, a heatmap tool or a social pixel loading before consent undoes the position you thought you had taken, and it is the sort of thing that is added months later by someone who was not in the original conversation.

The third is comparing periods across the change. Traffic will appear to fall on the day the banner goes live. Reading that as lost demand, rather than as lost visibility, leads to budget decisions based on nothing real.

How to act on it

Decide deliberately between basic and advanced, write down why, and take legal advice if the answer is not obvious for your markets. The choice is partly a legal one and partly a measurement one, and it should not be made silently by a plugin’s default setting.

Whichever you choose, stop relying on browser data for the count. Record enquiries, orders and calls in your own systems, tie them to campaign information captured at the point of submission, and reconcile the two regularly. A business that can count its own leads is not badly hurt by a conservative consent setup; a business that only knows what its tags reported is. Building that independent record is what a proper analytics and tracking setup should give you.

Do and do not

Do

  • Choose between basic and advanced deliberately, with legal advice
  • Gate non-Google scripts to the same standard
  • Annotate the date the banner went live

Do not

  • Read the traffic drop as falling demand
  • Expect strong conversion modelling in this setup
  • Let a plugin default decide your consent architecture

Questions people ask about this

Is basic consent mode safer than advanced?

It is the more cautious option, because nothing is sent to Google before a person agrees. Whether it is required depends on your markets and your legal advice, since views differ on whether an anonymous signal sent before consent is acceptable. Treat it as a decision to take with advice, not a technical default to accept.

Will I lose data with basic consent mode?

Yes, and you should plan for it. Visits from people who refuse are not recorded at all, and even for those who accept, the first moments of the visit happen before the tag loads, so the original referrer and landing page are often missing. Expect reported traffic and conversions to sit below what your own sales records show.

Can Google still model conversions in basic mode?

Modelling is much weaker here, because a refused visit sends nothing at all and there is no signal to estimate from. Google also applies volume conditions before it will model anything, which smaller accounts frequently do not meet. Plan on observed data being your practical reporting floor and reconcile against your own records.

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.