-
Notifications
You must be signed in to change notification settings - Fork 95
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
Saving Vendor Id 126 for Double Verify doesn't save into TC Consent string #427
Comments
Hi, I also tried it with version 1.4.0 and it does the same thing, so I think it's something (I don't know if it's an actual bug) that has been around for a long time. I see that the vendor doesn't have any purposes but only legInt purposes, maybe that is the problem? |
Hello! We are also struggling with this issue. Same thing happens when you are trying to accept for example "Mirando" ID: 279. Any updates about planned fixes? |
If there is no purpose to consent specified for a vendor that vendor cannot be written out as having consent. If the vendor specifies LegInt for purposes, the vendor can continue operating for the declared purposes under LegInt unless the user opted out of LegInt. If the vendor specifies FlexPurposes that will allow the publisher through the CMP to override the purpose declaration and if in this case the purpose(s) is/are set to consent, the vendor bit will be written for consent if consent is given. the library handles publisher overrides, hence you can mimic this behavior through library calls. |
Version
1.5.9
Module (core, cmpapi, cli, stub, or testing)
core
Describe with reproduction steps – What is the expected behavior?
Currently trying to save vendor 126 Double Verify into TC String using the encode functionality. The encode functionality doesn't directly save 126 into the cookie.
This is the output I got from the decoder:
And the encoded TC String:
CPywmUAPywmUADgACMENAYEgAAAAAAAAAAAAAZQAwAQAAqABkAAAAAAA.YAAAAAAAAAAA
The text was updated successfully, but these errors were encountered: