FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 3 of 6

Consent done right

Basic or advanced, the four types, the order of scripts and how to test it.

6 min readUpdated 2026-11-16
All chaptersChapter 3 of 6
  1. 01What to track and why
  2. 02Google Tag Manager and GA4 setup
  3. 03Consent done right
  4. 04Events that matter
  5. 05Clarity, Search Console and Bing
  6. 06Checking it works and a monthly report

The short answer

A cookie banner only matters if your tags actually follow it. The working setup is: set consent defaults before any tag runs, usually denied where consent is needed, then send an update the moment a visitor accepts, and save that choice so it carries to the next page. With Google tags, this is Google consent mode. Other tools, such as Clarity or ad pixels, need their own consent handling.

This chapter is general, technical information, not legal advice. What you need depends on where your business and your visitors are, and what your tags do. Ask a qualified adviser what applies to your site. For the Webflow side of banners and apps, read Cookie consent on Webflow.

Basic or advanced consent mode

Google's consent mode overview describes two ways to run it:

BasicAdvanced
When Google tags loadOnly after the visitor responds to the bannerAs soon as the page opens
Before a choiceNothing is sent to GoogleTags send measurements without cookies, with consent denied by default
After consent is deniedNo data is sentCookieless measurements continue
After consent is grantedFull measurementFull measurement, with cookies
ModelingA general modelA more detailed, advertiser-specific model

Google's own guide says to choose based on your company's guidelines. Basic is simpler to explain, because nothing reaches Google until a visitor says yes. Advanced gives Google more to model from. Which one is right for you is a question for your adviser, not your developer.

On our own site, Tag Manager loads only after a visitor clicks Accept, and the banner shows only on our live domains. That is a basic-style setup, chosen on purpose.

The four consent types

Google's consent mode guide uses these types for Google tags. Consent mode v2 is the version that added the last two.

TypeWhat it controls
analytics_storageCookies and storage for analytics, such as GA4
ad_storageCookies and storage for advertising
ad_user_dataSending user data related to advertising to Google
ad_personalizationPersonalised advertising

If you do not run Google ads, you still set all four. Denied ad types simply keep ad features off. If you add ads later, the defaults are already in place.

Get the order right

Google's guide is blunt about order: set the default before any command that sends measurement data, and if your consent code runs out of order, the defaults do not work. In practice, the sequence on every page load looks like this:

  1. Default. Set the default state, for example all four types denied. You can add a wait_for_update value in milliseconds, which gives your consent tool time to send an update before tags fire. Google's example uses 500.
  2. Restore. If the visitor already chose on an earlier page, send that choice straight away. Google notes that consent mode does not save choices, so your banner has to store it, for example in a first-party cookie or local storage.
  3. Update. When the visitor clicks Accept, Reject or saves settings, send an update for the types they chose. Send one again if they change their mind later.

Defaults can also be set per region with a region list of country or state codes. A default without a region applies to everyone else, and the more specific region wins. This is how some sites show a strict default to visitors in one region and a different one elsewhere. Your adviser decides the regions. Your developer only sets them.

Consent inside Tag Manager

If you run tags through Tag Manager, use its own consent tools rather than pasting gtag code.

  • Consent Initialization trigger. Google's Tag Manager consent help says every web container has a Consent Initialization - All Pages trigger that fires before all other triggers. Put your consent tool's tag, or the tag that sets defaults, on it.
  • Use a template. Most consent tools have a template in the Community Template Gallery that sets defaults and sends updates for you. Google's guide says not to call gtag('consent','update', ...) inside Tag Manager. A custom template uses setDefaultConsentState and updateConsentState instead.
  • Consent overview. Turn it on under Admin, Container settings, Enable consent overview. It splits tags into Consent Configured and Consent Not Configured, so you can see what you missed.
  • Additional consent checks. Google tags have built-in consent checks. For any other tag, such as an ad pixel or a heatmap tool, set "Require additional consent for tag to fire" and pick the types it needs. That tag then fires only when all of them are granted.

Decision rule Every tag in the container should show as Consent Configured. If one shows as Not Configured, it is either a Google tag you have not reviewed, or a third-party tag that runs whatever the visitor chose.

The banner itself

The banner is the part people see, so it is where most opinions land. Keep it plain and fair.

  • Say in one or two sentences what you use cookies for.
  • Offer Accept and Reject as clear choices. We give them equal weight.
  • Add a settings option if you use more than one category, such as analytics and ads.
  • Link to your privacy or cookie policy.
  • Add a Cookie settings link in the footer, so people can change their mind.
  • Keep the choice for a set period and say what it is. Ours is kept for 12 months.
  • Make it work with a keyboard and on a phone, and do not let it push the page around.

Your privacy policy should match the setup: which tools you use, what they do, how long the choice lasts and how to change it. When you add a tool, update the policy in the same change.

Test what really happens

Do not judge consent by how the banner looks. Open a private window, open your browser's developer tools, and watch the Network tab and the cookies list.

StepWhat you should see
Load a page, choose nothingNo analytics or ad cookies. In basic mode, no requests to Google at all.
Reject, then browse three pagesStill no analytics cookies. Requests follow the mode you chose.
AcceptGA4 loads or switches to full measurement. A page view appears in Realtime.
Reload and browseThe choice is remembered, and the banner does not come back.
Open Cookie settings and withdrawTags stop, and new requests follow the denied state.

Tag Assistant, which opens with Tag Manager preview, shows the consent state for Google tags at each step, which makes the default and the update easy to see. Repeat this test whenever someone adds a tag. Most consent problems arrive months after launch, when a new script goes in without anyone checking.

Expect your GA4 numbers to drop once consent is enforced. Traffic did not fall. You are now seeing the part of it that agreed to be measured. Note the date in your reports.

Takeaways

What to remember from chapter 3.

  • Set defaults before any tag runs, then update on the visitor's choice.
  • Consent mode does not save the choice. Your banner has to.
  • In Tag Manager, use the Consent Initialization trigger and a template, and check the consent overview.
  • Non-Google tags need their own consent checks. This is not legal advice: ask an adviser.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.