Skip to content

Commit 0c94456

Browse files
forstisabellaforstisabella
authored
Merge pull request #5634 from segmentio/consent-management-swift
Add info about Swift plugin to Consent Management docs
2 parents 1dc22c1 + a57cec8 commit 0c94456

File tree

1 file changed

+3
-10
lines changed

1 file changed

+3
-10
lines changed

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

+3-10
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@ Before you can configure consent in Segment, take the following steps:
2323
- **Know how your company uses each destination**. You need to know which destinations to map to each category.
2424
- **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.
2525

26-
<!-- TODO: fix above link to mobile consent repository-->
2726

2827
## Step 1: Create consent categories in the Segment app
2928

@@ -50,21 +49,15 @@ Once you've created consent categories in the Segment app, you need to integrate
5049
- If using Unify and Engage, generates the [Segment Consent Preference](/docs/privacy/consent-in-unify/#segment-consent-preference-event) event every time a user provides or updates their consent preferences with their anonymousId and userId
5150

5251
Segment provides a OneTrust wrapper for the following sources:
53-
- **Analytics.js**: 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"}.
52+
- **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.
5453
- **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.
55-
<!--- will not be released alongside the other two libraries, commenting out for now. - **Swift**: Please follow the instructions from the README in the [@repository](){:target="_blank"}.-->
54+
- **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.
5655

5756
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.
5857

59-
> warning "Consent Management is not backwards compatible with Segment's legacy Android library"
60-
> If you are using Segment's legacy Android library, you will need to upgrade to [Kotlin](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/migration/) before using Consent Management.
61-
62-
<!---
6358
> warning "Consent Management is not backwards compatible with Segment's legacy iOS and Android libraries"
6459
> 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.
6560
66-
--->
67-
6861
### Validate your CMP integration
6962

7063
Customers with Analytics.js 2.0 sources can use the [Segment Inspector](/docs/connections/sources/catalog/libraries/website/javascript/#segment-inspector) to confirm that events from their source contain the [consent object](/docs/privacy/consent-in-segment-connections). Unify and Engage users can also verify that the [Segment Consent Preference event](/docs/privacy/consent-in-unify/#segment-consent-preference-event) emits every time end users update their consent preferences.
@@ -89,4 +82,4 @@ Disabling a consent category means that Segment no longer enforces end user cons
8982

9083
1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
9184
2. On the Consent Management page, disable the toggle for the category you'd like to disable.
92-
3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.
85+
3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.

0 commit comments

Comments
 (0)