Learn how to validate that consent settings are properly applied to your data in Adobe Experience Platform. See the consent documentation for more information on testing your implementation.
Launch is now tags
In this section, we’ll look at our example site requests to inspect and validate our data collection. On our site, we refresh the page and confirm the library build in the Debugger Chrome extension. We can also inspect our set consent call for the Adobe one or two standards in the debugger by clicking on the post body line in the network request. To validate the set consent call and our rule for the IAB TCF 2.0 standard, we use the OneTrust consent banner on our test site to set our consent preferences and create the TC data described earlier. After clicking I accept, we can inspect the set consent call for the IAB standard in the debugger by clicking on the post body line in the network request where you see consent information. Here we see the data we set up earlier in our data elements and launch rule. The value property contains the encoded IAB TC string data we saw earlier. OneTrust, SourcePoint, and other CMPs that implement the IAB TCF 2.0 standard will all produce similar data in our pages. We can capture that data and use it with the Web SDK extension and launch using the custom code event in the rule we created earlier. The custom code will be the same regardless of the CMP used to generate the IAB TCF 2.0 data. The custom code can also be used with either of the platform consent standards, version 1.0 or version 2.0. For sending consent data with experience events, you may have noticed that the XDM consent strings data element we created earlier has not been used in our rules. This data element can be used when you need to send consent data with an experience event or send event action in the Web SDK as opposed to the set consent actions we used earlier. Since this data element contains all the fields required for the IAB TCF 2.0 standard, you can simply reference the data element when sending this XDM data with your experience events. Now that we’ve built our rules and inspected and validated the data, you should see how to implement and activate consent data and data obtained from a CMP using the platform Web SDK. For more details, see the links in the text version of this tutorial. Thank you.