In this article, we will cover the multiple ways your organization can request a mapping of vendors and their configured purposes for a particular property using GDPR Standard.
getVendorPurposeMapping command
The getVendorPurposeMapping command returns an array that contains information of each vendor, the purposes that are applicable to that vendor, and the legal basis used for the applicable purposes.
This provides a level of consistency and feature overlap between IAB TCF and Standard integrations. Your organization can call the command through the browser console.
Enter the following command directly into the browser tools' console window.
window._sp_.gdpr.getVendorPurposeMapping((data, success) => { console.log(data,success); });API endpoint
API requests from a tool like Postman or a server-side script to retrieve the vendor and purpose mapping for a specific property can be made to:
GET https://cdn.privacy-mgmt.com/consent/tcfv2/vendor-list/vendor-purpose-mappingQuery string parameters
| Parameter | Required | Description |
siteId |
true |
The site ID value is the same as the Property ID on the property for which you are making the request. It can be found on the Properties page inline with the property name. |
GET https://cdn.privacy-mgmt.com/consent/tcfv2/vendor-list/vendor-purpose-mapping?siteId=123456If your organization is a using a server-side script using code similar to the following PHP example to retrieve the vendor purpose mapping, you will need to provide the correct values for the site_id with the API endpoint.
<?php
$site_id = "XXXXX";
$api_endpoint = "https://cdn.privacy-mgmt.com/consent/tcfv2/vendor-list/vendor-purpose-mapping?siteId=".$site_id;
$handle = curl_init($api_endpoint);
$fileHandle = fopen("vendor_purpose_mapping.json", "w");
/* If you encounter an 'SSL certificate problem: unable to get local issuer certificate' then enable the following two lines */
/* This is NOT recommended as a solution and should only be used as a quick and temporary fix */
//curl_setopt($handle, CURLOPT_SSL_VERIFYHOST, 0);
//curl_setopt($handle, CURLOPT_SSL_VERIFYPEER, 0);
curl_setopt($handle, CURLOPT_FILE, $fileHandle);
curl_exec($handle);
curl_close($handle);
fclose($fileHandle);
?>Response
The response is a mapping of vendors and their configured purposes on the vendor list associated with the property.
Note: For each vendor, the response will only include purposes that have a configured legal basis (Consent, Legitimate Interest, Disclosure Only). Any purposes that are Not Applicable will not be returned in the response.
Additionally, vendors will need at least one purpose with a configured legal basis to be returned in the response.
The model for each array element in the response is as follows:
| Attribute | Type | Description |
vendorId |
String | The unique ID for a vendor on the vendor list associated with the property |
categories |
Array | An array of objects that detail the purposes configured for each vendor on the vendor list associated with the property. |
categories
Each categories array element is an object that lists the purpose ids and their corresponding consent type for a particular vendor. The model for each object is as follows:
| Key | Type | Value |
id |
String | The unique ID for a vendor on the vendor list associated with the property |
type |
String | The legal basis configured for the purpose. |
[
{
"vendorId": "5ea2d4894e5aa15059fde8a0",
"categories": [
{
"_id": "63ee7c5234a29806e1952c64",
"type": "CONSENT"
},
{
"_id": "63ee7c5234a29806e1952c6b",
"type": "CONSENT"
},
{
"_id": "63ee7c5234a29806e1952c72",
"type": "DISCLOSURE_ONLY"
}
]
},
{
"vendorId": "637be8a3a6865c0526b55e45",
"categories": [
{
"_id": "63ee7c5234a29806e1952c64",
"type": "CONSENT"
},
{
"_id": "63ee7c5234a29806e1952c6b",
"type": "LEGITIMATE_INTEREST"
}
]
}
]