Skip to content

Commit 2b6e0a4

Browse files
sanscontextOsama Khan
andauthored
itp edits (#1095)
Co-authored-by: Osama Khan <[email protected]>
1 parent 304b3af commit 2b6e0a4

File tree

6 files changed

+43
-63
lines changed

6 files changed

+43
-63
lines changed

src/_data/sidenav/main.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,8 +35,6 @@ sections:
3535
title: How does Segment handle duplicate data?
3636
- path: /guides/ignore-bots
3737
title: How can I ignore internet bots?
38-
- path: /guides/intelligent-tracking-prevention
39-
title: Is Segment impacted by Intelligent Tracking Prevention?
4038
- path: /guides/segment-vs-tag-managers
4139
title: What is the difference between Segment and tag managers?
4240
- path: /guides/what-is-replay

src/_data/sidenav/strat.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,8 @@ sections:
6262
section:
6363
- path: /connections/sources/catalog/libraries/website/javascript
6464
title: Analytics.js (Javascript) Source
65+
- path: /connections/sources/catalog/libraries/website/javascript/supported-browsers
66+
title: Analytics.js Supported Browsers
6567
- path: /connections/sources/catalog/libraries/website/javascript/quickstart
6668
title: Quickstart Tutorial
6769
- path: /connections/sources/catalog/libraries/website/javascript/identity

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

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -621,11 +621,6 @@ When enabled, Analytics.js automatically retries network and server errors. With
621621

622622
Analytics.js stores events in `localStorage` and falls back to in-memory storage when `localStorage` is unavailable. It retries up to 10 times with an incrementally increasing backoff between each retry. Analytics.js queues up to 100 events at a time to avoid using too much of the device's local storage. See the [destination Retries documentation](/docs/connections/destinations/#retries) to learn more.
623623

624-
625-
## Proxying Analytics.js
626-
627-
To use a proxy server with Analytics.js, first change the `cdn.segment.com` address in the snippet to use your own host. Next, [contact Segment Product Support](https://segment.com/help/contact/) and request to change the endpoint Segment sends your events to so that is uses your proxy instead. Make sure that your proxy behaves exactly like the Segment APIs. You can use [the Segment proxy server](https://github.com/segmentio/segment-proxy) as an example of a correctly-working proxy.
628-
629624
## Plugins
630625

631626
Segment offers video player 'plugins' so you can quickly collect video events using Analytics.js. See the specific documentation below to learn more:
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Analytics.js Browser Support
3+
redirect_from: '/guides/intelligent-tracking-prevention'
4+
strat: ajs
5+
---
6+
7+
[The Segment JavaScript library, Analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/), loads a snippet on your webpage that supports existing user consent APIs and native browser controls. Segment regularly tests Analytics.js against the following browsers on all major platforms, and updates the library accordingly.
8+
9+
The library is regularly tested and is functional with the following browsers:
10+
11+
- Internet Explorer
12+
- Apple Safari
13+
- Google Chrome
14+
- Mozilla Firefox
15+
- Microsoft Edge
16+
- Brave
17+
18+
### Internet Explorer Support
19+
20+
Segment guarantees support for Internet Explorer 11 and later for Analytics.js. Remember that different bundled (device-mode) destinations might have different compatibility guarantees for their own products. Refer to the vendor’s documentation to confirm browser compatibility.
21+
22+
23+
## Tracking Protection (ITP, ETP)
24+
25+
Segment is a customer data platform (CDP) that helps companies harness first-party customer data. The recent browser changes fully align with Segment’s privacy stance.
26+
27+
Browser manufacturers have enhanced their privacy features by adding third-party tracking protection mechanisms for end-users. These browser changes target third-party trackers and their cookies, and each platform takes a different approach.
28+
29+
For example, [Firefox Enhanced Tracking Protection (ETP)](https://blog.mozilla.org/blog/2020/08/04/latest-firefox-rolls-out-enhanced-tracking-protection-2-0-blocking-redirect-trackers-by-default/) relies on a dynamic list of known trackers to decide what to block. Browsers that use [Apple’s Webkit engine](https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/), like Safari and Chrome for iOS, use Intelligent Tracking Protection (ITP) which actively prevents the browser from loading cookies from a third-party domain.
30+
31+
> info ""
32+
> **Note:** Segment cookies expire after seven days of user inactivity, like all other application cookies under the Webkit engine ITP policy.
33+
34+
## Proxying Analytics.js
35+
36+
Because of regulatory, environmental, or security concerns, some customers prefer to set up proxy infrastructure for Analytics.js. You can use the `apihost` configuration option in the Analytics object to route traffic to different API endpoints. Business Tier customers can use Segment’s fully-managed proxy service: In-domain Instrumentation, which provides a similar function without the additional maintenance burden and cost of running your own proxy infrastructure.
37+
38+
> info ""
39+
> Business Tier customers who want to use a fully-managed proxy service can contact their account teams for full details.

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

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -51,15 +51,6 @@ In the below image, we use Google Analytics as an example. Our `page` call forms
5151

5252
If this outbound request is not showing up in the network when you fire an `identify` call, then check the following:
5353

54-
## Do you have any ad blockers enabled in your browser?
55-
56-
Segment and many destination partners use cookies/local storage to store information about users in the browser. Ad blockers prevent cookies and other data these tools rely on to make valid analytics requests. Some portion of your users are probably using ad blockers, which prevent the Segment script from fully executing. Both desktop and mobile browsers are impacted.
57-
58-
One particular issue is Safari private browsing mode which allows Analytics.js Identify calls to be made, but the traits object is stripped from the call. This results in identify calls missing email address and other traits.
59-
60-
## Internet Explorer Support
61-
62-
We guarantee support for Internet Explorer 9 and higher for Analytics.js. Keep in mind that different tools may have different compatibility guarantees for their own products. Refer to the vendor's documents to see what their browser compatibility looks like.
6354

6455
## Is your web site deployed under a domain on the Public Suffix List?
6556

@@ -115,7 +106,7 @@ console.log(JSON.stringify({ x: undefined, y: 6 }));
115106

116107
### Can I overwrite the context fields?
117108

118-
Yes. This can be useful if some of these fields contain information you don't want to collect.
109+
Yes. This can be useful if some of these fields contain information you don't want to collect.
119110

120111
For example, imagine that your website allows users to view a receipt for purchases at the URL `https://mywebsite.com/store/purchases`. Your users click a link that redirects to that specific URL, your app sets a `receiptId` in the query string, and returns the appropriate receipt. You also send a Track call to Segment from this page.
121112

@@ -125,7 +116,7 @@ Since this `receiptId` might contain sensitive information, you can prevent the
125116
analytics.track("Receipt Viewed", {}, {
126117
page: {
127118
url: null
128-
}
119+
}
129120
})
130121
```
131122

src/guides/intelligent-tracking-prevention.md

Lines changed: 0 additions & 45 deletions
This file was deleted.

0 commit comments

Comments
 (0)