Skip to content

Add info about profile-level conflicts in Unify to Consent in Unify docs [DOC-751] #5724

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

Closed
wants to merge 5 commits into from
Closed

Add info about profile-level conflicts in Unify to Consent in Unify docs [DOC-751] #5724

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9099494
init draft
forstisabella Nov 22, 2023
75e1f1a
[netlify-build]
forstisabella Nov 22, 2023
06b4bdb
fix formatting error [netlify-build]
forstisabella Nov 22, 2023
2cca1f5
[netlify-build]
forstisabella Nov 22, 2023
183ba23
comma fix [netlify-build]
forstisabella Nov 22, 2023
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
21 changes: 21 additions & 0 deletions src/privacy/consent-in-unify.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,24 @@ If you use Protocols, the Segment app automatically adds the Segment Consent Pre
> Segment has standardized a series of reserved event names that have special semantic meaning and maps these events to tools that support them.
>
> See the [Semantic Events](/docs/connections/spec/semantic/) docs for more details.

## Profile-level conflicts

You might encounter a profile with a consent value of `conflict` if one of your end users consents to different categories on different devices or if two distinct IDs are linked to one Unify profile.

### Device conflicts
A device conflict occurs when consent for one user ID is collected from two distinct devices. For example, if a user consented to all categories on their mobile phone, but consented only to essential categories on their desktop computer, their profile in [Unify](/docs/unify/) would have a consent value of `conflict`.

Device-level conflicts do not exist on the profile directly because they are always resolved by one of two strategies:

- **Latest Wins**: Segment sets the consent preferences to the most recent consent preferences collected from a user ID.
- **Resolve False**: Segment automatically sets consent to `false` if a consent conflict exists for a consent category.

<!-- TODO: fix this--->

You can select a device-level conflict resolution strategy by navigating to the `$fix_this` page and selecting **Latest Wins** or **Resolve False**.

### Profile conflicts
A profile-level conflict occurs when two distinct IDs with different consent preferences are linked to the same Unify profile. A profile-level conflict can also occur when a userID and an anonymousID (one without a linked userID) are linked to the same profile by an external ID, like an email address or phone number, and the consent preferences of both profiles do not match.

To avoid profile conflicts, Segment recommends that you configure your profiles to avoid sharing anonymous identifiers and limit the traits collected during anonymous browsing sessions.