Flip usersync_if_ambiguous Default #1786
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This proposed change would introduce too much risk in GDPR enforcement. I'll discuss further options on the linked issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses: #1783
The
usersync_if_ambiguousforces TCF enforcement on any bid request this doesn't explicitly set theregs.ext.gdprfield. This is not a good default and has caused several complaints. Setting this totrueis a better default value which only enforces TCF if the bid request includesregs.ext.gdprset to1.We'll follow-up with a separate PR to rename the
usersync_if_ambiguousconfig value to something more descriptive, as it controls much more than user sync.