TDDDG § 25 & Google Consent Mode v2: Compliant GTM Setup for German Websites & Agencies
On May 14, 2024, Germany officially enacted the TDDDG (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz), replacing the former TTDSG to align national terminology with the European Digital Services Act (DSA).
For German website operators, eCommerce merchants, and digital agencies across Berlin, Munich, Frankfurt, and Hamburg, Section 25 of the TDDDG (§ 25 TDDDG) remains the central pillar of digital measurement law. It mandates that accessing or storing information on an end-user’s device (including cookies, local storage, session storage, and browser fingerprints) is strictly unlawful without informed, unambiguous, and prior consent.
At the same time, Google’s EU User Consent Policy requires all advertisers using Google Ads or Google Analytics 4 in Germany to implement Google Consent Mode v2. Without it, automated Smart Bidding algorithms lose conversion data, remarketing audiences fail to populate, and campaign performance deteriorates.
In this technical guide, I outline the exact Google Tag Manager (GTM) architecture required to achieve airtight compliance with TDDDG § 25 while preserving Google Ads conversion modeling and GA4 reporting fidelity.
Key Takeaways for German Businesses & Marketing Agencies
- TDDDG § 25 Applies Independently of GDPR: Section 25 protects device integrity regardless of whether personal data (PII) is processed. Setting any non-essential cookie or reading local storage without prior consent is a direct statutory violation.
- Basic vs. Advanced Consent Mode v2: Understand the legal and technical trade-offs. Basic Consent Mode blocks Google tags entirely until consent is granted. Advanced Consent Mode fires cookieless pings when consent is denied, enabling Google’s machine-learning algorithms to model missing conversions legally.
- Consent Initialization Triggering: All consent default commands (
gtag('consent', 'default', {...})) must execute on theConsent Initialization - All Pagestrigger before any other tag or CMP script evaluates. - Seamless CMP Integration: Standardized integration workflows for leading German Consent Management Platforms (CMPs) including Usercentrics, Cookiebot, Borlabs Cookie, and CCM19.
Understanding TDDDG § 25: The Legal Requirement
Section 25 Paragraph 1 of the TDDDG states:
“The storage of information in the terminal equipment of the end user or the access to information already stored in the terminal equipment of the end user is only permissible if the end user has consented on the basis of clear and comprehensive information.”
What This Means in Practice:
- No Pre-Ticked Boxes or Deceptive Banners: Consent banners must offer equally prominent buttons for “Accept All” (Alle akzeptieren) and “Reject All” (Nur essenzielle Cookies akzeptieren). Dark patterns are actively penalized by German courts and state data protection authorities (e.g., BayLDA, LfDI Baden-Württemberg).
- Prior Consent is Mandatory: No tracking script (Meta Pixel, Google Ads tag, TikTok pixel, LinkedIn insight tag) may fire before the user explicitly clicks “Accept”.
- Statutory Exceptions are Narrow: Only cookies that are “technically strictly necessary” (unbedingt erforderlich) to provide the service explicitly requested by the user (such as shopping cart cookies or CSRF security tokens) are exempt from consent.
The Consent Mode v2 Parameters
Google Consent Mode v2 introduced two mandatory parameters alongside the original analytics and advertising flags:
| Parameter | Purpose | TDDDG Implication |
|---|---|---|
ad_storage | Allows reading/writing cookies for advertising | Must be denied until user accepts marketing |
analytics_storage | Allows reading/writing cookies for GA4 | Must be denied until user accepts statistics |
ad_user_data | Grants consent to send user data to Google for ads | New in v2: Controls transmission of user signals |
ad_personalization | Controls whether data is used for remarketing | New in v2: Dictates audience list enrollment |
Basic vs. Advanced Consent Mode in Germany
One of the most frequent debates among German agencies and data protection officers (Datenschutzbeauftragte - DSB) is whether to deploy Basic or Advanced Consent Mode:
1. Basic Consent Mode v2
- How it works: When a visitor rejects consent, Google tags are completely blocked from executing. Zero network requests leave the browser.
- Legal Profile: Safest legal profile with minimal regulatory scrutiny.
- Data Impact: 100% blind to non-consenting users. Zero conversion modeling in Google Ads; GA4 reports significant traffic drops.
2. Advanced Consent Mode v2
- How it works: Google tags load immediately, but operate in a restricted, cookieless state. When consent is denied, tags send cookieless pings that contain no user identifiers or device storage access.
- Legal Profile: Defensible under TDDDG § 25 because cookieless pings do not access or store information on the user’s terminal equipment. However, requires explicit disclosure in your privacy policy (Datenschutzerklärung).
- Data Impact: Google Ads machine-learning algorithms model some conversions from non-consenting users, which helps Smart Bidding keep learning.
Step-by-Step GTM Configuration
Step 1: Set Default Consent State on Consent Initialization
Create a Custom HTML tag in GTM triggered exclusively on the built-in Consent Initialization - All Pages trigger:
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
// Establish default consent states before CMP evaluates
gtag('consent', 'default', {
'ad_storage': 'denied',
'analytics_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
'wait_for_update': 500 // Milliseconds to wait for CMP to load
});
// Enable Google Ads URL parameter passthrough for click attribution
gtag('set', 'url_passthrough', true);
gtag('set', 'ads_data_redaction', true);
</script>
Step 2: Configure the CMP Update Listener
When the visitor interacts with your CMP (e.g., Usercentrics or Cookiebot), the CMP pushes a consent event to the dataLayer. Your GTM container must listen for this event and issue the update command:
gtag('consent', 'update', {
'ad_storage': userConsentedToMarketing ? 'granted' : 'denied',
'analytics_storage': userConsentedToStats ? 'granted' : 'denied',
'ad_user_data': userConsentedToMarketing ? 'granted' : 'denied',
'ad_personalization': userConsentedToMarketing ? 'granted' : 'denied'
});
Step 3: Enforce Tag-Level Consent Checks in GTM
In Google Tag Manager, ensure that every non-Google advertising tag (Meta Pixel, TikTok, Microsoft Advertising, LinkedIn Insight) has Additional Consent Checks enabled under Advanced Settings → Consent Settings, requiring ad_storage before firing.
Real-World Case Studies
Discover how server-side tracking, deduplication, and attribution modeling drive measurable revenue growth:
- Fintech & Regulated Privacy Tracking: Read how we resolved cross-domain consent splits in the Fintech Cross-Domain GA4 & Consent Mode Case Study.
- Server-Side GTM on EU Cloud Infrastructure: Explore the architecture in the Server-Side GTM on Google Cloud EU Case Study.
- Shopify & Multi-Currency Purchase Reconciliation: Learn how we fixed missing transaction attribution in the Shopify Purchase Reconciliation Case Study.
Frequently Asked Questions
Does TDDDG § 25 apply to server-side tracking?
Yes. If your website collects information from the user’s browser (e.g., via JavaScript or cookies) before transmitting it to a server container, that initial collection falls under TDDDG § 25. Server-side tracking gives you powerful data hygiene and proxy controls, but it does not exempt you from obtaining consent for marketing measurement.
What happens if a German website ignores Consent Mode v2?
If you do not pass valid consent signals to Google, Google Ads will block the creation and updating of remarketing audiences for European traffic. Furthermore, Google Ads Conversion Modeling will be disabled, leading to degraded Smart Bidding performance and higher Cost Per Acquisition (CPA).
Can we host our server container inside Germany?
Yes. We deploy server-side containers on Google Cloud Run in the Frankfurt region (europe-west3). This ensures that analytics hits remain within German borders, minimizing latency and providing full compliance with European data sovereignty guidelines.
Related Tracking Services & European Hubs
- DACH Region Solutions: Explore our Germany GA4 services, Austria GA4 services, and Switzerland GA4 services.
- Diagnostic Utilities: Test your consent signals with our Consent Mode Sandbox or debug tags with the Consent Tag Debugger.
- Book a Technical Consultation: Request a free tracking consultation to audit your GTM container and verify your TDDDG and Consent Mode v2 compliance.
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.
