Load Cookie With Consent #123
Merged
Conversation
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
…html. This will load the cookieSyncWithConsent.js script which will postMessage the parent window for GDPR consent data.
|
Thanks @mmoschovas . For the record, this is the code for #114 |
|
I'll take a cut at the docs. |
Fawke
requested changes
Oct 20, 2020
| return value; | ||
| } | ||
|
|
||
| /** |
There was a problem hiding this comment.
The comment and the code doesn't add up.
|
docs PR prebid/prebid.github.io#2456 |
harpere
approved these changes
Nov 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Created alternate to load-cookie.html named load-cookie-with-consent.html. This will load the new cookieSyncWithConsent.js script which will postMessage the parent window for GDPR consent data. If data is returned before the timeout, the data is parsed to retrieve the gdprApplies and consentString values, which are then set in the data of the Prebid Server request. If the timeout expires prior to data returning, the defaultGdprScope setting will determine if the user sync should still run or not. The below fields can be passed in the load-cookie-with-consent.html URL string.
defaultGdprScope : accepted values 0 or 1, default 1
timeout : integer, default 10000
i.e. The below example would set the timeout to 500ms and allow sync if timeout is reached and GDPR data is not returned
...load-cookie-with-consent.html?max_sync_count=5&timeout=500&defaultGdprScope=0