InteractiveAdvertisingBureau / GDPR-Transparency-and-Consent-Framework

Technical specifications for IAB Europe Transparency and Consent Framework that will help the digital advertising industry interpret and comply with EU rules on data protection and privacy - notably the General Data Protection Regulation (GDPR) that comes into effect on May 25, 2018.
855 stars 359 forks source link

Undocumented methods #350

Closed rforster-dev closed 9 months ago

rforster-dev commented 9 months ago

We work with SourcePoint and have been adding custom vendors. Using this documented:

__tcfapi('addEventListener', 2, (tcdata, success) => { console.log(tcdata) })

Returns the list of IAB vendors and their status under vendor.consents and if they are <true/false> but not the custom vendors added.

But using say:

function customVendors(data, success) {
    console.log(data, success)
}

// call the __tcfapi() function with callback only
__tcfapi('getCustomVendorConsents', 2, customVendors);

Does return the custom vendors can this be added to the documentation? Are there other methods that are not mentioned in the docs?

Thanks!

jawadst commented 9 months ago

This is a SourcePoint-specific implementation and is not part of the TCF specification and is probably not supported by other CMPs

rforster-dev commented 9 months ago

Ah I see, my apologies.

I suppose then there is no scope for this kinda functionality to be part of IABTCF is there?

If not, i'll close this :).

jawadst commented 9 months ago

No worries, I just wanted to add some context as I received a notification for your message :)

I'll let somebody from the IAB EU/Tech Lab chime in on whether they want to consider adding support for other features like custom vendors via the __tcfapi function.

HeinzBaumann commented 9 months ago

This is a custom function that vendor can already add to the tcf api.