Skip to content

Commit e9caccf

Browse files
authored
Merge pull request #5227 from segmentio/sarahrudy-patch-17-1
Add difference between GA4 Cloud and GA4 Web
2 parents 2610d12 + 4e3ba5d commit e9caccf

File tree

1 file changed

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

1 file changed

+2
-3
lines changed

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

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,6 @@ 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-
### Compare Google Analytics 4 metrics with Universal Analytics
98-
99-
As you set up Google Analytics 4, you should compare the reported results in your Google Analytics 4 property with those in your Universal Analytics property. This [Google article](https://support.google.com/analytics/answer/11986666?hl=en&sjid=3421230313554474956-NA#acquisition&zippy=%2Cin-this-article){:target="_blank"} explains the extent to which you can and cannot compare metrics between Universal Analytics and Google Analytics 4.
97+
### Differences between Google Analytics 4 Cloud and Google Analytics 4 Web destinations
10098

99+
Segment's [Google Analytics 4 Cloud](/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, whereas Segment's [Google Analytics 4 Web](/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. Each destination has its own advantages and disadvantages. Your choice between the two will depend on your specific use case, technical expertise, and the platforms from which you want to track data.

0 commit comments

Comments
 (0)