Skip to content

Commit e2344d7

Browse files
authored
Apply suggestions from code review
1 parent 846b638 commit e2344d7

File tree

1 file changed

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

1 file changed

+2
-3
lines changed

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

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,8 +81,8 @@ 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-
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:
85-
```
84+
You can double-check your session_id and session_number with the [Google Site Tag function](https://developers.google.com/tag-platform/gtagjs/reference){:target='_blank'} or by running this script in your JavaScript console and replacing `G-xxxxxxxxxx` with your GA4 measurement ID:
85+
```java
8686
const sessionIdPromise = new Promise(resolve => {
8787
gtag('get', 'G-xxxxxxxxxx', 'session_id', resolve)
8888
});
@@ -94,7 +94,6 @@ Promise.all([sessionIdPromise, sessionNumPromise]).then(function(session_data) {
9494
console.log("session ID: "+session_data[0]);
9595
console.log("session Number: "+session_data[1]);
9696
});
97-
```
9897

9998
> info "Session tracking limitations"
10099
> Session tracking server-side only works if you're also sending data to Google Analytics 4 client-side. This is because the `session_id` must match a value that was previously collected on the client. For events to stitch properly, they must arrive within a 48 hour window of when the client-side events arrived.

0 commit comments

Comments
 (0)