Skip to content

Commit 4ad2173

Browse files
authored
Add tips regrading GTM 404 error
1 parent 22bb7fe commit 4ad2173

File tree

1 file changed

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

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,8 @@ Segment sends it to the `dataLayer` as an object like this:
8080
## Troubleshooting
8181

8282
### 404 Error
83-
If you are seeing `404` error on the JavaScript console of your page and it is attributed to Google Tag Manager, it is likely that you have yet to publish your GTM container.
83+
If you are seeing `404` error on the JavaScript console of your page and it is attributed to Google Tag Manager, it is likely that you have yet to publish your GTM container. If the issue still persists, please ensure that Google's preview mode is disabled and that the [environment variable](/docs/connections/destinations/catalog/google-tag-manager/#environment) is removed from your destination settings.
84+
8485

8586
### Duplicate Events
8687
If you have Google Ads enabled and see duplicate events in GTM, check to see if the event is set as a conversion in Google Ads. Duplicate conversions are common when you use both Google Ads and GTM, since Segment's Adwords destination initializes the gtag script with the dataLayer itself. So, when you fire a mapped event, Segment submits the payload directly to the dataLayer.

0 commit comments

Comments
 (0)