You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/privacy/consent-management/configure-consent-management.md
+14-7Lines changed: 14 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,19 +39,26 @@ Before you can configure consent in Segment, take the following steps:
39
39
40
40
## Step 2: Integrating your CMP with Segment
41
41
42
-
Once you've created consent categories in the Segment app, you need to integrate your CMP with Segment. Segment recommends using a CMP wrapper, but you can use any solution provided it meets the following criteria:
43
-
- Reads the end user consent preference from your CMP and includes the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) in every event
44
-
- 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
42
+
Once you've created consent categories in the Segment app, you need to integrate your CMP with Segment.
45
43
46
-
Segment supports the following wrappers:
44
+
Segment supports the following CMPs:
47
45
48
46
| Consent Management Platform | Supported web libraries | Supported mobile libraries | Contact |
| OneTrust |[Analytics.js](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} |[Kotlin](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"} <br> [Swift](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"} <br> [React Native](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-onetrust){:target="_blank"} | For support and troubleshooting, contact [Segment](mailto:[email protected]){:target="_blank"}. |
51
-
| Ketch |[Analytics.js](https://docs.ketch.com/ketch/docs/segment-tag-management-automation){:target="_blank"} || For support and troubleshooting, contact [Ketch](https://www.ketch.com/contact-us){:target="_blank"}. |
48
+
| OneTrust |[Analytics.js](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"}<sup>*</sup> |[Kotlin](https://github.com/segment-integrations/analytics-kotlin-consent/blob/main/README.md#getting-started){:target="_blank"} <br> [Swift](https://github.com/segment-integrations/analytics-swift-consent#segment-consent-management){:target="_blank"} <br> [React Native](https://github.com/segmentio/analytics-react-native/tree/master/packages/plugins/plugin-onetrust){:target="_blank"} | For support and troubleshooting, contact [Segment](mailto:[email protected]){:target="_blank"}. |
52
49
| TrustArc |[Analytics.js](https://github.com/trustarc/trustarc-segment-wrapper){:target="_blank"} || For support and troubleshooting, contact [TrustArc](https://trustarc.com/contact/){:target="_blank"}. |
50
+
| Ketch |[Analytics.js](https://docs.ketch.com/ketch/docs/segment-tag-management-automation){:target="_blank"} || For support and troubleshooting, contact [Ketch](https://www.ketch.com/contact-us){:target="_blank"}. |
51
+
52
+
<sup>*</sup>_If you send data to device-mode destinations connected to your Analytics.js source, you must navigate to your Analytics.js source in the Segment app, select **Settings > Analytics.js**, and enable Destination Filters._
53
+
54
+
> success ""
55
+
> For more information about Segment’s Analytics.js OneTrust wrapper, see the [Analytics.js OneTrust Wrapper](/docs/privacy/consent-management/onetrust-wrapper/) documentation.
56
+
57
+
If you'd like to integrate with any other CMP, Segment requires you to build your own wrapper or use any mechanism provided it meets the following requirements for data and event generation:
58
+
- Reads the end user consent preference from your CMP and includes the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) in every event
59
+
- 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
53
60
54
-
If you'd like to integrate with any other CMP, Segment requires you to build your own wrapper or use any mechanism provided it meets the above requirements of data and event generation. To get started building your own wrapper, follow the instructions in the [@segment/analytics-consent-tools](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} repository.
61
+
To get started building your own wrapper, follow the instructions in the [@segment/analytics-consent-tools](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} repository.
55
62
56
63
> warning "Consent Management is not backwards compatible with Segment's legacy iOS and Android libraries"
57
64
> If you are using one of Segment's legacy mobile libraries (iOS or Android,) you will need to upgrade to [Swift](/docs/connections/sources/catalog/libraries/mobile/apple/migration/) or [Kotlin](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/migration/) before using Consent Management.
0 commit comments