NonPersonalizedAds - Missing network extra to toggle npa parameter #131
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR that aims to fix the following issue.
We are missing a key property in the network parameters that is npa.
This property allows us to toggle whether we want to request personalized ads for the current user.
Whenever from our custom CMP SDK (For example OneTrust) we detect that the user has changed our permission to track his data through advertisement, we need to properly tell ad manager to avoid serving personalized ads. Otherwise we are not compliant, especially in Europe, under GDPR.
Here you can find sources: