Skip to content

Commit 6b5f57e

Browse files
Merge pull request #5281 from segmentio/onetrust-consent-docs-replace-instructions-with-link-to-readme
Replace OneTrust consent docs with link to README
2 parents b5937c3 + 5e98532 commit 6b5f57e

File tree

1 file changed

+1
-45
lines changed

1 file changed

+1
-45
lines changed

src/privacy/configure-consent-management.md

Lines changed: 1 addition & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -40,51 +40,7 @@ Before you can configure consent in Segment, take the following steps:
4040
> Segment assumes all destinations without a mapping do not require user consent and will receive all events containing a consent object.
4141
4242
## Step 2: Add the consent wrapper to Analytics.js
43-
44-
If you're using OneTrust as your CMP, you can install the OneTrust integration consent wrapper (`@segment/analytics-wrapper-onetrust`) using a [snippet](#onetrust-for-snippet-users-windowanalytics) or [npm](#onetrust-for-npm-library-users).
45-
46-
If you have a CMP other than OneTrust, you can install the `@segment/analytics-consent-tools` package using the [instructions in the analytics-next repository](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank”}.
47-
48-
> error "After adding the consent object to your events, your data is immediately impacted"
49-
> If you disable a consent category, end user consent preferences for that category will not be enforced.
50-
>
51-
> If a destination is mapped to more than one other consent category, and an end user's consent preferences is "false" for either category, data will not get sent.
52-
>
53-
> If an event includes both an integrations object and a consent object, Segment will look at the consent object first, and then take into account the integrations object.
54-
55-
### OneTrust for snippet users (window.analytics)
56-
Delete the `analytics.load()` line from the snippet in the header of your website:
57-
58-
```diff
59-
- analytics.load("<MY_WRITE_KEY>");
60-
```
61-
62-
Run the following initialization code in your project, replacing `<MY_WRITE_KEY>` with your write key:<sup>1</sup>
63-
```ts
64-
import { oneTrust } from '@segment/analytics-consent-wrapper-onetrust'
65-
66-
67-
// snippet users
68-
oneTrust(window.analytics)
69-
window.analytics.load('<WRITE_KEY>')
70-
```
71-
72-
### OneTrust for npm library users
73-
74-
Initialize the OneTrust wrapper by running the following code on your command line, replacing `<MY_WRITE_KEY>` with your write key:<sup>1</sup>
75-
76-
```ts
77-
import { oneTrust } from '@segment/analytics-consent-wrapper-onetrust'
78-
import { AnalyticsBrowser } from '@segment/analytics-next'
79-
80-
export const analytics = new AnalyticsBrowser()
81-
82-
oneTrust(analytics)
83-
84-
analytics.load({ writeKey: '<MY_WRITE_KEY'> })
85-
```
86-
87-
<sup>1</sup>: You can find your write key by navigating to Connections > Sources > [Source Name] > Settings.
43+
Please follow the instructions from the README in the [@segment/analytics-consent-wrapper-onetrust repository](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"}.
8844

8945
## Edit consent categories
9046

0 commit comments

Comments
 (0)