Home › Blog · Privacy · 29 October 2026 · 6 min read

Consent mode and conversion tracking, explained

How consent works for ad tracking in the EEA, UK and Switzerland, what Google Consent Mode and IAB TCF do, and what may be sent before and after.

In the EEA, the UK and Switzerland, a site is generally expected to ask visitors before it uses advertising cookies or sends their data to ad platforms, and consent mode is the mechanism that tells your tags what each visitor chose. Respecting that choice and measuring your advertising are compatible, because the events you are allowed to send are enough to run campaigns well.

This article describes the rules in general terms. It is not legal advice. Requirements differ between countries and change over time, so check your own obligations.

Where consent is expected

In the European Economic Area, which is the European Union plus Iceland, Liechtenstein and Norway, two sets of rules matter for tracking. The ePrivacy rules cover storing or reading information on a visitor's device, which includes cookies. Anything that is not strictly necessary for the service the visitor asked for needs consent first. The General Data Protection Regulation, or GDPR, covers how personal data is used after that.

The United Kingdom has its own versions of both. Switzerland has its own data protection law, with its own details. Many sites treat the three regions the same way, which is the simplest way to stay careful.

Advertising tags are not strictly necessary for showing someone a product page. In these regions they should wait for a yes.

How consent is collected

A consent banner asks the visitor what they accept. The tool behind the banner is called a consent management platform, or CMP. It records the choice, usually by category such as analytics and advertising, and makes it available to the tags on the page.

The banner is half of the job. The other half is making every tag obey the answer. Two standards exist for passing the answer along: Google Consent Mode and the IAB Transparency and Consent Framework.

Google Consent Mode

Consent Mode is Google's way of telling its tags what the visitor allowed. It uses four main signals. Each one is either granted or denied.

SignalWhat it controls
ad_storageCookies and other storage used for advertising
analytics_storageCookies and other storage used for analytics
ad_user_dataSending the visitor's data to Google for advertising
ad_personalizationUsing the data for personalized advertising, such as remarketing

The site sets a default before anything else runs. In regions with consent rules, the default is denied:

gtag('consent', 'default', {
  ad_storage: 'denied',
  analytics_storage: 'denied',
  ad_user_data: 'denied',
  ad_personalization: 'denied'
});

When the visitor makes a choice, the banner sends an update:

gtag('consent', 'update', {
  ad_storage: 'granted',
  analytics_storage: 'granted',
  ad_user_data: 'granted',
  ad_personalization: 'granted'
});

There are two ways to run it. In the basic setup, Google's tags do not load at all until the visitor accepts. In the advanced setup, the tags load straight away and, while consent is denied, send limited signals without cookies, which Google uses to estimate the conversions it could not observe. Whether the advanced setup suits your site is a decision to take with whoever advises you on privacy.

Other tools can read these signals as well. A tag for another platform can look at the same consent state and hold back until it changes.

The IAB Transparency and Consent Framework

The Transparency and Consent Framework, or TCF, is a standard from the advertising industry body IAB Europe. A CMP that follows it records the visitor's choices in a compact text called the TC string. The string lists which purposes the visitor accepted, such as storing information on a device or measuring ad performance, and which vendors may act on them.

Tags read the string through a function the CMP places on the page, named __tcfapi. A tag that supports TCF asks that function whether it has permission and waits for the answer.

You do not need both standards for them to be useful. What matters is that your banner publishes the choice in a form your tags understand, and that every tag on the site listens.

What may be sent before and after consent

MomentWhat a careful setup does
Before a choiceNo advertising cookies are written or read. No events with identifiers go to ad platforms. Only what is strictly necessary to run the site is used.
After acceptanceTags load and fire. Cookies are set. Events carry click IDs and, where the visitor agreed to it, hashed contact details.
After refusalAdvertising tags stay silent for that visitor. The site works normally.
After a change of mindThe visitor can withdraw consent as easily as they gave it, and tags stop from that point.

Two points are often misunderstood.

Server-side tracking does not change the answer. Sending an event from a server is a different route for the same data. If the visitor refused, the server should not send it either. See what server-side tracking is for what it does and does not fix.

Hashing does not change the answer. A hashed e-mail address is still generally treated as personal data. It needs the same permission as the readable address.

Why respecting consent and measuring are compatible

It can feel as though each refusal is a hole in your data. In practice, a consent-respecting setup still gives you what you need.

  • Consented events are complete events. A visitor who accepts can be tracked with full detail: click ID, cookies and matched contact details. Platforms optimize well on a smaller set of high-quality events.
  • Platforms estimate the rest. Ad platforms use statistical modeling to account for conversions they could not observe. Clean consent signals make those estimates better.
  • Your totals never depended on tracking. Your shop knows how many orders it had and how much revenue it took, with or without consent. Measures built on those totals, such as blended ROAS, stay accurate.
  • A clear banner earns more acceptances. People are more willing to agree when the request is plain, the options are equal, and refusing takes one click. A banner that hides the refuse button erodes trust and may break the rules it exists to follow.
  • The risk goes away. A setup that fires tags before consent can expose you to complaints and fines. One that waits does not.

How to check your own site

  1. Open your site in a private window, as a visitor in a consent region would see it.
  2. Before touching the banner, open the browser's developer tools and look at the network tab. No requests should go to ad platforms.
  3. Refuse. Browse a few pages. Still no requests to ad platforms.
  4. Start again and accept. The tags should now fire, and a test purchase should arrive in each platform's events tool.
  5. Withdraw consent from the banner's settings link and confirm the tags stop.

Where Tagbreeze fits

Tagbreeze waits for consent in the EEA, the UK and Switzerland before it sends anything, from the browser or from its servers. It reads Google Consent Mode and the IAB TCF, so it follows the banner you already have. If you have none, it includes a simple built-in banner.

In short

  • In the EEA, the UK and Switzerland, advertising tags should wait for the visitor's agreement. Check the details that apply to you.
  • Google Consent Mode passes the choice through four signals. The IAB TCF passes it through the TC string.
  • Before consent and after refusal, ad tags stay silent, including on the server.
  • Consented events, platform modeling and your shop's own totals are enough to measure and optimize.

If you want tags that wait for consent by default, add your site.

Know what your ads really bring in.

It takes a few minutes. Nothing is changed on your site until you install the tag.

Add your site
Hands on a laptop beside parcels ready to ship