Skip to content

Commit 72743b4

Browse files
authored
GTM: Add info block
- add info block to be consistent with our other public pages - remove sentence about 404 error since it wouldn't be relevant for most customers and it exists in the troubleshooting section, which seems like a better spot for it?
1 parent 612e603 commit 72743b4

File tree

1 file changed

+2
-4
lines changed
  • src/connections/destinations/catalog/google-tag-manager

1 file changed

+2
-4
lines changed

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,8 @@ 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-
**Notes**
21-
* Segment recommends that you load GTM through Segment rather than loading Segment inside of GTM.
22-
* Be sure to "publish" your GTM container in GTM before trying to load it through Segment, otherwise your container URL will return a 404 error.
23-
20+
> info ""
21+
> Segment recommends that you load GTM through Segment rather than loading Segment inside of GTM. When you load Segment through GTM, it will limit our ability to help troubleshoot should you experience any technical issues.
2422
2523
## Page
2624
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:

0 commit comments

Comments
 (0)