Admin access or Domain access to property (property group) with feature access to vendor list management
The Krux/Salesforce DMP platform provides a JavaScript API to set consent for end-users. In this article, we will cover how your organization can utilize The Krux API within consent and reject action fields to generate consent for the end-user.
​Example Krux API Calls​
In this section, we provide your organization with an example for a Krux API call to use for a consent action and a reject action, respectively.
We strongly recommend reviewing the additional information on use cases and Krux namespaces here.
Krux('ns:mynamespace', 'consent:set', {dc: true,al: true,tg: true,cd: false,sh: false,re: false}, function(errors, body) {if (errors) {console.error(errors);} else {console.log('Successfully set consent flags.');}});
Krux('ns:mynamespace', 'consent:set', {dc: false,al: false,tg: false,cd: false,sh: false,re: false}, function(errors, body) {if (errors) {console.error(errors);} else {console.log('Successfully set consent flags.');}});
In this section, we will cover how to add the Krux API call to a GDPR TCF v2 Vendor List.
Alternatively, navigate along the following pathways to add a API call to a vendor on a GDPR non-TCF or CCPA Vendor List:
GDPR > Non IAB > Edit
CCPA > Vendor List > Edit
Navigate to your Sourcepoint account and click GDPR from the top navigation bar. Select TCF v2 from the dropdown menu.
Navigate to a Vendor List on the subsequent list and click Edit.
Ensure that the vendor Salesforce (KRUX) is added to the Vendor List.
Click Salesforce (KRUX) from the list of vendors.
From the subsequent modal, select either Consent Actions or Reject Actions and navigate to the provided Custom JS field.
Input the appropriate Krux API call in the field and click Apply changes when finished.
Confirm the implementation with your Krux/Salesforce team to ensure that they are receiving the correct signals.