Skip to content

Commit 2b16598

Browse files
committed
respond to Atit's feedback [netlify-build]
1 parent 9010521 commit 2b16598

File tree

1 file changed

+16
-15
lines changed

1 file changed

+16
-15
lines changed

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

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -3,26 +3,12 @@ title: Analytics.js OneTrust Wrapper
33
plan: consent-management
44
---
55

6-
This guide to Segment's Analytics.js OneTrust wrapper contains expected wrapper behavior, context about which configurations might cause data loss, steps you can take to remediate data loss, and configurations that minimize data loss.
6+
This guide to Segment's Analytics.js OneTrust wrapper contains context about which configurations might cause data loss, steps you can take to remediate data loss, configurations that minimize data loss, and a guide to expected wrapper behavior.
77

88
For questions about OneTrust Consent and Preference Management behavior, see the [OneTrust documentation](https://my.onetrust.com/s/topic/0TO3q000000kIWOGA2/universal-consent-preference-management?language=en_US){:target="_blank"}.
99

1010
For questions about the Analytics.js OneTrust wrapper, see the [@segment/analytics-consent-wrapper-onetrust](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-wrapper-onetrust){:target="_blank"} repository.
1111

12-
## Expected wrapper behavior
13-
14-
The following table explains how Segment's OneTrust wrapper works with different configurations of consent categories and destination behaviors.
15-
16-
| Consent categories | Unmapped destinations | Mapped destinations | Wrapper behavior |
17-
| ------------------ | --------------------- | ------------------- | ---------------- |
18-
| All categories are disabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | Any configuration | No data flows to Segment |
19-
| All categories are disabled | At least 1 enabled destination is not mapped to a consent category | Any configuration | Data flows to Segment |
20-
| All categories are disabled | S3 destination is unmapped | Any configuration | Data flows to Segment |
21-
| 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 |
22-
| 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 |
23-
| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |
24-
| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |
25-
2612

2713
## OneTrust consent banner behavior
2814

@@ -200,3 +186,18 @@ You might experience data loss if a user navigates away from a landing page befo
200186
</table>
201187

202188
<!-- TODO (IG, 4/2024): the above tables would not render ordered lists in a cell - figure out why this happened-->
189+
190+
191+
## Expected wrapper behavior
192+
193+
The following table explains how Segment's OneTrust wrapper works with different configurations of consent categories and destination behaviors.
194+
195+
| Consent categories | Unmapped destinations | Mapped destinations | Wrapper behavior |
196+
| ------------------ | --------------------- | ------------------- | ---------------- |
197+
| All categories are disabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | Any configuration | No data flows to Segment |
198+
| All categories are disabled | At least 1 enabled destination is not mapped to a consent category | Any configuration | Data flows to Segment |
199+
| All categories are disabled | S3 destination is unmapped | Any configuration | Data flows to Segment |
200+
| 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 |
201+
| 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 |
202+
| 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 |

0 commit comments

Comments
 (0)