Once you have submitted this request, Adobe will proceed to the provisioning of the integration for you and contact you to provide details and information that you have to finalize the configuration:
If you are using the demdex domain and following the syntax ftp-out.demdex.com for the import external account and ftp-in.demdex.com for the export external account, you need to adapt your implementation accordingly and move to Amazon Simple Storage Service (S3) connector to import or export data. For more information on how to configure your external accounts with Amazon S3, refer to this section.
The following diagram details how this integration works. Here, AAM stands for Adobe Audience Manager and AC for Adobe Campaign.
First, we need to configure or check the external accounts in Adobe Campaign as follows:
Click the Explorer icon.
Go to Administration > Platform > External accounts. The mentioned SFTP accounts should have been configured by Adobe and the necessary information should have been communicated to you.
Select the Export audiences to the Adobe Marketing Cloud external account.
From the Type drop-down, select AWS S3.
Provide the following details:
AWS S3 Account Server
URL of your server, it should be filled as follows:
<S3bucket name>.s3.amazonaws.com/<s3object path>
AWS access key ID
To know where to find your AWS access key ID, refer to this page .
Secret access key to AWS
To know where to find your secret access key to AWS, refer to this page.
To learn more on AWS region, refer to this page.
Click Save and configure the Import audiences from the Adobe Marketing Cloud external account as detailed in the previous steps.
Your external accounts are now configured.
The Recipient - Visitor ID is created inside Audience Manager. This is an out-of-the-box data source configured by default for Visitor ID. Segments created from Campaign will be part of this data source.
To configure the Recipient - Visitor ID data source:
From the Explorer node, select Administration > Platform > AMC Data sources.
Select Recipient - Visitor ID.
Enter the Data Source ID and AAM Destination ID provided by Adobe.
For the configuration of the integration with People Core service or Audience manager, we also need to configure Campaign Tracking server.
To enable shared audiences to function with Visitor ID, the tracking server domain should be a sub-domain of the clicked URL or the main website.
You need to make sure the Campaign Tracking Server is registered on the domain (CNAME). You can find more information about domain name delegation in this article.
Sync customer identifiers with Declared ID using the
setCustomerID function in the Experience Cloud ID service with the integration code:
AdobeCampaignID should match the value of the Reconcilation key set in the Recipient Data Source configured in Step 2: Configure the Data Sources.
Your configuration and provisioning are finalized, the integration can now be used to import and export audiences or segments.