Skip to content

Commit 8a9ab8e

Browse files
authored
Merge pull request #8006 from segmentio/DOCSPLAT-2878-P4
DOCSPLAT 2878 PT4 Replace with info box
2 parents 592248c + 2cb131a commit 8a9ab8e

File tree

1 file changed

+8
-14
lines changed

1 file changed

+8
-14
lines changed

src/privacy/consent-management/onetrust-wrapper.md

Lines changed: 8 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,9 @@ The OneTrust consent banner has three key UI configurations that control how the
2020
- **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)
2121
- **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)
2222

23-
<div class="premonition info">
24-
<div class="fa fa-info-circle"></div>
25-
<div class="content">
26-
<p class="header">Segment's Analytics.js OneTrust wrapper assumes the following:</p>
27-
<p markdown=1>
28-
**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`.
29-
</p>
30-
</div>
31-
</div>
23+
24+
> info "Segment's Analytics.js OneTrust wrapper assumes the following"
25+
> **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`.
3226
3327
<!-- TODO (IG, 4/2024): the above callout would not render correctly in markdown - figure out why that happened-->
3428

@@ -69,10 +63,10 @@ To minimize the possibilities for data loss:
6963

7064
| Banner behavior | Cookie banner | User interaction with webpage | Segment loads | Possibility of data loss |
7165
| --------------- | ------------ | ----------------------------- | ------------ | ---- |
72-
| Mandatory | <img class="inline" src="/docs/images/supported.svg" /> Displayed on page load | <img class="inline" src="/docs/images/supported.svg" /> Required to access webpage | After user action | [Low](#low), until a user changes their preferences |
73-
| A banner that always remains as a user navigates your site | <img class="inline" src="/docs/images/supported.svg" /> Displayed on page load | <img class="inline" src="/docs/images/unsupported.svg" /> Not required to access webpage | With page load | [Medium](#medium) |
74-
| A banner that disappears after a user action, like clicking or scrolling | <img class="inline" src="/docs/images/supported.svg" /> Displayed on page load | <img class="inline" src="/docs/images/unsupported.svg" /> Not required to access webpage | With page load | [Medium](#medium) |
75-
| A banner that is optional and never displayed to a user | <img class="inline" src="/docs/images/unsupported.svg" /> Not displayed on page load | <img class="inline" src="/docs/images/unsupported.svg" /> Not required to access webpage | With page load | [Low](#low), until a user changes their preferences |
66+
| Mandatory | &#x2705; Displayed on page load | &#x2705;Required to access webpage | After user action | [Low](#low), until a user changes their preferences |
67+
| A banner that always remains as a user navigates your site | !&#x2705; Displayed on page load | &#x1F6AB; Not required to access webpage | With page load | [Medium](#medium) |
68+
| A banner that disappears after a user action, like clicking or scrolling | &#x2705;Displayed on page load | &#x1F6AB; Not required to access webpage | With page load | [Medium](#medium) |
69+
| A banner that is optional and never displayed to a user | &#x1F6AB; Not displayed on page load | &#x1F6AB; Not required to access webpage | With page load | [Low](#low), until a user changes their preferences |
7670

7771
## Scenarios where you might experience data loss
7872

@@ -200,4 +194,4 @@ The following table explains how Segment's OneTrust wrapper works with different
200194
| One or more categories are enabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | All destinations are disabled | No data flows to Segment |
201195
| One or more categories are enabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | One or more destinations are enabled | Data flows to Segment |
202196
| One or more categories are enabled | One or more destinations are enabled | All destinations are disabled | Data flows to Segment |
203-
| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |
197+
| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |

0 commit comments

Comments
 (0)