Configure the Adobe Target destination in Real-Time Customer Data Platform

Hi, this is Daniel and in this video I’m going to show you how to set up the Adobe target destination in Realtime Customer Data Platform so you can begin sharing both segments and profile attributes from real-time CDP to target to personalize your websites, mobile apps, and other connected devices. These are mostly administrative tasks needed to get the integration up and running. In other videos we’ll cover how to actually share and use the segments and profile attributes. The setup is easy and you’ll see it’s just a matter of checking various boxes and pressing buttons, but they’re spread over a few product features and depending on how your company manages user permissions it might require a few people at your company to complete these steps. So the features we need to configure are data streams, merge policies, and destinations. First let’s enable a data stream. To get the most functionality out of the integration you should implement the Adobe Experience Platform web and or mobile SDKs which use platform edge network and data streams to send data to target. You can still share segments to target if you’re still on an older SDK like ATJS, but the segment qualification won’t happen on the edge and will be a little slower. Of course ATJS doesn’t use data stream so if you’re still using that library you can skip this step. Okay so I’m in the platform interface but you can also do this in the data collection interface too. You need to have permissions to view and manage data streams to complete this step. Okay so first both target and experience platform need to be included as services in the data stream. Second in the experience platform service you need to check these two boxes for edge segmentation and personalization destinations. Now I’m doing this in a dev sandbox and you would need to repeat this for any other sandboxes or data streams in which you’re going to use the integration. That’s it for this step. Next let’s make a small change to a merge policy. To complete this step you need to have permissions to view and manage merge policies. In experience platform I’ll navigate to profiles in the left navigation and select the merge policies tab. A merge policy creates a view of a profile specifying which data sets are included and how to prioritize overlapping fields. You can create multiple merge policies that create different views of a single profile but only one merge policy can be selected as the default and only one can be used with edge segments. To keep things simple for your marketers I suggest just activating your default merge policy for edge which you can easily do by enabling this active on edge merge policy toggle and then clicking through the workflow to save the policy. When marketers create segments that evaluate on the edge the segment definition needs to use this active on edge merge policy. Let me just show you quickly in this segment builder. You see here under the gear icon you can see the merge policy used by this segment. So if you hear from a marketer that they’re unable to save an edge segment it’s probably because they’re using the wrong merge policy and that’s why it’s easiest to just enable the default merge policy for edge. Again another simple but important configuration. So finally I’ll set up the Adobe Target connection and a destination. For this I need permission to view and manage destinations. All you have to do is select the connect to destination button and it’s going to connect to the Adobe Target account that’s in your experience cloud organization. This checkbox will subscribe you to alert notifications if a certain threshold of profiles aren’t getting sent to target due to missing attributes or consent violations. You can subscribe to them later as well. On the next screen it’s going to ask me for a name and description as well as the data stream id. For the data stream id I’m going to select the one that I just enabled with those two check boxes. Then I’m asked for the marketing actions used by target. This is a configuration setting for every destination and it helps to automate enforcement of your organization’s data governance policies and your customers consent preferences. It’s basically asking how do you use target which might be slightly different for each one of you. I’ll check a few options and that’s it for the destination and remember you can set up additional destinations for your other data streams and sandboxes. In other videos I’ll show you how you can activate segments and profile attributes to target and use them to personalize your digital properties. So thanks for listening.