Learn how to activate an Adobe Experience Platform segment to a destination using the Amazon S3 connection type.
Hello, and welcome to creating an Adobe Campaign destination in Platform. In order to use Adobe Experience Platform segments to enrich our audiences within Campaign, we need to connect Campaign as a Platform destination. This is done using the Platform user interface. In this video, we will walk through the steps necessary to connect Campaign to Platform as a destination. Experience Platform allows data to be activated or exported to multiple external sources, such as Adobe applications, cloud-based storage, databases and more. This video follows a workflow for creating a Campaign destination using an Amazon S3 bucket, creating a data flow to export a Platform segment to the bucket, and then scheduling the data flow to happen multiple times per day. This video will not cover the steps for creating segments within Platform. For detailed steps on how to create a Platform segment, please refer to the Experience linked videos and documentation.
You will need to have a segment created before creating a destination.
In the Platform UI, select Destinations from the left navigation, then select the Catalog to view all available destinations. You can browse the catalog or use the search functionality to search for Adobe Campaign. Once you have located the Campaign destination, select Configure to begin configuring the destination. If your organization has already connected to this destination, you will see the option to Activate instead of Configure on the destination card. To learn more about the difference between activating and configuring, please refer to the Experience Platform Destinations documentation. For this example, we will select to Configure to configure a new destination from scratch.
Selecting Configure enters the activate destination workflow, where the first step is to connect our Campaign account. We select new account, and then for the connection type, we can select an option from the drop-down. The recommended method to send data to Campaign is through Amazon S3 or Azure Blob. Depending on the connection type you select, you must enter the appropriate details. We will be using Amazon S3, which requires an access key ID and a secret access key.
Optionally, you can add your RSA formatted public key to add encryption with PGP and GPG to your export files under the key section. Your public key must be written as a Base64 encoded string. For this example, we will not select this option. To learn more about adding encryption, refer to the Destinations documentation. Once the information has been entered, select connect to destination.
After confirming that are connected, select Next to continue with the workflow. The next step in the destination activation workflow is to provide account authentication information. This includes a name, where we provide a relevant name for your destination. The description; enter an optimal description for your destination. This is useful if your organization is creating multiple destinations or has multiple people working with destinations. The bucket name. For S3 connections, enter the location of your S3 bucket where Platform will deposit your export data. The folder path. Provide the path in your storage location to the file that should hold your export data.
The file format. For this example, we’ll be exporting as CSV files. And marketing actions. Marketing actions indicate the intent for which data will be exported to the destination. You can select from Adobe defined marketing actions, or you can create your own marketing action. For more information about marketing actions, see the Experience Platform Data Governance documentation. We will select email targeting as our marketing action because this export will be used for sending an email Campaign. After completing the authentication information, select create destination to create your destination.
Once your destination is confirmed, select next to choose the Experience Platform segments that you would like to activate to Campaign. For this example, we have selected a segment of customers who are predicted to make an order, as we want to target them with an email offering a discount code on a future purchase.
With our segment selected, we can select Next to proceed with scheduling our export. On the export screen, we can see the name of the segment we selected, scheduling information, as well as file name. For file based destinations, a unique file name is generated per segment. You can use the file name editor to create and edit a unique file name, or keep the default name. We will keep the default name.
When we select create schedule, the scheduling dialog opens, allowing us to configure our schedule. Under file export options, we can choose to export full files or export incremental files. Choosing to export full files will export a complete snapshot of all the profiles that qualify for the segment.
Choosing to export incremental files will export only the profiles which qualified for the segment since the last export. The first incremental file export includes all profiles that qualify for the segment, acting as a backfill. Future incremental files include only the profiles which qualified for the segment since the first incremental file export. We will select this option to help limit load on our instance. For frequency, we will have the export happen every three hours and indicate the time we would like the first export to happen. For date, we can select a single day or date range where we would like the export to take place. After creating our schedule, we return to the workflow and can see that frequency and export type are now filled in. We then select Next to proceed to selecting attributes. On the attributes selection screen, Experience Platform provides recommended attributes to help us get started. You can use the minus sign to remove any recommended attributes that you don’t want to use. Attributes can be added using the add new field button and can be marked as mandatory or duplication keys using the check boxes. A mandatory attribute makes it so that all exported profiles must include that attribute. In other words, profiles without the mandatory key are not exported, leaving all mandatory check boxes blank exports all qualified profiles, regardless of their attributes. A deduplication key eliminates multiple records of the same profile in the export files. You can select a single namespace or up to two schema fields as a duplication key. Not selecting a duplication key may lead to duplicate profile entries in the export files. Since this segment will be used for an email campaign, we will set email address as a mandatory field, thereby not exporting any profile that does not contain an email address. We will be using the mobile number and email address to deduplicate our records.
With our attributes selected, we can use the Next to proceed to the final review stage.
The review screen provides an overview of the destination that we just created, including the name that we provided, the destination, Adobe Campaign, any marketing actions that were selected. We can also review the number of selected segments and attributes. After confirming this information is accurate, we will select finish to complete our destination setup and begin our scheduled exports.
After our export has run, we can select the Browse tab under Destinations to view our configured destinations. Selecting the name of the destination opens details regarding data flows and activations.
The Dataflow Runs tab shows our data flows every three hours as specified. Since our destination was set up for incremental export, we can see that the first data flow included all profiles in order to backfill the data. Since no profiles were added between the first data flow and the next, the subsequent data flows shows zero new profiles received.
The Activation Data tab shows the segments that have been activated to Adobe Campaign, as well as their status related to marketing actions and more.
Here we can see the customers predicted to order segment that we selected during the destination configuration.
After watching this video, you’ve learned how to activate an Experience Platform segment to a destination using an Amazon S3 bucket. The export of data is now available within S3 and updated files will add only the newly qualified segment members at regular intervals. Thanks for watching. -