Sourcepoint offers your organization additional commands that can be used for GDPR Standard web implementation. This provides a level of consistency and feature overlap between IAB TCF and Standard integrations.
The getVendorPurposeMapping command enables your organization to handle vendors participating in Standard campaigns.
getVendorPurposeMapping command
The command returns a JSON object that contains information on the purposes and corresponding legal basis attributed to each vendor and their legal basis. The format of the getVendorPurposeMapping command is as follows:
//Input into browser console to receive response
window._sp_.gdpr.getVendorPurposeMapping((data, success) => { console.log(data,success); });Your organization can use a third party service like Postman to retrieve the vendor url mapping. You will need to provide the correct API endpoint address and values for siteID.
https://sourcepoint.mgr.consensu.org/tcfv2/vendor-list/vendor-purpose-mapping?siteId=SITE_ID Note: The site_id value can be found by selecting a property from the Dialogue dashboard and navigating to the browser address bar. The site_id value will be shown in the browser address bar.
Your organization could use 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 site_id in the script.
Note: The site_id value can be found by selecting a property from the Dialogue dashboard and navigating to the browser address bar. The site_id value will be shown in the browser address bar.
<?php
$site_id = "XXXXX";
$api_endpoint = "https://sourcepoint.mgr.consensu.org/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);
?>getVendorPurposeMapping response
The response contains the consent data that maps the purposes and legal basis to the vendor.
Vendor mapping
The categories section lists the purpose ids for each vendor with their legal basis type.
| Parameter | Description |
_id |
Purpose ID |
type |
The legal basis set for this purpose - consent, legitimate interest, not allowed, disclosure only |
vendorId |
Vendor ID |
length |
Number of purposes attached to this vendor |
0:
categories:
0: {_id: "5ff4ca88f485275018dd8b9e", type: "CONSENT"}
1: {_id: "5ff4ca88f485275018dd8b99", type: "CONSENT"}
2: {_id: "5ff4ca88f485275018dd8ba3", type: "CONSENT"}
vendorId: "5e7ced57b8e05c47e418b73c"
length: 3
1:
categories:
0: {_id: "5ff4ca88f485275018dd8b9e", type: "CONSENT"}
1: {_id: "5ff4ca88f485275018dd8b99", type: "LEGITIMATE_INTEREST"}
2: {_id: "5ff4ca88f485275018dd8ba3", type: "CONSENT"}
vendorId: "5fd78083fc186126cb9fabad"
length: 3