Skip to content

Commit cd1600a

Browse files
ashton-huxtablemarkzegarelli
andauthored
Add troubleshooting section on duplicate events (#4953)
* Add troubleshooting section on duplicate events * Apply suggestions from code review Co-authored-by: markzegarelli <[email protected]> --------- Co-authored-by: markzegarelli <[email protected]>
1 parent 5a6ba8e commit cd1600a

File tree

1 file changed

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

1 file changed

+5
-1
lines changed

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

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

8282
### 404 Error
83-
8483
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.
8584

85+
### Duplicate Events
86+
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.
87+
88+
Google recommends using [transactionIds](https://support.google.com/google-ads/answer/6386790){:target="_blank" to prevent this duplication.
89+
8690

8791
## Appendices
8892

0 commit comments

Comments
 (0)