Skip to content

Commit 914a63f

Browse files
Merge pull request #6706 from segmentio/destination-filters-analytics-js-consent-wrapper
Add info about users enabling a.js dest filters for onetrust wrapper users (consent management)
2 parents 564c74d + c9cd843 commit 914a63f

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

src/privacy/consent-management/configure-consent-management.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ Before you can configure consent in Segment, take the following steps:
1717
- **Set up your third-party consent management tool and create consent categories**. Take note of your consent categories and the key or ID associated with each category.
1818
- **Know how your company uses each destination**. You need to know which destinations to map to each category.
1919
- **Access to your web and mobile libraries**. After you set up consent categories in the Segment app, you need to integrate your CMP and your Segment sources using a wrapper or other solution.
20+
- _For Analytics.js sources only_ : Navigate to your Analytics.js source. Select **Settings > Analytics.js** and enable **Destination Filters**.
2021

2122

2223
## Step 1: Create consent categories in the Segment app
@@ -43,7 +44,7 @@ Once you've created consent categories in the Segment app, you need to integrate
4344
- If using Unify and Engage, generates the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event every time a user provides or updates their consent preferences with their anonymousId and userId
4445

4546
Segment provides a OneTrust wrapper for the following sources:
46-
- **Analytics.js**: Please follow the instructions from the README in the [@segment/analytics-consent-wrapper-onetrust](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} repository. For more information about Segment's Analytics.js OneTrust wrapper, see the [Analytics.js OneTrust Wrapper](/docs/privacy/consent-management/onetrust-wrapper) documentation.
47+
- **Analytics.js**: Please follow the instructions from the README in the [@segment/analytics-consent-wrapper-onetrust](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} repository. For more information about Segment's Analytics.js OneTrust wrapper, see the [Analytics.js OneTrust Wrapper](/docs/privacy/consent-management/onetrust-wrapper) documentation. You should also navigate to your Analytics.js source in the Segment app, select **Settings > Analytics.js**, and enable **Destination Filters** before enabling your OneTrust wrapper.
4748
- **Kotlin**: Please follow the instructions from the README in the [@segment-integrations/analytics-kotlin-consent](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"} repository.
4849
- **Swift**: Please follow the instructions from the README in the [@segment-integrations/analytics-swift-consent](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"} repository.
4950
<!---- **React Native**: Please follow the instructions from the README in the [](){:target="_blank"} repository.--->

0 commit comments

Comments
 (0)