Skip to content

Commit 1016f25

Browse files
Update index.md
1 parent 51b2874 commit 1016f25

File tree

1 file changed

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

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -838,6 +838,9 @@ So, for example, if somebody follows the link with above query string to your si
838838
839839
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.
840840
841+
**Additional Note**:
842+
Segment does not validate UTM parameter names. This design supports the flexibility to track both standard parameters (e.g., utm_source, utm_medium) and custom parameters defined by users. As a result, all parameters present in the URL are collected as-is and added to the context field, without checks for naming conventions or validity.
843+
841844
## Analytics.js performance
842845
843846
The Analytics.js library and all Destination libraries are loaded with the [HTML script `async` tag](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script#attr-async){:target="_blank"}. This also means that Segment fires methods asynchronously, so you should adjust your code accordingly if you require that events be sent from the browser in a specific order.

0 commit comments

Comments
 (0)