Skip to content

Commit 397d026

Browse files
Adding details about the clientId
When customers are combining device-mode and cloud-mode, they'll need to take care of passing the clientid to Segment. Adding this topic to the GA4 Web documentation, as this will likely be a common question from customers.
1 parent 278f498 commit 397d026

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
@@ -48,3 +48,7 @@ With Google Analytics 4, you must create custom dimensions and metrics within th
4848
### Debug Mode
4949

5050
The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/7201382?hl=en){:target="_blank"} is supported with the Google Analytics 4 Web destination. DebugView displays the events and user properties that Analytics collects from a user in real-time. This can be helpful in troubleshooting your implementation.
51+
52+
### Send events from both the browser and the server
53+
54+
With Google Analytics 4 Web events are sent from the browser to GA4. If you choose to also use Segment’s [Google Analytics 4 Cloud](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4/#benefits-of-google-analytics-4-cloud) to send events through the API and tie data between client-side and server-side, you'll need to pass the same Client ID from the browser and the server. To do this, fetch the Gtag-generated **clientId** on the web client and pass it to Segment as a property. See more details [here](https://segment.com/docs/connections/destinations/catalog/actions-google-analytics-4/#user-identification) on the next steps.

0 commit comments

Comments
 (0)