Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add section on ISO date conversion #4508

Merged
merged 2 commits into from
Mar 31, 2023
Merged

Add section on ISO date conversion #4508

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
27337ad
Add section on ISO date conversion
ashton-huxtable Mar 30, 2023
9e5c0af
Add sentence casing to headers
rchinn1 Mar 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions src/connections/sources/catalog/libraries/website/javascript/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ For example, you can use Analytics.js 2.0 to build features that:
- Enrich events with customer or page context while in-flight with middleware
- Check an event for errors after the event is sent to Segment

## Getting Started
## Getting started

Use the [Analytics.js QuickStart Guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) to learn how to add Analytics.js to your site. Once you've installed the library, read on for the detailed API reference.

Expand Down Expand Up @@ -544,6 +544,15 @@ analytics.load('writekey', { obfuscate: true })

The `obfuscate` value is `false` by default.

#### ISO string conversion
By default, the Analytics.js library will convert ISO8061 strings to a Date object before passing it to downstream device-mode integrations. If you would like to disable this functionality and send those strings as they are passed to the event, you can use the load method to pass in the `disableAutoISOConversion` option.

For example:

```js
analytics.load('writekey', { disableAutoISOConversion: true })
```


## Retries

Expand Down Expand Up @@ -760,7 +769,7 @@ Analytics.js tracks across subdomains out of the box. All Segment destinations f

To track activity on your subdomains, include the Segment Analytics.js snippet on each subdomain. Segment sets users' `anonymousId` on the top-level domain, so that users are tracked across any subdomain.

Because Segment tracks across subdomains, you can either use the same Segment source, or use separate sources for each subdomain. What you decide depends on your team's goals for tracking each subdomain.
Because Segment tracks across subdomains, you can either use the same Segment source, or use separate sources for each subdomain. What you decide depends on your team's goals for tracking each subdomain.

## UTM Tracking

Expand All @@ -777,7 +786,7 @@ So, for example, if somebody follows the link with above query string to your si
"name": "mytestcampaign",
"source": "mysource",
},


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.

Expand Down