SGTM + Consent Mode auto-redispatch: deduplication setup is critical
Automatic Page View Redispatch in Server-Side GTM After Consent Granted
Original: #GTMTips: Automatic Page View Hits In SGTM After Consent Granted
Importance: SGTM ユーザー向けの技術解説記事で、実装者が知っておくべき仕様変更だが、障害や破壊的変更ではなく、仕組みの理解促進が主眼
Summary
This technical article explains how server-side Google Tag Manager (SGTM) automatically redispatches page_view and conversion events to the SGTM endpoint when user consent transitions from denied to granted state using Google Consent Mode. This eliminates the need to manually reconfigure event dispatch after consent is granted, reducing implementation overhead. However, understanding this behavior is critical to avoid unexpected duplicate tracking if not properly managed.
Key Points
- SGTM auto-redispatches page_view when Consent Mode transitions to granted
- Conversion tags are also included in automatic redispatch
- Reduces manual reconfiguration effort post-consent
- Verify deduplication logic to prevent double-counting
View developer summary
When Consent Mode state transitions from denied to granted, hits marked with page_view and Conversions (key events) flags are automatically redispatched to the SGTM endpoint. This eliminates the previous requirement to manually reconfigure event dispatch post-consent, reducing implementation complexity. However, without proper deduplication logic in SGTM configuration, double-counting of events may occur.
Source: https://www.simoahava.com/gtmtips/automatic-page-view-hits-to-sgtm-after-consent-granted/
Outlet: Simo Ahava's blog
This article is an AI-generated summary (Claude Haiku 4.5) of publicly available information from Google, X, TikTok, Meta, LINE, YouTube and other marketing platforms. The original source URL is always provided in accordance with fair-use citation requirements. Summaries are AI-generated and may contain mistranslations or misinterpretations. Always verify details with the original source.