Important GDPR Changes
The gdpr.usersync_if_ambiguous config option has been removed in this release. We heard your feedback that this was confusing and that the default value causes side affects which are hard to identify, especially during development. In its place, we've added a gdpr.default_value string config which Prebid Server uses if regs.ext.gdpr is absent from the request. There is no default value. Prebid Server will not start until this value is configured as either "0" or "1".
This release also removes support for TCF1 consent strings. The IAB deprecated TCF1 last year and has since taken down the TCF1 Global Vendor Lists. TCF1 consent strings will now be treated by Prebid Server as invalid TCF2 consent strings.
Changes
- Pubmatic: Sending GPT slotname in impression extension (#1880)
- Fix a weak vendor enforcement bug where vendor does not exist (#1890)
- New Adapter: Smile Wanted (#1877)
- GDPR: require host specify default value (#1859)
- Sovrn: Accept bidfloor from impression to fix issue #1787 (#1886)
- Rename GDPR UserSyncIfAmbiguous to DefaultValue (#1858)
- Remove GDPR TCF1 (#1854)
Contributors
@MaxSmileWanted, @bsardo, @hhhjort, @rachelrj and @sachin-pubmatic