Skip to content

Commit 36086b3

Browse files
authored
Update src/connections/destinations/catalog/actions-google-analytics-4/index.md
1 parent 0a944dc commit 36086b3

File tree

1 file changed

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

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ In addition to recommended events, you can also send custom events using the [Cu
7272
#### Custom Dimensions & Metrics
7373
With Google Analytics 4, you must create custom dimensions and metrics within the Google Analytics 4 interface and link parameters to the corresponding dimension or metric. When creating the dimension or metric, you can either select a parameter from the list of already collected fields or enter the name of the parameter you plan to collect in the future. Custom dimensions can be either event-scoped or user-scoped, and custom metrics must always be event-scoped. To send parameters to Google Analytics 4, use the Event Parameters or User Properties object available on every action. Google will silently drop any events that include nested parameters so please ensure you are only passing flat key-value pairs in the Event Parameters and User Properties objects.
7474

75-
To achieve parity with Universal Analytics, you will probably want to create the same custom dimensions that you defined in Universal Analytics. Additionally, many of the values that you tracked as event dimensions in Universal Analytics, particularly event category and event label, should be recreated in Google Analytics 4 as custom dimensions. For more information, see Google’s [Google Analytics 4 Custom dimensions and metrics](https://support.google.com/analytics/answer/10075209){:target='_blank'}.
75+
To achieve parity with Universal Analytics, you'll probably want to create the same custom dimensions that you defined in Universal Analytics. Additionally, many of the values that you tracked as event dimensions in Universal Analytics, particularly event category and event label, should be recreated in Google Analytics 4 as custom dimensions. For more information, see Google’s [Google Analytics 4 Custom dimensions and metrics](https://support.google.com/analytics/answer/10075209){:target='_blank'}.
7676

7777
#### Tracking Active Users & Sessions
7878
The Google Analytics 4 reports will only display active users who engage with your site for a non-zero amount of time. To ensure users are rendered in reports, Segment sets the `engagement_time_msec` parameter to 1 by default. If you track engagement time on your Segment events, you can use the **Engagement Time in Milliseconds** field mapping to set `engagement_time_msec` to a different value.

0 commit comments

Comments
 (0)