Skip to content

Commit bec9eb5

Browse files
authored
Add difference between GA4 Cloud and GA4 Web
1 parent 3f3d232 commit bec9eb5

File tree

1 file changed

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

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,3 +94,7 @@ UTM Parameters are automatically tracked and sent to Google when they are presen
9494

9595
Without any further configuration, traffic-source data for `campaign`, `campaign_id`, `content`, `medium`, and `source` will populate in GA4. This can be observed on Google's side by triggering a `Page` call with UTM parameters present in the URL and navigating to the **Realtime overview** report in GA4 to see the resulting `page_view` event under the _Event count by Event name_ card.
9696

97+
### Difference between Google Analytics 4 Cloud and Google Analytics 4 Web destinations
98+
99+
Segment's [Google Analytics 4 Cloud](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, while Segment's [Google Analytics 4 Web](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4-web/) device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. There are advantages and disadvantages to each destination and your choice between the two will depend on your specific use case, technical expertise, and the platforms from which you want to track data.
100+

0 commit comments

Comments
 (0)