Skip to content

Commit 3bc0dc5

Browse files
Update index.md
1 parent c818c91 commit 3bc0dc5

File tree

1 file changed

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

1 file changed

+0
-1
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,6 @@ The Google Analytics 4 reports only display active users who engage with your si
8181

8282
If you choose to integrate with Google Analytics 4 client-side (using Gtag outside of Segment) _and_ also use Segment's Google Analytics 4 destination to send events through the API, you can track sessions server-side. When using Gtag, [Google generates a `session_id` and `session_number` when a session begins](https://support.google.com/analytics/answer/9191807?hl=en){:target='_blank'}. The `session_id` and `session_number` generated on the client can be passed as Event Parameters to stitch events sent through the API with the same session that was collected client-side.
8383

84-
Ripping off that old section we could maybe add this line at the end of the Session section:
8584
You can double-check your session_id and session_number with the [Google Site Tag function](https://developers.google.com/tag-platform/gtagjs/reference) or by running this script in your JavaScript console and replacing G-xxxxxxxxxx with your GA4 measurement ID:
8685
```const sessionIdPromise = new Promise(resolve => {
8786
gtag('get', 'G-xxxxxxxxxx', 'session_id', resolve)

0 commit comments

Comments
 (0)