The Acxiom Data Enhancement destination is in beta. This destination connector and documentation page are created and maintained by the Acxiom team. For any inquiries or update requests, please contact them directly at acxiom-adobe-help@acxiom.com.
Use the Acxiom Data Enhancement connector to supply additional descriptive data to your customer profiles, for use in analytics, segmentation, and targeting applications. With hundreds of elements available, this allows you to better segment and model data, resulting in more accurate targeting and predictive modeling.
This tutorial provides steps to create an Acxiom Data Enhancement destination connection and dataflow using the Adobe Experience Platform user interface. This connector is used to deliver data to Acxiom enhancement service using Amazon S3 as a drop point.
To help you better understand how and when you should use the Acxiom Data Enhancement destination, here are sample use cases that Adobe Experience Platform customers can solve by using this destination.
This connector should be used by marketing professionals aiming to enhance the effectiveness of their outreach strategies by appending selected descriptive elements to their customer profiles and use these to better target campaigns.
For example, as a marketer, you might want to deepen your understanding of your existing audiences by enriching their profiles with additional data. Doing so will improve your segmentation and targeting strategies, leading to a boost in campaign personalization and conversion.
The use case is executed through a combination of both destination and source connectors.
You would start by exporting your existing customer records for enrichment using this destination connector. Acxiom’s service would search for the file, retrieve it, enrich it with Acxiom’s data and generate a file.
The customer would then use the corresponding Acxiom Data Ingestion source card to ingest the hydrated customer profiles back into Adobe Real-Time CDP.
This section describes which type of audiences you can export to this destination.
Audience origin | Supported | Description |
---|---|---|
Segmentation Service | ✓ | Audiences generated through the Experience Platform Segmentation Service. |
Custom uploads | x | Audiences imported into Experience Platform from CSV files. |
Refer to the table below for information about the destination export type and frequency.
Item | Type | Notes |
---|---|---|
Export type | Profile-based | You are exporting all members of a segment, together with the desired schema fields (for example: email address, phone number, last name), as chosen in the select profile attributes screen of the destination activation workflow. |
Export frequency | Batch | Batch destinations export files to downstream platforms in increments of three, six, eight, twelve, or twenty-four hours. Read more about batch file-based destinations. |
To connect to the destination, you need the View Destinations and Manage and Activate Dataset Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
To connect to this destination, follow the steps described in the destination configuration tutorial. In the destination configuration workflow, fill in the fields listed in the two sections below.
To authenticate to the destination, fill in the required fields and select Connect to destination.
In order to access your bucket on Experience Platform, you need to provide valid values for the following credentials:
Credential | Description |
---|---|
S3 Access key | The access key ID for your bucket. You can retrieve this value from the Acxiom team. |
S3 Secret key | The secret key ID for your bucket. You can retrieve this value from the Acxiom team. |
Bucket name | This is your bucket where files will be shared. You can retrieve this value from the Acxiom team. |
To define a new Acxiom Managed S3 location:
Accounts already defined using the Acxiom Data Enhancement destination appear in a list pop-up. When selected, you can see details on the account in the right rail. View the example from the UI, when you navigate to Destinations > Accounts;
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
When selecting the CSV option, Delimiter, Quote Character, Escape Character, Empty Value, Null Value, Compression format, and Include manifest file options will be presented, the following document explains these settings in more detail configure the formatting options.
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
Read Activate audience data to batch profile export destinations for instructions on activating audiences to this destination.
The correct processing of files on the Acxiom side requires name and address elements. While not all elements are required, providing as much as possible will aid in successful matching.
Mapping suggestions are provided in the table below listing attributes on your destination side that are used by Acxiom processing that customers can map profile attributes to. Treat these elements as suggestions as not all elements are required and the source values will depend on the needs of the account.
Target Field | Source Description |
---|---|
name | The person.name.fullName value in Experience Platform. |
firstName | The person.name.firstName value in Experience Platform. |
lastName | The person.name.lastName value in Experience Platform. |
address1 | The mailingAddress.street1 value in Experience Platform. |
address2 | The mailingAddress.street2 value in Experience Platform. |
city | The mailingAddress.city value in Experience Platform. |
state | The mailingAddress.state value in Experience Platform. |
zip | The mailingAddress.postalCode value in Experience Platform. |
If you map additional fields not listed above in the dataflow, these will be included in the data export, but will be ignored by Acxiom processing.
To verify if data has been exported successfully, check your Amazon S3 Storage bucket and make sure that the exported files contain the expected profile populations.
By following this tutorial, you have successfully created a dataflow to export profile data from Experience Platform to your Acxiom managed S3 location. Next, you need to contact your Acxiom representative with the name of the account, file names, and the bucket path so that processing can set up.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, read the Data Governance overview.
Acxiom Infobase: https://www.acxiom.com/wp-content/uploads/2022/02/fs-acxiom-infobase_AC-0268-22.pdf