Article · June 17, 2026
Google Tag Manager and PDPL: Consent management for tracking tags
Google Tag Manager (GTM) loads tracking tags. Configure GTM to block tags before consent and integrate Consent Mode v2 under PDPL.
Quick answer
Why is GTM the consent control point?
Because all tracking tags go through GTM, this is the ideal place to enforce consent once for all. If misconfigured, GTM will fire a slew of tags as soon as the page loads — activating non-essential cookies before consent, violating the PDPL.
Compliant GTM configuration
Integrate consent signals:
Put the consent state (analytics/marketing) into the dataLayer.
Enable Consent Mode in GTM:
Configure integrated consent checks for each tag.
Set triggers by consent:
Analytics/Ads tags only fire when the corresponding group is consented.
Default to blocked:
Before any choices, the default is denied.
Test with Preview:
Use GTM’s Preview mode to confirm tags do not fire when denied.
Does GTM automatically comply with PDPL?
No. GTM provides tools (Consent Mode, consent checks) but proper configuration and obtaining/maintaining consent are the business’s responsibility. GTM needs to be combined with a banner/CMP that provides consent signals.
- GTM itself does not collect personal data; the issue lies with the tags it fires. You need to gate those tags based on consent.
- You can do it in both. GTM supports integrated consent checks; the CMP provides consent signals pushed into the dataLayer.
- Use GTM’s Preview mode and the browser’s developer tools to confirm no tracking tags run when the user declines.
consent.vn provides standard consent signals for GTM and Consent Mode v2, helping gate tracking tags in line with the PDPL.
Source: Luật 91/2025/QH15 — thuvienphapluat.vn | Google Tag Manager Consent — support.google.com
Get started — no account needed.
Ready to comply with PDPL?