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.

Sign up for GitHub

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

Jump to bottom

Controlling GDPR behavior for AMP #1323

Closed
bretg opened this issue Jun 1, 2020 · 2 comments
Closed

Controlling GDPR behavior for AMP #1323

bretg opened this issue Jun 1, 2020 · 2 comments
Labels
Intent to implement An issue describing a plan for a major feature. These are intended for community feedback PBS-Go

Comments

@bretg
Copy link
Contributor

bretg commented Jun 1, 2020 •
edited
Loading

We discussed in the Prebid Server committee that publishers sometimes implement GDPR differently for AMP and Web due to differences in the CMPs available. The request has come up to enable accounts to turn off GDPR enforcement at the integration type level: AMP/Web/App.

The TCF2 requirements at https://docs.google.com/document/d/1fBRaodKifv1pYsWY3ia-9K96VHUjd8kKvxZlOsozm8E/edit# have been updated with proposed config. See requirement 21 in the Prebid Server section.

The proposed account config is:

  • account.A.gdpr.integration_enabled.amp: true/false // default to account.A.gdpr.enabled
  • account.A.gdpr.integration_enabled.app: true/false // default to account.A.gdpr.enabled
  • account.A.gdpr.integration_enabled.web: true/false // default to account.A.gdpr.enabled
  • account.A.gdpr.integration_enabled.video: true/false // default to account.A.gdpr.enabled

We don't believe there's a need to control the integration behavior at the purpose level.

Notes:

  • /cookie_sync and /setuid are not separately controllable -- they're used across all of the integration types, so depend only on the status of account.A.gdpr.enabled.
  • there's no cross-account mechanism for turning off GDPR enforcement for one integration type. This is purely a per-account control.
  • if account.A.gdpr.enabled is not defined, then the host-level gdpr.enabled is used as a default for integration_enabled

This is related to Issue #1312
@bretg bretg added the Intent to implement An issue describing a plan for a major feature. These are intended for community feedback label Jun 1, 2020
@SyntaxNode SyntaxNode mentioned this issue Jun 6, 2020
Closed
@bsardo bsardo mentioned this issue Aug 14, 2020
Merged
@bretg bretg added the PBS-Go label Sep 25, 2020
@bretg
Copy link
Contributor Author

bretg commented Sep 25, 2020

This feature is in PBS-Java 1.41

This was referenced Nov 3, 2020
Merged
Merged
@SyntaxNode
Copy link
Contributor

This is implemented in PBS-Go 0.137.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Intent to implement An issue describing a plan for a major feature. These are intended for community feedback PBS-Go
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SyntaxNode @bretg