Skip to content

Commit 7b17471

Browse files
Apply suggestions from code review
1 parent 6c8d7c4 commit 7b17471

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -762,9 +762,9 @@ To track activity on your subdomains, include the Segment Analytics.js snippet o
762762

763763
## UTM Tracking
764764

765-
UTM parameters are only used when linking to your site from outside your domain. When a visitor arrives via a link containing UTM parameters, our analytics.js library will parse the URL query string and add the information to the event payload. Further details in our best practices guide [here](https://segment.com/docs/guides/how-to-guides/cross-channel-tracking/)
765+
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.
766766

767-
UTM parameters contain three essential components (utm_source, utm_medium, utm_campaign) and two optional (utm_content, utm_term). For example, having the following three parameters included in your URL: ?utm_source=mysource&utm_medium=email&utm_campaign=mytestcampaign, once a visitor arrives via a link containing the above, we automatically grab the UTM parameters and subsequent events will contain these parameters within the 'context' object (visible in your source Debugger in the raw view).
767+
UTM parameters contain three essential components (utm_source, utm_medium, utm_campaign) and two optional (utm_content, 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.)
768768

769769
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:
770770

@@ -777,7 +777,7 @@ So, for example, if somebody follows the link with above query string to your si
777777
},
778778

779779

780-
Whenever the UTM parameters are no longer a part of the URL, we will no longer include them. For example, if the user goes to a new page within your website which does not contain these parameters, they will not be included in subsequent events. UTM parameters are non-persistent by default as they could potentially cause data accuracy problems. Here's an example of why: Say a user clicks on an ad and lands on your site. He navigates around and bookmarks an internal page - or maybe shares a link with a friend, who shares it with another friend. All those links would then point back to the same test utm_source as the initial referrer for any purchase.
780+
Whenever the UTM parameters are no longer a part of the URL, Segment no longer includes them. For example, if the user goes to a new page within your website which does not contain these parameters, they will not be included in subsequent events. UTM parameters are non-persistent by default as they could potentially cause data accuracy problems. Here's an example of why: Say a user clicks on an ad and lands on your site. He navigates around and bookmarks an internal page - or maybe shares a link with a friend, who shares it with another friend. All those links would then point back to the same test utm_source as the initial referrer for any purchase.
781781

782782
## Analytics.js performance
783783

0 commit comments

Comments
 (0)