Skip to content

Commit ba487e8

Browse files
authored
Merge pull request #396 from segmentio/repo-sync
repo sync
2 parents fde83e9 + 5742b92 commit ba487e8

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ 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){:target='_blank'} or by running this script in your JavaScript console and replacing `G-xxxxxxxxxx` with your GA4 measurement ID:
84+
You can 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 Google Analytics 4 Measurement ID:
8585

8686
```java
8787
const sessionIdPromise = new Promise(resolve => {
-1.45 KB
Loading

src/engage/overview/onboarding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ Start by creating your Twilio account and getting an API key for Engage:
176176
2. In your Twilio console, select the **Account** dropdown menu, then **API keys & tokens**.
177177
3. On the Auth Tokens & API Keys page, click **Create API key**.
178178
4. Enter a name for the API key in the **Friendly name** field.
179-
5. Set the region to **United States (US1) - Default** and key type to **Standard**.
179+
5. Set the region to **United States (US1) - Default** and key type to **Main**.
180180
6. Click **Create API Key**.
181181
7. Copy both the **SID** and **Secret** field contents.
182182

0 commit comments

Comments
 (0)