Skip to content
Use cases

GDPR-compliant tracking with Consent Mode v2

Choose per project what happens before consent, let TSO read the decision from your cookie banner, and decide per platform which data goes out.

The problem

Without consent, data is missing; set up wrong, you risk legal trouble. On top comes Google Consent Mode v2, and every pixel reads the banner differently. In the end nobody knows exactly what is sent before consent.

How to do it

  1. Choose a modeChoose one of three modes per project, together with your privacy adviser. The mode decides what is stored and sent before consent.
  2. Connect the bannerGoogle Consent Mode v2, Cookiebot, OneTrust, Usercentrics, Borlabs and Complianz are detected automatically. Other banners pass the decision to the script with one command.
  3. Load pixels through TSOWhen the TSO script loads the pixels, they only start with consent, and a withdrawal is passed on to every pixel.
  4. Set fields per platformPer destination, hold back what shouldn't be sent, such as IP address and user agent, and send events only with consent.
  5. CheckThe delivery log shows what was sent with which fields. Meta, Google Ads, TikTok, Snapchat and ChatGPT Ads can be checked in test mode first.
Privacy
  • Without consent
    You are responsible for the legal basis.
  • Cookieless until consent
    Count anonymously without a cookie, recognize visitors once they consent.
  • Only with consent
    Nothing is sent until the visitor consents.
Cookie banner
Google Consent ModeCookiebotOneTrustUsercentrics · detectedBorlabsComplianz
Send to Meta
  • Email, phone hashed
  • Revenue
  • IP address, user agent
ModeBefore consentAfter consent
Without consentEvery visitor is recognised; you're responsible for the legal basisunchanged
Cookieless until consentVisits are counted anonymously with a daily ID on the server; nothing is stored in the browserThe visitor is recognised, and the visit before is kept
Consent onlyThe script sends and stores nothing; events wait in the page's memoryThe waiting events are sent

When TSO reports a conversion to Google Ads, consent goes along: granted if all visits that click, page and IP come from consented, denied otherwise. Google gets the consent signal it expects for Consent Mode v2, even for conversions from sales.

Keep data lean

  • Visitors are recognised with a first-party ID, without third-party cookies.
  • Contact data goes to the platforms hashed only (SHA-256).
  • IP address and user agent are deleted after 60 days, immediately on withdrawal.

The result

One privacy mode per project that defines what happens before consent, a banner TSO understands directly, and a clear list per platform of the data that is sent.

Common mistakes

Works with

  • Google Ads
  • Meta

Frequently asked questions

Does this make TSO GDPR-compliant automatically?

TSO gives you the tools. Which legal basis you use and which mode you choose is up to you and your privacy adviser.

Does TSO set Consent Mode for Google?

On pages without their own data layer, the script sets Consent Mode itself, granted on consent and denied on withdrawal. If the page has its own, the script uses it.

What happens when consent is withdrawn?

The pixels stay silent for the rest of the page, and the visitor's IP address and user agent are deleted immediately.

Where is the data stored?

In Germany. You sign a data processing agreement with us under Art. 28 GDPR.

More use cases

Set it up in your project.

Hosted in Germany · Built in Austria