https://iabgpp.com out of date?

[nicolas-raoul]

Hi all,

Would you mind clarifying whether https://iabgpp.com is considered as up-to-date?
If yes, should we report bugs on the present issue tracker?
If no, maybe better disable it or at least add a warning banner? Some companies are using it and getting into issues.

Thanks!

[nicolas-raoul]

Details:

• IAB Europe TCF strings generated by that tool mislead publishers, as they use a global scope, which is invalid under the TCF policy version used.
• The Allowed Vendors segment and the Disclosed Vendors segment must be removed, and the Core segment's isServiceSpecific flag must not be set to false.
• The tool should probably not even include an IAB Europe TCF 2.x string, as those won't be handled through GPP.

[cchigurupati]

@iabmayank : Please kindly take a look at this issue.

Thank you.

[nicolas-raoul]

Hi @IABTechLab,

Did you get a chance to look into this?
You could help CMP developers greatly by either fixing the tool or clearly deprecating it.

Thanks for your consideration!

[HeinzBaumann]

Currently the IAB EU TCF is not supported under GPP. You have to write a standalone TCF 2.2 string to be compliant.

[ram-securiti-ai]

@HeinzBaumann Thank you for your response.

I believe @nicolas-raoul is referring to the TCF 2.2 string itself; but the iabgpp.com or iabtcf.com decoders/encoders are not raising any warning or error when decoding a TCF 2.2 string which contains the deprecated fields like Allowed Vendors, Disclosed Vendors, isServiceSpecific flag must not be set to false.

Can we expect any fix from the IAB end for this decoder tools so that the deprecated/incorrect fields are validated and reported in their UI accordingly.