diff --git a/src/privacy/consent-management/onetrust-wrapper.md b/src/privacy/consent-management/onetrust-wrapper.md index 6e1538deb6..1270604997 100644 --- a/src/privacy/consent-management/onetrust-wrapper.md +++ b/src/privacy/consent-management/onetrust-wrapper.md @@ -20,15 +20,9 @@ The OneTrust consent banner has three key UI configurations that control how the - **Opt-In:** The user, by default, does not consent to all categories (except those that you deem to be mandatory). The user is required to select categories that they consent to share data with (or, "opt-in" to data collection) - **Opt-out:** The user, by default, does consent to all categories. The user can choose to select categories that they do not consent to share data with (or, "opt-out" of data collection) -
-
-
-

Segment's Analytics.js OneTrust wrapper assumes the following:

-

- **Opt-In** and **Implied** statuses are treated in Segment's OneTrust wrapper as `Opt-In`. **Notice Only**, **Custom**, or **Opt-Out** statuses are treated in Segment's OneTrust wrapper as `Opt-Out`. -

-
-
+ +> info "Segment's Analytics.js OneTrust wrapper assumes the following" +> **Opt-In** and **Implied** statuses are treated in Segment's OneTrust wrapper as `Opt-In`. **Notice Only**, **Custom**, or **Opt-Out** statuses are treated in Segment's OneTrust wrapper as `Opt-Out`. @@ -69,10 +63,10 @@ To minimize the possibilities for data loss: | Banner behavior | Cookie banner | User interaction with webpage | Segment loads | Possibility of data loss | | --------------- | ------------ | ----------------------------- | ------------ | ---- | -| Mandatory | Displayed on page load | Required to access webpage | After user action | [Low](#low), until a user changes their preferences | -| A banner that always remains as a user navigates your site | Displayed on page load | Not required to access webpage | With page load | [Medium](#medium) | -| A banner that disappears after a user action, like clicking or scrolling | Displayed on page load | Not required to access webpage | With page load | [Medium](#medium) | -| A banner that is optional and never displayed to a user | Not displayed on page load | Not required to access webpage | With page load | [Low](#low), until a user changes their preferences | +| Mandatory | ![](/docs/images/supported.svg) Displayed on page load | ![](/docs/images/supported.svg) Required to access webpage | After user action | [Low](#low), until a user changes their preferences | +| A banner that always remains as a user navigates your site | ![](/docs/images/supported.svg) Displayed on page load | ![](/docs/images/unsupported.svg) Not required to access webpage | With page load | [Medium](#medium) | +| A banner that disappears after a user action, like clicking or scrolling | ![](/docs/images/supported.svg) Displayed on page load | ![](/docs/images/unsupported.svg) Not required to access webpage | With page load | [Medium](#medium) | +| A banner that is optional and never displayed to a user | ![](/docs/images/unsupported.svg) Not displayed on page load | ![](/docs/images/unsupported.svg) Not required to access webpage | With page load | [Low](#low), until a user changes their preferences | ## Scenarios where you might experience data loss @@ -200,4 +194,4 @@ The following table explains how Segment's OneTrust wrapper works with different | One or more categories are enabled | No unmapped destinations
**or**
All unmapped destinations are disabled | All destinations are disabled | No data flows to Segment | | One or more categories are enabled | No unmapped destinations
**or**
All unmapped destinations are disabled | One or more destinations are enabled | Data flows to Segment | | One or more categories are enabled | One or more destinations are enabled | All destinations are disabled | Data flows to Segment | -| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment | \ No newline at end of file +| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |