Skip to content
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

GDPR cookie sync configuration #503

Closed
dbemiller opened this issue May 10, 2018 · 1 comment
Closed

GDPR cookie sync configuration #503

dbemiller opened this issue May 10, 2018 · 1 comment
Assignees

Comments

@dbemiller
Copy link
Contributor

dbemiller commented May 10, 2018

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:

  1. Identify themselves as one of the members of the global vendors list
  2. Define how Prebid Server should behave if the Request doesn't carry any GDPR info in it.

Working design

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 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 no gdpr info.

usersync_if_ambiguous is optional, and will be treated as false if host_vendor_id is defined.

See #504 for changes to the core logic in the endpoints.

@dbemiller dbemiller changed the title GDPR cookie sync support GDPR cookie sync configuration May 10, 2018
@bretg
Copy link
Contributor

bretg commented May 10, 2018

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants