Information to help you set up destinations in Audience Manager and avoid common problems.
Common destination configuration problems include the following issues:
When selecting a format for your outbounded data, it’s best, if possible, to re-use an existing format. Using an already-proven format ensures that your outbound data will be generated successfully. To see exactly how an existing format is formatted, click the Formats option in the menu bar and search for your format either by name or by ID number. Malformed formats or macros used in formats will provide incorrectly formatted output or will prevent information from being output entirely.
For more information on setting up formats and using macros, see File Format Macros and HTTP Format Macros.
FTP
S3
READ-ONLY
credentials that are meant to be handed off to the client. These credentials should not be entered into the Access / Secret Key fields, because this will cause the transfer to fail (because those credentials are read-only, not writable). In the case where TechOps creates a bucket and provides credentials, the consultant should also request an Adobe key pair - NOT TO BE GIVEN TO THE CLIENT - that will allow for writing files to this bucket. That key should be added into these fields.HTTP
SSH PRIVATE
key value in this box, including headers, footers, and line breaks to ensure accurate encryption/key storage.The outbounding process runs twice daily, and multiple processes (outbounding, publishing, pushing to external locations, etc.) must run before a file is pushed to its final destination. A good rule of thumb is that a destination should be fully configured at least 24 hours before you can expect data to be pushed to an external location.
When outbounding files to destinations, you can split larger outbound files in file chunks. Make sure that the individual file chunks do not exceed 10 GB. See also, Outbound Data File Name: Syntax and Examples.
This page shows you how to set up destinations to export data keyed off the ID type you want in Outbound Data Files.
Destinations allow our customers to activate their data across any number of digital channels. For example, they can export audience data to other Adobe Experience Cloud solutions (Target, Campaign, etc.). Or, they could send data to DSPs, SSPs, or any platform that is integrated with Audience Manager. We keep a list of partners we work with on our Integrations Wiki page.
For a detailed walkthrough on creating destinations in the Admin UI, look to the Create or Edit Company Destinations article.
Your customers want to export different ID types, depending on destination. The configuration chart below shows the options you should select to export profile information related to different ID types. We recommend you also refer to the Index of IDs in Audience Manager. There are three important settings to consider, the User ID Key, the Data Source Type and the Format. We detail all of them below.
User ID Key. In the Admin UI, go to Companies. Search for your customer’s company and click it. Look for the Destinations tab and press Add Destination. In the Add Destination workflow, select the User ID Key. The User ID Key will filter the incoming IDs from the target data source and only allow the IDs to pass.
Data Source Type. Select this when creating a destination in the Audience Manager UI. First of all, select Inbound, then select the ID type you want. The options are:
Format. This option determines the file format you will export. In the Add Destination workflow, under Batch Data, select the format.
To inspect a format, go to Admin UI > Formats and look for the Data Row element. This element contains a macro of the file format, <MCID> in the example below.
Configuration No. | User Key |
Data Source Type |
Format |
Exported ID Type |
---|---|---|---|---|
1 | Adobe Audience Manager (0) |
Experience Cloud ID |
<DP_UUID> |
Experience Cloud ID |
2 | Adobe Audience Manager (0) |
Experience Cloud ID |
MCID |
Audience Manager UUID |
3 | Adobe Audience Manager (0) |
Experience Cloud ID |
UUID |
Experience Cloud ID |
4 | Adobe Audience Manager (0) |
Audience Manager ID |
<DP_UUID> |
Audience Manager UUID |
5 | Adobe Audience Manager (0) |
Audience Manager ID |
MCID |
Experience Cloud ID |
6 | Adobe Audience Manager (0) |
Audience Manager ID |
UUID |
Audience Manager UUID |
7 | DPID (Any data source that the company has access to) |
Customer ID |
<DP_UUID> |
Customer ID (DPUUID) |
8 | DPID (Any data source that the company has access to) |
Customer ID |
MCID |
Experience Cloud ID |
9 | DPID (Any data source that the company has access to) |
Customer ID |
UUID |
Audience Manager UUID |
10 | DPID (Any data source that the company has access to) |
Audience Manager ID |
<DP_UUID> |
Audience Manager UUID |
11 | DPID (Any data source that the company has access to) |
Audience Manager ID |
MCID |
Experience Cloud ID |
12 | DPID (Any data source that the company has access to) |
Audience Manager ID |
UUID |
Audience Manager UUID |
Let’s say you use Audience Manager and Campaign. In order to make the customer data actionable in Campaign, you want to export Experience Cloud IDs. You should use configuration number 3 in this case.