Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add table of expected behavior to the OneTrust Consent wrapper page #7252

Merged
merged 3 commits into from
Dec 2, 2024
Merged

Add table of expected behavior to the OneTrust Consent wrapper page #7252

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3c1ae9a
add table
forstisabella Nov 21, 2024
9010521
[netlify-build]
forstisabella Nov 21, 2024
2b16598
respond to Atit's feedback [netlify-build]
forstisabella Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion src/privacy/consent-management/onetrust-wrapper.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,13 @@ title: Analytics.js OneTrust Wrapper
plan: consent-management
---

This guide about Segment's Analytics.js OneTrust wrapper contains context about which configurations might cause data loss, steps you can take to remediate data loss, and configurations that minimize data loss.
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.

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"}.

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.


## OneTrust consent banner behavior

The OneTrust consent banner has three key UI configurations that control how the banner and consent preferences behave:
Expand Down Expand Up @@ -185,3 +186,18 @@ You might experience data loss if a user navigates away from a landing page befo
</table>

<!-- TODO (IG, 4/2024): the above tables would not render ordered lists in a cell - figure out why this happened-->


## Expected wrapper behavior

The following table explains how Segment's OneTrust wrapper works with different configurations of consent categories and destination behaviors.

| Consent categories | Unmapped destinations | Mapped destinations | Wrapper behavior |
| ------------------ | --------------------- | ------------------- | ---------------- |
| All categories are disabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | Any configuration | No data flows to Segment |
| All categories are disabled | At least 1 enabled destination is not mapped to a consent category | Any configuration | Data flows to Segment |
| All categories are disabled | S3 destination is unmapped | Any configuration | Data flows to Segment |
| 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 |
| 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 |
| 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 |
Loading