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

stayseesong · markzegarelli · web-flow · commit 0de4178ca8f4 · 2023-03-16T09:14:11.000-07:00
Co-authored-by: markzegarelli &lt;mark.zegarelli@segment.com&gt;
diff --git a/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md b/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md
@@ -51,4 +51,4 @@ The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/
 
 ### Send events from both the browser and the server 
 
-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.
+With Google Analytics 4 Web, events are sent from the browser to GA4. If you use Segment’s [Google Analytics 4 Cloud destination](/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 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. For more information, see [Google Analytics 4 destination: User Identification](/docs/connections/destinations/catalog/actions-google-analytics-4/#user-identification) on the next steps.

Original file line number	Diff line number	Diff line change
`@@ -51,4 +51,4 @@ The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/`
`51`	`51`
`52`	`52`	`### Send events from both the browser and the server`
`53`	`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.
	`54`	+With Google Analytics 4 Web, events are sent from the browser to GA4. If you use Segment’s [Google Analytics 4 Cloud destination](/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 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. For more information, see [Google Analytics 4 destination: User Identification](/docs/connections/destinations/catalog/actions-google-analytics-4/#user-identification) on the next steps.