-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
add support for non-purpose1 consent domains to appnexus and PBS bid adapters #6484
Merged
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
ec640c6
add support for non-purpose1 consent domains
jsnellbaker 401c0f3
fix logic and consentdata to clientSideSyncs
jsnellbaker 22b701a
Merge branch 'master' into appnexus-simple-domain-support
jsnellbaker 95b913d
update openx vendor config
jsnellbaker File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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
Oops, something went wrong.
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.
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.
@jsnellbaker This looks good. One question on this piece though. Should this work the same for both client and s2s. It seems to me that the PBS Bid Adapter runs doClientSideSyncs() which in turn calls registerSyncs([]) not passing in any GDPR data when GDPR exists on the bidderRequests. I just want to understand if this is expected or not. The reason being that testing the s2s, the following always returns true since the gdprConsent value is undefined and therefore, the sync iframe runs.
if (syncOptions.iframeEnabled && hasPurpose1Consent({gdprConsent}))
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.
@mmoschovas Thanks for raising this concern.
I did some digging and found that the behavior within the
doClientSideSyncs
function wasn't properly working with the gdprEnforcement module. It was consistently returning this warning:WARNING: User sync not allowed for null
because we were not properly permitting the bidder to run this code within the special control logic that was added to thesrc/config.js
(seerunWithBidder
).I'm about to push a commit that should address the lack of consent data on this registerSync call and grant the permissions. Please take a look
CC @snapwich to take a look at the change, to ensure it's formatted properly with the config bidder permission logic (which I believe he helped design).
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.
@jsnellbaker your update looks good and it does look like the server -> client syncs call not passing consent data was an oversight (possibly was added before we had standardized on the user sync call). good callout @mmoschovas