Skip to content

Commit 6645826

Browse files
Update guide to add a note about Consent Mode.md
### Proposed changes Adding a note to our Google destinations about our current work on Consent Mode. ### Merge timing ASAP once approved ### Related issues (optional) Slack: https://twilio.slack.com/archives/CC97A542H/p1708101546856579
1 parent 5322da3 commit 6645826

File tree

1 file changed

+3
-0
lines changed
  • src/connections/destinations/catalog/google-tag-manager

1 file changed

+3
-0
lines changed

src/connections/destinations/catalog/google-tag-manager/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ id: 54521fd625e721e32a72eeb9
1717
3. In your Segment UI's destination settings, enter your Container ID (note: it should start with "GTM-"). You can find this in the Admin section of your [GTM dashboard](https://tagmanager.google.com/#/admin/){:target="_blank"}.
1818
4. GTM loads on any pages where your Segment snippet is initialized and `analytics.page` is called in client-side JavaScript. Once you've turned on GTM through Segment, you can use Segment `track` events to populate the GTM `dataLayer`, and remove the GTML snippet from your page.
1919

20+
> info ""
21+
> Consent Mode: Segment is currently building Consent Mode functionality for all affected Google destinations. However, for GTM, please note that consent mode settings need to be managed directly [within your GTM account](https://support.google.com/tagmanager/answer/10718549?hl=en#tag-settings). Therefore, there's no direct update from Segment for the GTM destination regarding consent mode, as it is managed within GTM tags themselves.
22+
2023
> info ""
2124
> Segment recommends that you load GTM through Segment rather than loading Segment inside of GTM. When you load Segment through GTM, it limits Segment's ability to help troubleshoot.
2225

0 commit comments

Comments
 (0)