These commands are not processed until you have communicated the user’s opt-in preferences to the SDK. With this “Pending” setting, attempting to execute any commands that require user opt-in preferences (for example, the event command) will result in the command being queued within the SDK. If the default consent setting is “Pending”, the SDK will queue any events that occur before the user provides consent preferences, so the events may be sent after consent preferences are set, and after the SDK is initially configured during a visit. For example, if you scroll and view a web page before you select the consent banner, and this “Out” setting is used, that scroll activity and viewing time will not be sent if the user later provides explicit consent for data collection. Visitor activity that occurs before setting the consent preference will not be included in any data sent by the SDK after consent is set. If the default consent setting is “Out”, this tells the SDK that it should not collect any events that occur before the user opt-in preferences are set. These preferences are typically handled and stored in a CMP. If the default consent setting is “In”, this tells the SDK that it should not wait for explicit consent and it should collect the events that occur before the user provides consent preferences. Pending - Queue events that occur before the user provides consent preferences.Out - Drop events that occur before the user provides consent preferences.In - Collect events that occur before the user provides consent preferences.The chosen setting answers the question of “what should the SDK do if the user has not yet provided explicit consent preferences?” This sets the default state for consent and event data collection in the SDK. The “Privacy” section sets the consent level for the SDK if the user has not previously provided consent preferences. Step 1: Configure Consent in the Web SDK extensionĪfter we’ve installed the Platform Web SDK extension in a Tags property, we can configure the options for addressing consent data on the extension configuration screen: The screenshots below of the Platform Web SDK extension are from version 2.4.0 of the extension which is compatible with either v1.0 or v2.0 of the Adobe Consent Standard.įor more information on these standards, see Supporting customer consent preferences. The 2.0 standard allows you to add additional consent data that can be used to manually enforce consent preferences. The 1.0 standard is being phased out in favor of v2.0. Using the Web SDK with the Adobe Consent Standard (v1.0 or v2.0) To implement the IAB TCF example with a CMP on your own site, you’ll need access to a CMP like OneTrust or Sourcepoint to generate the data they provide, or you can simply follow along here and see the results below. We’ll also use the Platform Debugger Chrome extension to inspect and validate our implementation. These topics are detailed and demonstrated in these documents: This tutorial assumes you have access to Data Collection and have created a client-side Tags property with the Web SDK extension installed and a working library created and built for development. For a tutorial on schema creation, see Create a schema using the Schema Editor and for the required Consent and Preference Details field group see Configure a dataset to capture consent and preference data. To send consent information with events, the IAB TCF 2.0 Consent Details field group needs to be added to your Experience Event schema:įor the Platform consent standard v2.0, we’ll also need access to Adobe Experience Platform to create an XDM Individual Profile schema and dataset. On that page, there’s a requirement for an “Event Dataset” and, just like it sounds, this is a dataset to hold your experience event data. The prerequisites for using the Web SDK are listed here. For an overview of the Web SDK, see this page. This tutorial uses the Platform Web SDK extension to send consent data to Platform. We’ll do this using both of the Adobe standards and the IAB TCF 2.0 consent standard, with OneTrust or Sourcepoint as example CMPs. This tutorial demonstrates how to implement and activate consent data obtained from a Consent Management Platform (CMP) using the Platform Web SDK extension in Data Collection. Edge configurations are now datastreams.Platform Launch Server Side is now event forwarding.Platform Launch (Client Side) is now tags.Several terminology changes have rolled out in the interface which you should be aware of while using this content: Adobe Experience Platform Launch is being integrated into Adobe Experience Platform as a suite of data collection technologies.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |