After you did the upgrade to IAB TCF v2.0 we cannot decode the consent string anymore and it seems broken. Could you please look at this and report back if anything found. At least when we decode the string it converts to unreadable characters only.
Our SSP's are also seeing problems decoding the consent string to a readable object.
Please sign in to leave a comment.