Adding General Vendors to Vendor Lists

Using Cookie Consent, you can add General Vendors outside of the IAB Global Vendor Lists. General vendors enable you to add any vendor you wish to disclose to your OneTrust CMP.

Specifically, you can disclose vendors that may use tracking technologies other than cookies to your users. Users can then configure their preferences regardless of what tracking technology (e.g., pixels, web beacons) the vendor deploys.

You can also use general vendors to disclose third-party vendors alongside all the services and technologies they deploy on your site.

To add a general vendor

  1. On the Cookie Consent menu, select Vendors.

    The Vendor List screen appears.

  2. Click the Add General Vendor button.

    The General Information tab appears.

  3. Complete the fields.


  4. Click the Next button.

    The Apply to Websites page appears.

  5. Select the websites to which the vendor applies.


  6. Click the Next button.

    The Apply to Apps screen appears.

  7. Select the apps to which the vendor applies.
    Note:

    Only applicable to users of Mobile & CTV/OTT App Consent.

  8. Click the Next button.

    The Regions screen appears.

  9. Select the regions in which the vendor is active.


  10. Click the Next button.

    The Select Categories screen appears.

  11. Select the categories and purposes that apply to the vendor.


  12. Click the Next button.

    The Cookies and Hosts screen appears.

  13. Select the cookies and hosts used by the vendor (optional). You can edit cookies and hosts after the vendor is created.


  14. Click the Next button.

    The SDKs screen appears.

  15. Select SDKs used by the vendor (optional). You can edit SDKs after the vendor is created.
    Note:

    Only applicable to users of Mobile & CTV/OTT App Consent.

  16. Click the Add Vendor button.

To display General Vendors on the Preference Center

  1. On the Cookie Consent menu, select Templates. The Templates list screen appears.

  2. Select the Template for which you want to enable General Vendors. The Template Details screen appears.

  3. Go to the Preference Center tab.
  4. Click the Expand icon next to the Content section.
  5. Click the Edit icon next to Vendor List. The Vendor List modal appears.

  6. Enable the Show General Vendors setting.


  7. Configure the fields. For more information, see Customizing the Preference Center Template.
  8. Click the Save button.
  9. Click the Save Template button on the Template Details screen.

General Vendors will display in the Vendor List on your Preference Center upon republication of the corresponding scripts. For more information, see Publishing and Implementing Cookie Consent Scripts.

Managing Consent Outside of the IAB Global Framework

You can add vendors that are not part of the IAB Global Framework to the General Vendors list in Cookie Consent. General vendors can read users' consent on the page provided by the consent management platform and update if they are active or inactive on the page.

Vendors read users' consent by (1) reading the OnetrustActiveGroups data layer variable or (2) the OptanonConsent cookie, which is set by the OTSDKstub.js file on the page.

Option 1: OnetrustActiveGroups

  • If OnetrustActiveGroups exists and contains the vendor ID, the vendor can be active on the page.

    Note:

    It is the site owner's responsibility to communicate to vendors what their vendor ID is and how to read the OnetrustActiveGroups data layer variable.

  • If OnetrustActiveGroups does not exist or does not contain the vendor ID, then the vendor is not able to be active on the page.

    Note:

    It is the site owner's responsibility to communicate to vendors what their vendor ID is and how to read the OnetrustActiveGroups data layer variable.

Option 2: OptanonConsent

In addition to the OneTrustActiveGroups data layer variable, the OTSDKstub.js file also sets the first party cookie, OptanonConsent, to capture user consent. When decoding the value of the OptanonConsent cookie as a string URI component, the current consent can be read.

Original string:

CODE 
consentId=e1e8d9f0-4677-4212-856a-9009ea15f55b&datestamp=Tue+Jul+30+2024+17%3A01%3A07+GMT-0400+(Eastern+Daylight+Time)&version=202407.1.0&interactionCount=0&isAnonUser=1&isGpcEnabled=0&browserGpcFlag=0&isIABGlobal=false&hosts=&genVendors=V16%3A0%2CV20%3A0%2C&landingPath=https%3A%2F%2Fexample.com%Example%2FUser%2FOneTrust%2520-%2520Test%2Fexample.html&groups=C0001%3A1%2CC0004%3A1%2CC0002%3A1%2CC0003%3A1%2CC0007%3A1

Decoded string:

CODE 
consentId=e1e8d9f0-4677-4212-856a-9009ea15f55b&datestamp=Tue+Jul+30+2024+17:01:07+GMT-0400+(Eastern+Daylight+Time)&version=202407.1.0&interactionCount=0&isAnonUser=1&isGpcEnabled=0&browserGpcFlag=0&isIABGlobal=false&hosts=&genVendors=V16:0,V20:0,&landingPath=https://example.com/test/user/OneTrust%20-%20Testing/test.html&groups=C0001:1,C0004:1,C0002:1,C0003:1,C0007:1
Note:

The value after the colon next to a cookie category ID or vendor ID indicates if a user has consented (i.e,. 1 = consented to, 0 = not consented to). As such, the vendor can read the OptanonConsent cookie to determine if their vendor ID has been consented to and is therefore active or inactive on the page. It is the vendor's responsibility to read the consent and determine if they can be active or inactive on the page.