ÃÛ¶¹ÊÓƵ

DocumentationCampaignCampaign Standard Documentation

Provisioning and configuring integration with Audience Manager or People core service integration-with-audience-manager-or-people-core-service

Last update: Wed Jul 31 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Intermediate
  • Developer

The provisioning and configuring of Audience Manager and People core in ÃÛ¶¹ÊÓƵ Campaign take two steps: Submitting request to ÃÛ¶¹ÊÓƵ then Configuring the integration in ÃÛ¶¹ÊÓƵ Campaign.

Submitting request to ÃÛ¶¹ÊÓƵ submitting-request-to-adobe

Audience Manager (AAM) or People core service integration lets you import and export audiences or segments in ÃÛ¶¹ÊÓƵ Campaign.

This integration must first be configured. To request provisioning of this integration, contact ÃÛ¶¹ÊÓƵ Support with the following information:

Request Type:
Configure AAM/People core service-Campaign Integration
Organization Name:
Your organization name
IMS Org ID
Your Organization ID.
To find your organization ID, refer to this page
Environment:
Example: Production
AAM or People Service
Example: ÃÛ¶¹ÊÓƵ Audience Manager. Be sure to mention to the provisioning team whether or not you own Audience Manager license.
Declared ID or Visitor ID
Example: Declared ID
Additional Information
Any useful information or comment that you may have

Configuring the integration in ÃÛ¶¹ÊÓƵ Campaign configuring-the-integration-in-adobe-campaign

After submitting this request, ÃÛ¶¹ÊÓƵ 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:

Step 1: Configure or check the external accounts in ÃÛ¶¹ÊÓƵ Campaign step-1--configure-or-check-the-external-accounts-in-adobe-campaign

We first need to configure or check the external accounts in ÃÛ¶¹ÊÓƵ Campaign. These accounts should have been configured by ÃÛ¶¹ÊÓƵ and the necessary information should have been communicated to you.

To do so:

  1. From the advanced menu, select Administration > Application settings > External accounts.

    Select one of the following external accounts available for this integration:

  2. Enter Receiver server in following format

  3. Enter the AWS Access Key ID, Secret Access Key and AWS Region.

Your external accounts are now configured for this integration.

Step 2: Configure the Data Sources step-2--configure-the-data-sources

The two following data sources are created inside Audience manager: ÃÛ¶¹ÊÓƵ Campaign (MID) and ÃÛ¶¹ÊÓƵ Campaign (DeclaredId). At the same time, these two data sources are available in ÃÛ¶¹ÊÓƵ Campaign:

  • Recipient - Visitor ID (Defaultdatasources): 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.
  • Declared ID data source: This data source needs to be created and mapped with the DeclaredId data source definition from Audience Manager.

Please note that in the case of multiple websites with different domains, ÃÛ¶¹ÊÓƵ Campaign does not support reconciliation based on ECID.

To configure the Recipient - Visitor ID (Defaultdatasources) data source:

  1. In Administration > Application settings > Shared Data Sources, select Recipient - Visitor ID (Defaultdatasources).

  2. Choose ÃÛ¶¹ÊÓƵ Campaign in the Data Source/ Alias drop-down.

  3. Enter the AAM Destination ID provided by ÃÛ¶¹ÊÓƵ.

  4. In the Reconciliation process category, we advise you not to change the reconciliation criteria and always use the Visitor ID.

  5. Click Save.

To create the Declared ID data source:

  1. In Administration > Application settings > Shared Data Sources, click the Create button.
  2. Edit the Label of your data source.
  3. In the Data Source/ Alias drop-down, choose the Data Source corresponding to the DeclaredID data source from Audience Manager.
  4. Configure your data source by entering the Data Source / Alias and AAM Destination ID provided by ÃÛ¶¹ÊÓƵ.
  5. Set the Reconciliation process as needed.
  6. Click Save.
NOTE
The AAM Destination ID field is not required if you are configuring the shared data source for the Campaign-Triggers integration. Priority is only needed when configuring the Triggers - Campaign integration. Priority decides which Data Source will be configured first. Priority can be any number such as 1 or 100. The higher the priority, the higher the preference during reconciliation.

Step 3: Configure Campaign Tracking server step-3--configure-campaign-tracking-server

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.

IMPORTANT
You need to make sure the Campaign Tracking Server is registered on the domain (CNAME). You can find more information about domain name configuration in .

Step 4: Configure the Visitor ID Service step-4--configure-the-visitor-id-service

In the case that your Visitor ID service has never been configured on your web properties or websites, refer to the following document to learn how to configure your service or the following .

Sync customer identifiers with Declared ID using the setCustomerID function in the Experience Cloud ID service with the integration code: ÃÛ¶¹ÊÓƵCampaignID. The ÃÛ¶¹ÊÓƵCampaignID 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.

recommendation-more-help
3ef63344-7f3d-48f9-85ed-02bf569c4fff