-
Notifications
You must be signed in to change notification settings - Fork 367
OneTrust wrapper doc [DOC-895] #6455
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.
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
Conversation
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor suggestions, other than that LGTM.
|
||
#### Low | ||
|
||
Segment assess some behaviors to have a low possibility of data loss because Twilio Segment Analytics.js and third-party device mode libraries are loaded only after the user has provided their consent (for consent banners a user **must** interact with to use your site) or your site assumes that a user consents (if you set your cookie banner on your site to be optional and never displayed to a user). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could be reading this wrong, but did you mean "Segment assessed" or "Segment assesses"?
|
||
#### Medium | ||
|
||
Segment assess some banner behaviors, like those that always remain as a user navigates your site and those that disappear after a user action like clicking or scrolling, to be at a medium possibility for data loss and noncompliance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, re: "assess."
Co-authored-by: pwseg <[email protected]>
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
Added a page to the Consent Management docs set about the configurations of the a.js OneTrust wrapper that aren't supported and might lead to data loss
Merge timing
Thursday, May 2
Related issues (optional)
#6106