Google Consent Mode v2 for your website

For Google Analytics, Google Ads and Tag Manager. Made in South Africa.

Google Consent Mode v2 is how your website tells Google's tags what a visitor agreed to. It asks nobody anything, so it needs a banner that does. Embedra's banner asks, starts every signal at denied, and sends the visitor's answer to Google Analytics, Google Ads and Tag Manager.

Design your banner

See it on this page →

What is Google Consent Mode v2?

Consent Mode is Google's way for a website to pass a visitor's cookie choice to Google's tags. Version 2 added two advertising signals to the original two, so there are four, and each one is either granted or denied. Consent Mode is only the messenger. It shows no banner and asks no question. The banner asks, and Consent Mode carries the answer to every Google tag on the page.

How the banner fits POPIA →

analytics_storage

Lets Google Analytics use cookies, such as the one that measures visit length. Follows the visitor's Analytics choice.

ad_storage

Lets Google's advertising tags use cookies. Follows the visitor's Marketing choice.

ad_user_data

New in v2. Allows sending data to Google for advertising, which Google Ads conversion tracking needs. Follows Marketing.

ad_personalization

New in v2. Allows personalised ads, such as remarketing. Follows Marketing.

Not sure how your site starts today? The free Consent Mode Checker loads your homepage as a first-time visitor and shows whether the four signals start as denied.

Consent Mode asks nobody anything. It needs a banner that does.

Do I need Consent Mode v2 for Google Ads?

If your ads reach people in Europe, yes. For a South African audience, Google does not demand it, but POPIA asks for the same thing: a yes before tracking.

The banner that sends it →

Visitors in Europe, the UK or Switzerland

Google asks advertisers who receive data from visitors in the European Economic Area to send Consent Mode v2. Its EU user consent policy also covers the UK and Switzerland.

Visitors in South Africa

Google's rule is written for Europe. Here POPIA applies: cookie IDs and IP addresses are personal information, and people must be told before you collect them.

Both new signals matter

Google's own reference says ad_user_data and ad_personalization must both be granted for personalised advertising. Embedra sends all four signals.

Design it like it belongs there.

Try the controls below. Adjust the padding, match your brand colors, and pick the perfect placement. What you design here is exactly what drops into your site.

Basic vs advanced consent mode

Google describes two ways to run Consent Mode. In basic, Google's tags stay blocked until the visitor chooses, and nothing reaches Google before that. In advanced, the tags load straight away with every signal denied and send cookieless pings, which Google uses to model the conversions it cannot count. Embedra does both, and you pick per tool. We recommend basic: it is the easiest to explain to a visitor, because nothing is sent before a yes.

Set it up →

G-AW-GTM-Recommended

Basic: Embedra loads it

Paste your G-, AW- or GTM- ID and remove the old tag. The banner loads Google's tag only after the visitor allows it, with Consent Mode already set from their choice.

Head codeYour own tag

Advanced: already on my site

Keep your Google tag or plugin and paste the banner's head code above it. Every signal starts denied, and the visitor's choice updates them.

Consent Mode with Google Tag Manager

Paste your GTM- container ID and the banner loads your container once the visitor allows Analytics or Marketing, with Consent Mode set from their choice before any tag runs. Or keep the container you have, put the banner's head code above it, and let the banner send the update. Either way the defaults are in place before your container starts, so there is no consent tag to build in Tag Manager.

Try the banner →

Google's tags check for themselves

Google Ads, Google Analytics and Floodlight tags have consent checks built in. They read the signals with no extra setup.

Other tags need one setting

For anything else in your container, such as an ad pixel, open the tag's consent settings, choose "Require additional consent for tag to fire" and add ad_storage.

Analytics only means analytics only

A visitor who allows only Analytics gets analytics_storage granted and the three ad signals denied, so your Google Ads tags hold back.

Running Meta ads? You need a cookie notice on every page

If the Meta Pixel is on your website, two sets of rules apply at once: Meta's own terms ask for a notice, and POPIA asks for a choice. A banner that only shows a message while the Pixel already runs gives people no choice. Ads that only run on Facebook and Instagram, with no Pixel on your site, need nothing on the website. The moment you add the Pixel to track conversions or retarget visitors, you need both a notice and a choice.

The banner and POPIA →

Meta's terms require a notice

Meta's Business Tools Terms require a clear and prominent notice on every page where the Pixel runs, linking to how third parties, including Meta, use cookies on your site and how people can opt out of ad targeting.

POPIA asks you to ask first

The ID the Pixel stores, and the IP address that comes with it, are personal information, and Meta processes them outside South Africa. The Pixel should wait for a yes.

The banner covers both

It shows on every page with a link to your privacy policy, which is the notice Meta asks for. And it holds the Pixel back until the visitor allows Marketing, then lets your conversion tracking run.

Does the Meta Pixel have a consent mode?

Not under that name: Consent Mode v2 is Google's. The Meta Pixel has its own consent switch, and the banner works it for you. TikTok and Microsoft Clarity have one too.

Every tool the banner holds back →

Meta Pixel

Revoke before the Pixel starts

Meta's own guide says to revoke consent before the Pixel's init on every page. The banner's head code does that for a Pixel your site already runs.

Meta Pixel

Grant on a yes

When the visitor allows Marketing, the banner grants consent and the Pixel sends the page view it was holding.

Meta Pixel

Or let Embedra load it

Paste your Pixel ID and remove the old code. The Pixel loads only after a yes, so before that nothing reaches Meta.

TikTok

TikTok Pixel

TikTok's pixel can hold its events until consent. The banner holds them and releases them only when the visitor allows Marketing.

Clarity

Microsoft Clarity

Until a visitor accepts, the banner tells Clarity to drop its cookies and record only anonymous page views. No Clarity settings to change.

←→

Every tool in its category

Google Ads, Meta and TikTok count as Marketing. Google Analytics and Clarity count as Analytics. Allow only Analytics, and no ad pixel runs.

How to set up Consent Mode v2 on Webflow, WordPress or Shopify

Six steps, once, the same on every platform. The banner's code goes in your site's footer, so it runs on every page.

The full guide →

Create a free account

At app.embedra.io, then add a Cookie Banner.

Keep Strict Compliance on

New banners start with Accept, Decline and Manage preferences.

The Embedra builder's Consent panel, choosing Informational or Strict Compliance and how long to remember a choice

Switch on your tools

Under Tracking tools, switch on Google Analytics, Ads or Tag Manager, and any other tool your site runs.

Choose who loads each one

Embedra loads it (paste the ID), or Already on my site.

The Embedra builder's Embed tab with the integration guide for Google Analytics and the Meta Pixel

Remove the old tag, or add the head code

If Embedra loads it, remove any other copy of the tag. If not, paste the head code from Embed, Integration guide at the very top of your head.

Paste one line of code

Into your site's footer, once, so it runs on every page.

The Embedra builder after saving a cookie banner, with the one line of code ready to copy

On Shopify, pixels added through Shopify apps follow Shopify's own consent setting, which the banner does not set yet. Let the banner load your Google tag and Pixel instead, or manage those apps in Shopify's privacy settings.

Step-by-step guides: Webflow, WordPress, Wix, Shopify, Squarespace, Framer and plain HTML.

What it does, and what it does not

Straight answers, so you know exactly what the banner covers.

✓

Denied first

Start every Google signal at denied, then send the visitor's choice.

✓

Load after a yes

Load Google, Meta, TikTok and Clarity only after a yes, or hold back the ones already on your site.

✓

Two categories

Keep Analytics and Marketing apart, so an Analytics-only yes never runs your ads.

✓

No cookies of its own

Set no cookies of its own, and send nothing to Embedra.

No site scanner

It does not scan your site for tags. It controls the tools you connect, and anything else you wrap in its browser event.

No central record

The answer stays in the visitor's browser. Google's EU user consent policy asks for consent records for visitors from Europe, the UK and Switzerland.

No reopen link yet

A visitor cannot yet reopen their choice from a Cookie settings link. That is next.

Plays nice with whatever you're using.

If your site builder lets you paste a line of custom code, Embedra works. Seamless integration with Webflow, WordPress, Shopify, Wix, Squarespace, and HTML.

Start free. Upgrade when you grow.

Every plan includes every tracking tool. The banner counts a view each time it loads, and a visitor counts once every 30 minutes.

Free

$0 forever

500 monthly views

1 widget

1 domain

Small Embedra badge

Create yours

Starter

$7/mo

15,000 monthly views

Any 3 widgets

Unlimited domains

Filter what appears

No badge

Try starter free

Pro

$16/mo

75,000 monthly views

Any 10 widgets

Unlimited domains

Custom CSS / JS

5 projects

No badge

Try pro free

Business

$34/mo

300,000 monthly views

Everything in Pro

Unlimited widgets

1/2 overage rate

15 projects

No badge

Try business free

Free

$0 forever

500 monthly views

1 widget

1 domain

Small Embedra badge

Create yours

Starter

$7/mo

15,000 monthly views

Any 3 widgets

Unlimited domains

Filter what appears

No badge

Try starter free

Pro

$16/mo

75,000 monthly views

Any 10 widgets

Unlimited domains

Custom CSS / JS

5 projects

No badge

Try pro free

Business

$34/mo

300,000 monthly views

Everything in Pro

Unlimited widgets

1/2 overage rate

15 projects

No badge

Try business free

T's & C's Apply

Questions

The ones site owners ask most about Consent Mode v2.

All questions →

Is Google Consent Mode v2 free?

Consent Mode itself is a free Google feature, but it needs a banner to drive it. Embedra's Free plan includes Consent Mode v2 and every tracking tool, for one banner and 500 views a month.

Do I need Consent Mode v2 if my visitors are in South Africa?

Google requires it for visitors in the European Economic Area. In South Africa, POPIA is the rule that applies: it asks you to tell people before you collect their information, and lets them object. Consent Mode is how your Google tags hear their answer.

Does it work with Google Tag Manager?

Yes. Paste your GTM- container ID and the banner loads it after consent, with Consent Mode v2 set from the visitor's choice. Or keep your container, add the head code above it, and let the banner send the update.

Basic or advanced consent mode: which does Embedra use?

Either, your choice per tool. Let Embedra load your Google tag and nothing reaches Google before a yes, which is basic. Keep your own tag with the head code and Google's tags load with every signal denied, which is advanced.

Does the Meta Pixel support Consent Mode?

Not Google's. The Pixel has its own consent switch, and the banner uses it: revoked until the visitor allows Marketing, then granted.

What happens when a visitor clicks Decline?

Every Google signal stays denied, and the tools Embedra loads never load. The answer is remembered, so the banner does not ask again on every page.

Send Google the right answer.

Consent Mode v2 from a banner that looks like part of your site. No plugins and no developer required.

Create a free banner