Inconsistency between CoreTC and PublisherTC

Comments

7 comments

  • Hi John Fax,

    The Cookiebot's core consent framework collects 'blanket' consent for all vendors that are not part of IAB TCF 2 or Google's Ad Tech Providers (Additional Consent Mode). This is the case with FreeWheel MRM and SFX, since Cookiebot do not support the use of Publisher specific purposes (Publisher TC Segments) under TCF 2.
    This is why the PublisherTC section of the TCF consent string is only a 'placeholder'. Any Vendor not included in TCF/AC should instead rely on the client side boolean value of Cookiebot.consent.marketing to determine if the user has opt'ed in.

    Regards,
    Spas

    0
    Comment actions Permalink
  • Avatar
    John Fax

    Hi Spas,

    i'm sorry for the delay but i was waiting for a response from Freewheel.
    They say this:

    We are part of IAB TCF v2, our Global Vendor List ID is 285. Cookiebot should be able to use Publisher TC Segments.

    I looked up on google and the id 285 belongs to "Comcast International France SAS":
    https://iabeurope.eu/vendor-list-tcf-v2-0/
    and Freewheel is a Comcast company (https://www.freewheel.com/privacy-policy)

    So Freewheel is in fact part of the IAB TCF 2; is it possible for Cookiebot to update it's vendor list so we can pass a correct consent string to freewheel?

    Tank you again

    0
    Comment actions Permalink
  • Hi John Fax,

    Cookiebot does include Freewheel vendor with id 285 in the list of IAB vendors. Cookiebot's IAB TCF 2.0-integration by default includes Comcast/Freewheel on the partner list in the cookie banner. 
    See screenshot taken from Cookiebot's demo site on https://cookiebot-demo.azurewebsites.net/

    However, you can read out more about consent vendor as described in the last section "For IAB Vendors" in the help center article https://support.cookiebot.com/hc/en-us/articles/360007652694-Cookiebot-and-the-IAB-Consent-Framework
    Please do not hesitate to write us back in case of any further questions.

    Regards,
    Spas

    0
    Comment actions Permalink
  • Avatar
    John Fax

    Hi Spas,

    on our website we include the cookiebot js with the `data-framework="IAB"` parameter.  
    Then we call `__tcfapi('getTCData', 2, function(tcData, success) {.....})` to retrieve the consent string for the user.  
    We then call a freewheel url, passing the consentstring from cookiebot as a get parameter.  

    Is this the correct flow? How can we solve the problem freewheel is reporting to us?  

    Thanks again  

    0
    Comment actions Permalink
  • Hi John Fax,

    Yes, this is the correct flow.
    The vendor can read out the user's consent state from the tcData object and string when Cookiebot is loaded and exposes the stub function "__tcfapi" as you mentioned above `__tcfapi('getTCData', 2, function(tcData, success) {.....})`

    You can also add a callback function to an event listener or modify the stub function. You can find more detailed information here: https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/IAB%20Tech%20Lab%20-%20CMP%20API%20v2.md#how-does-the-cmp-provide-the-api

    Regards,
    Spas

    0
    Comment actions Permalink
  • Avatar
    John Fax

    Hi Spas,

    ok, so we can retrieve the tcData object and get the TC String.
    The issue though is that Freewheel doesn't want a placeholder/blanket for the PublisherTC section of the string (the "YAAAAAAAAAAA"). Cookiebot gave us that placeholder even if Freewheel is part of IAB TCF v2 (vendor id 285).

    How can we pass valid data to Freewheel?

    Thank you

    0
    Comment actions Permalink
  • Hi John Fax,

    You could check the value of the tcData object for that specific vendor, Freewheel with id 285 by using the stub function:

    __tcfapi('getTCData', 2, (tcData, success) => { if(success) { if (tcData.vendor.consents[285]) { console.log("Vendor 285 has consent") } else { console.log("Vendor 285 has NO consent")}}});

    However, Cookiebot does not support PublisherTC.

    Regards,
    Spas

    0
    Comment actions Permalink

Please sign in to leave a comment.