Skip to content

Commit 293b00f

Browse files
committed
Move misc items to new branch
1 parent b214654 commit 293b00f

File tree

3 files changed

+31
-1
lines changed

3 files changed

+31
-1
lines changed

src/_data/sidenav/main.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -515,6 +515,8 @@ sections:
515515
title: Configure Consent Management
516516
- path: /privacy/consent-management/consent-in-unify/
517517
title: Consent in Unify
518+
- path: /privacy/consent-management/consent-faq/
519+
title: Consent FAQs
518520
- path: /privacy/account-deletion
519521
title: Account & Data Deletion
520522
- path: /privacy/hipaa-eligible-segment

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Segment provides a OneTrust wrapper for the following sources:
5353
- **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.
5454
<!---- **React Native**: Please follow the instructions from the README in the [](){:target="_blank"} repository.--->
5555

56-
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.
56+
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.
5757

5858
> warning "Consent Management is not backwards compatible with Segment's legacy iOS and Android libraries"
5959
> 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.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Frequently Asked Questions
3+
plan: consent-management
4+
---
5+
6+
## Is Segment's Consent Manager part of Consent Management?
7+
8+
No. Segment's deprecated [open-source Consent Manager](https://github.com/segmentio/consent-manager){:target="_blank”}, which captures end user consent, is not part of Segment's Consent Management product, which focuses only on enforcing end user consent.
9+
10+
Segment recommends moving from the deprecated consent-manager to a commercial alternative, like [OneTrust](https://www.onetrust.com/){:target="_blank”}.
11+
12+
## What destinations support consent enforcement?
13+
14+
All event streams destinations, with the exception of AWS S3 and Engage destinations, support consent enforcement.
15+
16+
## Can I share current end user consent preferences with my destinations?
17+
18+
You can use the [Destination Actions framework](/docs/connections/destinations/actions/) to share the current status of your end-users' consent with your Actions destinations.
19+
20+
For more information, see the [Sharing consent with Actions destinations](/docs/privacy/consent-management/consent-in-unify/#sharing-consent-with-actions-destinations) documentation.
21+
22+
## Can I use a Consent Management Platform (CMP) other than OneTrust to collect consent from my end users?
23+
24+
Yes, you can use any commercially available CMP or custom solution to collect consent from your end users. If you use a CMP other than OneTrust, you must generate your own wrapper or other mechanism to add the following objects to the events collected from your sources:
25+
- Includes the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) on every event
26+
- 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. This event must contain their anonymousId or userId.
27+
28+
Segment provides guidance about creating your own wrapper in the [@segment/analytics-consent-tools](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} GitHub repository.

0 commit comments

Comments
 (0)