Skip to main content
FHAVI

Free resource

Consent Mode, and the stores that do not need it

Consent is where a store either loses a third of its measurement or breaks the law, and the two failures look identical in a dashboard. This is the checklist we run on a store with European traffic — and an honest note on when the answer is “you can skip this”.

First, whether this applies

Most stores selling only domestically can stop here

Consent requirements come from where the visitor is, not where the store is. If you sell only inside Bangladesh, or only to markets without comparable consent rules, a full Consent Mode implementation is usually unnecessary — and adding a badly-built banner costs you conversion for no benefit.

If you take traffic from the EU, the UK, or anywhere with similar consent rules, then advertising and analytics storage must wait for permission. That is not optional, and retrofitting it after an ad account restriction is much more expensive than doing it once.

The rest of this page assumes you do have EU or UK traffic. If you are unsure, the honest test is your analytics: look at where your sessions actually come from, not where you think they do.

The four signals

What Consent Mode v2 actually gates

01

Storage and use

  1. analytics_storage — whether analytics cookies may be set and read.
  2. ad_storage — whether advertising cookies may be set and read.
  3. ad_user_data — whether user data may be sent to advertising platforms for measurement.
  4. ad_personalization — whether data may be used for personalised advertising.
  5. All four default to denied until the visitor chooses; the banner then grants or keeps denial per category.
02

What that means in practice

  1. Tags still load before consent in advanced mode, but send no identifiers and no cookies until it is granted.
  2. Without ad_user_data and ad_personalization, Google's ad measurement degrades even if ad_storage is granted.
  3. Consent choices must persist, be changeable later, and be recorded — not re-asked on every page.
  4. Server-side events are not a way around consent; they inherit the same rules for the same visitor.

The checklist

Ten checks on a live implementation

03

Before launch

  1. The banner appears before any non-essential tag fires — verified in a clean browser profile, not by reading the code.
  2. Denying everything actually stops analytics and advertising cookies: check the cookie list, not the banner text.
  3. Granting everything sets them, and the choice survives a reload and a returning visit.
  4. The four signals are visible in the tag manager's consent settings and are wired to the banner categories.
  5. There is a persistent way to change the choice later — usually a footer link — for visitors who change their mind.
  6. Server-side sends check consent state for the same visitor rather than firing unconditionally.
  7. The banner does not block the page from rendering, and does not push the primary action off the screen on mobile.
  8. Reject is as easy to find as Accept, and the same size.
  9. Consent state is recorded with a timestamp for auditability.
  10. A test purchase after denial still completes — the sale must not depend on tracking consent.

What it costs you

The measurement trade, stated honestly

Implementing consent properly loses you a measurable share of analytics and advertising signal, because a portion of visitors decline or ignore the banner. That is a real cost and pretending otherwise leads to bad decisions.

What you do not lose is the sale — and what you gain is a store that can keep running ads in those markets. Model the modelling: platforms estimate for denied traffic, and the estimation is imperfect but it is not zero.

The alternative — no consent gate, full signal — works until someone complains or a platform audits you, at which point the loss is not a percentage of data but the account.

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

European traffic and no consent gate?

Tell us the markets you sell into and the platform. We will say whether this is a project you need, or a problem you do not have.

Prefer email? Write to md@fhavi.com