Skip to content

Commit 74554ab

Browse files
add information on deduplication
1 parent 059aa56 commit 74554ab

File tree

1 file changed

+3
-0
lines changed
  • src/connections/destinations/catalog/actions-google-analytics-4

1 file changed

+3
-0
lines changed

src/connections/destinations/catalog/actions-google-analytics-4/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -219,3 +219,6 @@ Because [Google's Measurement Protocol API](https://developers.google.com/analyt
219219

220220
The Google Analytics 4 Cloud destination does not support Google Optimize. This destination operates in cloud-mode (sending events from Segment servers to Google Analytics using the Measurement Protocol API), which prevents the required [Optimize SDK](https://support.google.com/optimize/answer/11287798?visit_id=637903946258690719-978290187&rd=1){:target="_blank"} snippet from loading on the page.
221221

222+
### Client/Server-side Event Deduplication
223+
Google doesn't offer guidence around how to deduplicate the same event coming in server and client-side. As that is the case, Segment advises that you not send the same event into Google Analytics 4 from two different locations such that you would expect Google to deduplicate one of the events out of their pipeline. You can [deduplicate user counts]([url](https://support.google.com/analytics/answer/9355949?hl=en)) using the `User ID` field, but you cannot deduplicate whole events in the Google platform as far as Segment is aware.
224+

0 commit comments

Comments
 (0)