Skip to content

Commit c53930a

Browse files
authored
Update index.md - user-provided data feature (GA4)
1 parent dbf235b commit c53930a

File tree

1 file changed

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

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -229,5 +229,9 @@ Because [Google's Measurement Protocol API](https://developers.google.com/analyt
229229
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.
230230

231231
### Client/server-side event deduplication
232+
232233
Google doesn't offer guidance around how to deduplicate the same event coming in server and client side. As a result, Segment recommends 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](https://support.google.com/analytics/answer/9355949?hl=en){:target="_blank"} using the `User ID` field, but you cannot deduplicate whole events in the Google platform as far as Segment is aware.
233234

235+
### User-provided data collection
236+
237+
Google has introduced a beta feature for collecting data provided by users, [User-provided data collection](https://support.google.com/analytics/answer/14077171?hl=en&utm_id=ad). It's important to note that this feature is currently not supported by Segment, and, acknowledging this feature policy in your Google Analytics 4 Account has irreversible effects.

0 commit comments

Comments
 (0)