Set consent using the Adobe standard

Transcript

Now that we’ve set the default behavior of the SDK, we can use launch rules to send visitor consent preferences to platform. Sending consent data using the Adobe one or two standard is easily implemented using the set consent action of the web SDK. Let’s create a rule to demonstrate this. In your launch property, click on rules, then on the blue add rules button. I’ll name this rule set consent on load consent 1.0 and click to add an event. For the event, choose window loaded, which will trigger this rule whenever a page is loaded on our website. Next, under actions, click add to open the action configuration screen. This is where we’ll set the consent data. Click the extension drop down and select AEP web SDK. Then click the action type and select set consent. Under consent information, choose fill out a form. And in this rule action, we’ll use the web SDK to set consent for the Adobe one O consent standard by filling in the form. We can choose to pass in, out, or provided by data element with this set consent action. A data element here should resolve to in or out. In this example, we’ll select in to indicate the visitor has consented to allow the web SDK to send data to platform. Click the blue keep changes button to save this action, then save to library to save this rule. Note, once a visitor has opted out, the SDK will not allow you to set the user’s consent to in. Your launch rules can be triggered by a variety of built in or custom events, which can be used to pass this consent data to platform at the appropriate time during a visitor session. In the above example, we use the window loaded event to trigger the rule. In a later section, we use a consent preference event from a CMP to trigger a set consent action. You can use a set consent action or send event action in a rule triggered by any event you prefer, to indicate an opt in preference setting. Version two of the platform consent standard works with XDM data. It also requires adding a privacy details mix into your profile schema and platform. See the link to governance, privacy and security and platform for more information on this version of the platform consent standard and this mix in. We need to create a custom code data element to pass data to the collect and metadata properties of the consents object shown in this profile schema. The preference details mix in contains fields for the consents and preferences XDM data type, which will contain the consent preference data we send to platform with the SDK in our rule action. Currently, the only required properties to implement the platform consent standard version two dot o are the collect value and the metadata time value. Let’s create a data element for this data. Click on data elements in the blue add data element button. I’ll call this XDM consent to. And using the core extension will select a custom code type. You can enter or copy and paste the following code into the custom code editor window. This time field should specify when the user last updated their consent preferences. We’re creating a timestamp here in his example using a standard method on the JavaScript date object. Click to save the custom code and click save to library to save the data element. Next, let’s click on rules and add a rule. I’ll name it set consent on load Adobe to. Let’s choose the window loaded event as our rule trigger and then add an action. Choose the AEP Web SDK extension and a set consent action type. The standard should be Adobe and version should be two dot o. For value, we use the data element we just created that contains the collect and time values we need to send to platform. To review this example action, we’re calling set consent from the AEP Web SDK extension and passing the standard and the version from the form while passing the values for collect and time from the data element we created earlier. Click the blue save button and again to save the rule. We now have two rules, one for each of the platform consent standards. In practice, you may choose one standard across your site. Next, we’ll create an example using the IABTCF 2.0 consent standard.