Skip to content

Commit 5fe630e

Browse files
committed
fix numbers
1 parent 2142180 commit 5fe630e

File tree

1 file changed

+5
-5
lines changed
  • src/connections/sources/catalog/libraries/website/javascript

1 file changed

+5
-5
lines changed

src/connections/sources/catalog/libraries/website/javascript/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Use the [Analytics.js QuickStart Guide](/docs/connections/sources/catalog/librar
2020

2121
## Benefits of Analytics.js
2222

23-
Analytics.js provides two key benefits over the previous version.
23+
Analytics.js provides 2 key benefits over the previous version.
2424

2525
### Performance
2626

@@ -301,7 +301,7 @@ Find more details about the Group method, including the payload, in [the Group S
301301

302302
### Alias
303303

304-
The Alias method combines two unassociated user identities. Segment usually handles aliasing automatically when you call Identify on a user, however some tools require an explicit Alias call.
304+
The Alias method combines 2 unassociated user identities. Segment usually handles aliasing automatically when you call Identify on a user, however some tools require an explicit Alias call.
305305

306306
This is an advanced method, but it's required to manage user identities successfully in *some* Segment destinations like [Kissmetrics](/docs/connections/destinations/catalog/kissmetrics/#alias) and [Mixpanel](/docs/connections/destinations/catalog/mixpanel/#alias). <!-- TODO: LR Dests question: is this still true? Is there a list of the ones that require this?-->
307307

@@ -883,7 +883,7 @@ Because Segment tracks across subdomains, you can either use the same Segment so
883883

884884
UTM parameters are only used when linking to your site from outside your domain. When a visitor arrives using a link containing UTM parameters, Segment's Analytics.js library will parse the URL query string and add the information to the event payload. For more information about UTM tracking, see the [Tracking Customers Across Channels and Devices](/docs/guides/how-to-guides/cross-channel-tracking/) documentation.
885885

886-
UTM parameters contain three essential components (utm_source, utm_medium, and utm_campaign) and two optional (utm_content and utm_term). For example, if you include the following three parameters in your URL: `?utm_source=mysource&utm_medium=email&utm_campaign=mytestcampaign`, once a visitor arrives using a link containing the above, Segment automatically grabs the UTM parameters and subsequent events will contain these parameters within the `context` object (visible in the raw view of your Source Debugger.)
886+
UTM parameters contain 3 essential components (utm_source, utm_medium, and utm_campaign) and 2 optional (utm_content and utm_term). For example, if you include the following 3 parameters in your URL: `?utm_source=mysource&utm_medium=email&utm_campaign=mytestcampaign`, once a visitor arrives using a link containing the above, Segment automatically grabs the UTM parameters and subsequent events will contain these parameters within the `context` object (visible in the raw view of your Source Debugger.)
887887

888888
So, for example, if somebody follows the link with above query string to your site, the subsequent Page call in your Debugger should contain the below and will be passed to any enabled destinations:
889889

@@ -945,7 +945,7 @@ Without any destinations enabled, the `analytics.min.js` file is about 62 KB. Ea
945945
946946
### Cookies set by Analytics.js
947947
948-
Segment sets three cookies in general:
948+
Segment sets 3 cookies in general:
949949
950950
| Cookie | Description |
951951
| ------------------ | --------------------------------------------------------------------------------- |
@@ -1053,7 +1053,7 @@ Once installed, use the Inspect Elements developer tool in Chrome to use the Seg
10531053
- Identify users
10541054
10551055
### Components of the Segment Inspector
1056-
The Segment Inspector is composed of these three components:
1056+
The Segment Inspector is composed of these 3 components:
10571057
1. The **Diagnostics** tab
10581058
- This tab shows the library versions and the list of active integrations that are running.
10591059
- When you select an integration, you can see the options that passed while the integration loads. If you made any local overrides within the integration or on the page itself, they appear highlighted in the code.

0 commit comments

Comments
 (0)