We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue is for adding GDPR support to the Prebid Server config. For an overview of GDPR support in Prebid Server, see #501
Prebid Server host companies must be able to:
We plan to add the following config options:
gdpr: host_vendor_id: 23 usersync_if_ambiguous: true
If these are undefined, we will assume that the publisher doesn't care about GDPR and continue to sync users all the time.
If defined:
host_vendor_id
usersync_if_ambiguous
gdpr
usersync_if_ambiguous is optional, and will be treated as false if host_vendor_id is defined.
false
See #504 for changes to the core logic in the endpoints.
The text was updated successfully, but these errors were encountered:
LGTM
Sorry, something went wrong.
dbemiller
No branches or pull requests
This issue is for adding GDPR support to the Prebid Server config. For an overview of GDPR support in Prebid Server, see #501
Requirements
Prebid Server host companies must be able to:
Working design
We plan to add the following config options:
If these are undefined, we will assume that the publisher doesn't care about GDPR and continue to sync users all the time.
If defined:
host_vendor_id
must be an integer > 0 which identifies the Prebid Server host company in the Global Vendors List.usersync_if_ambiguous
will determine whether or not usersyncs are done if the incoming request has nogdpr
info.usersync_if_ambiguous
is optional, and will be treated asfalse
ifhost_vendor_id
is defined.See #504 for changes to the core logic in the endpoints.
The text was updated successfully, but these errors were encountered: