Skip to content

Commit a59e965

Browse files
committed
[netlify-build]
1 parent f2f3dd7 commit a59e965

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/privacy/consent-management/consent-in-unify.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ A device-level conflict occurs when conflicting consent preferences linked to on
6666
6767
For example, if an end-user didn’t consent to Advertising on their mobile phone, but later consented to Advertising on their desktop computer, this user would have a conflicting consent preference for the `advertising` category.
6868

69-
By default, Segment relies on the latest consent preferences collected for a user, so would set the `advertising` category to `true` given that the **latest** consent preference collected (from the desktop computer) consented to the `advertising` category.
69+
By default, Segment relies on the latest consent preferences collected for a user and would set the `advertising` category to `true` given that the **latest** consent preference collected (from the desktop computer) consented to the `advertising` category.
7070

7171
If you would like to use a different method of conflict resolution, you must build an approach to address and resolve conflicting consent preferences in your website or mobile app and then send the updated consent back to Segment.
7272

0 commit comments

Comments
 (0)