Every plan

Google Consent Mode v2, set up for you

Google Ads and GA4 need consent signals from your banner. allowedit sends the defaults before any tag loads and updates them the moment a visitor chooses.

What Google's tags are told on your site

  • Before any tag loads (EU visitor) ad_storage, ad_user_data, ad_personalization, analytics_storage: denied
  • Visitor allows analytics only update: analytics_storage granted
  • Visitor accepts all update: all four granted
The defaults follow your region rules, so a visitor in Texas and a visitor in Germany start differently.
Google Consent Mode v2 is how a consent banner tells Google tags what a visitor agreed to. allowedit sets every signal to denied before tags load where consent is needed, sends an update when the visitor chooses, and includes ad_user_data and ad_personalization, which Google requires for EEA ad features. It's on every plan.

How it works

Three steps, most of them done for you.

  1. 1

    Put the script first

    Add the allowedit script at the top of your head, above Google Tag Manager or gtag.js, so the defaults are in place before any Google tag runs.

  2. 2

    Pick basic or advanced

    Advanced lets Google tags load in a denied state and send cookieless pings. Basic keeps them blocked until the visitor consents. Consent Mode is on by default, in advanced mode.

  3. 3

    Check it in Tag Assistant

    Open Google Tag Assistant on your site. You should see the consent default first, then an update after you click a button in the banner.

What it handles

The parts of Consent Mode that are easy to get wrong by hand.

All four v2 signals

ad_storage, analytics_storage, ad_user_data and ad_personalization, so Google Ads audiences and conversion modelling keep working in the EEA.

Defaults by region

Denied in the EU, UK, Switzerland and Quebec. Granted where your region rules let tags run, such as US states with an opt-out.

Updates on every choice

Accept all, Reject all, a custom choice, the opt-out link and a Global Privacy Control signal each send the matching update.

Ads data redaction

With ads_data_redaction on (the default), ad click identifiers are removed from requests while ad_storage is denied.

URL passthrough

Optionally pass click information through page URLs, so conversions can still be measured when cookies are refused.

A trigger for Tag Manager

An allowedit_consent event is pushed to the dataLayer after each choice, ready to use as a custom event trigger in GTM.

Basic or advanced Consent Mode: which should I use?

Both are valid ways to implement Consent Mode. Advanced sends Google some data before consent, without cookies, so check with your own legal adviser which fits your site.

Basic and advanced Consent Mode compared
BasicAdvanced
Before consentGoogle tags don't load at allGoogle tags load with every signal denied
Data sent before consentNothingCookieless pings, no cookies set
Conversion modelling in GoogleGeneral modelling onlyModelling based on your site's own pings
Pick it ifYou want no Google requests before consentYou rely on Google Ads measurement

How do categories map to Google's signals?

  • Analytics allowed: analytics_storage granted
  • Marketing allowed: ad_storage, ad_user_data and ad_personalization granted
  • Preferences allowed: functionality_storage and personalization_storage granted
  • security_storage is always granted, because it covers what keeps the site safe

Do I need Consent Mode v2?

If you use Google Ads or GA4 and have visitors in the European Economic Area, yes. Since March 2024, Google requires ad_user_data and ad_personalization for audiences and personalised ads based on EEA users. Without them, remarketing lists and some conversion features stop growing.

Consent Mode v2 explainedGoogle Tag Manager setup

What each plan gets

Pro is $10 a month for 3 sites. Agency is $39 a month for every site you run. Cancel any time. Your banners keep working if you do.

Free

  • Consent Mode v2 with all four signals
  • Basic or advanced mode
  • ads_data_redaction and url_passthrough options
  • The allowedit_consent dataLayer event
Start free

Pro

  • The same on each of your 3 sites
  • No "Consent by allowedit" link
See Pro pricing

Agency

  • The same on every client site
  • A monthly compliance report email for each client
See Agency pricing

What it doesn't do

  • It sets consent signals; it doesn't install GA4 or Google Ads for you. Your tags still go in GTM or your site as usual.
  • If a Google tag loads above the allowedit script, it can run before the defaults are set. The script must come first.
  • Consent Mode only covers Google tags. Other vendors are handled by auto-blocking or manual blocking.
  • We don't offer IAB TCF yet, so Google's TCF-based ad serving for publishers isn't covered.

Questions

Is allowedit's Consent Mode on the free plan?

Yes. Consent Mode v2, basic and advanced, is on every plan, including the free plan for 1 site.

Does it work with Google Tag Manager?

Yes. Put the allowedit script above the GTM snippet. GTM's consent checks then see the defaults and updates, and you can use the allowedit_consent custom event as a trigger.

What does Consent Mode do in the US?

With the default region rules, visitors in US states with privacy laws start with signals granted, since tags may run until they opt out. If they use the opt-out link or send Global Privacy Control, the marketing signals are updated to denied.

Will Consent Mode keep my conversions accurate?

It helps. In advanced mode, Google uses cookieless pings to model conversions from visitors who said no. Numbers will still be lower than before consent banners, because some people refuse.

Get Consent Mode v2 right the first time

Defaults before tags, updates on every choice. Free for 1 site.

Create a free account