-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: Enable GPP Multi-State Privacy String (MSPS) with U.S. Privacy #806
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tricksy! Looks good to me.
🦋 Changeset detectedLatest commit: e13a188 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Coverage report
Test suite run success328 tests passing in 16 suites. Report generated by 🧪jest coverage report action from e13a188 |
🚀 0.0.0-beta-20240111123721 published to npm as a beta release |
🚀 0.0.0-beta-20240115103106 published to npm as a beta release |
🚀 0.0.0-beta-20240115104820 published to npm as a beta release |
🚀 0.0.0-beta-20240116101956 published to npm as a beta release |
🚀 0.0.0-beta-20240119094923 published to npm as a beta release |
src/types/window.d.ts
Outdated
@@ -97,5 +98,9 @@ declare global { | |||
callback: (tcData: TCData, success: boolean) => void, | |||
vendorIDs?: number[], | |||
) => void; | |||
__gpp?: ( | |||
command: string, | |||
callback: (gppData: any, success: boolean) => void, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be an 'any' type?
🚀 0.0.0-beta-20240126154929 published to npm as a beta release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We did some extra testing of the resulting GPP string and that the Privacy Manager appears, it's looking good! 🎉
What does this change?
IAB is deprecating US privacy string - at the end of September and moving to the multi-state privacy agreement.
Google has said they will continue to support US Privacy String so not all vendors have signed up to use or accept the multi-state privacy string and have said they will continue to use the US privacy string.
To ensure full monetisation:
SP have a back up solution, Combination of the two (GPP and US Privacy String), so we will still be able to monetise those vendors for both frameworks
We need to implement BOTH:
MSPS (Multi-State Privacy String; GPP, Global Privacy Platform)
&
US privacy string (Current, soon to be legacy but still being supported)
https://trello.com/c/6qAHXGHq
https://docs.sourcepoint.com/hc/en-us/articles/18007731422099-Enable-GPP-Multi-State-Privacy-String-MSPS-with-U-S-Privacy-CCPA-solution
Why?
Sourcepoint recommended change