Skip to main content

Update to IAB TCF v2.0

Comments

4 comments

  • Jacob Buch

    Hi Martin, 

    It sounds like you are using a IAB TCF version 1 decoder to decode a version 2 consent string. Please note that the two versions are not compatible by design. Please check your consent string here to make sure that it is a valid version 2 string: https://iabtcf.com/#/decode

    Also, please confirm that your SSP's have migrated to version 2, thanks.

    0
  • Martin Hjorth Christensen

    Hi,

    Thanks for the quick response and now see content data making sense, thanks. Will notify our SSP's.

    0
  • Jacob Buch

    Martin, we have today released an update that allow publishers to continue to use version 1.1 of IAB TCF if necessary, please check out the details here: https://support.cookiebot.com/hc/en-us/articles/360007652694-Cookiebot-and-the-IAB-Consent-Framework

    0
  • Martin Hjorth Christensen

    Thanks Jacob,

    Seems like a lot of SSP's weren't ready for this, so much appreciated. I have forwarded this to our programmatic if we should make use of this change, so they have at least to the 30th of June to fix it.

    0

Please sign in to leave a comment.