An AAM Destination integration is used to send audiences from AAM to a 3rd party (partner) application. This setup is done either by an Adobe consultant or Adobe CustomerCare representative. This setup is usually done within 1-3 business days following the request being made to Adobe.
Enabling an integration for a customer really means creating a server-to-server "Destination" in Audience Manager. The Destination is configured with information about the partner's server/endpoint and how frequently data should be delivered.
Enabling a Partner destination for a customer does not automatically enable the Partner ID sync pixel on their web property. Customer's must explicitly mention this to the Adobe CustomerCare/Consultant.
Customer integration process flow
The following is a typical process for enablement:
- Customer requests integration activation to either the Partner or Adobe representative (Adobe consultant or CustomerCare). Partner should ask the customer to redirect their request to the Adobe representative.
- Adobe representative reviews the integration request and sets up ("Activates") the Destination for the customer.
- Adobe representative may contact the Partner contact to exchange segment mapping and other required information.
- Destination is setup and Partner should start receiving the audience data -- assuming segments have been mapped to the Destination.
Once the Destination is created, audience segments can be mapped to it. These segments can be online or offline depending on how the audiences are being collected:
- Online (Rule-based) Segments: The audiences collected in these segment are based on their qualification of some business logic or rule as defined by the customer. These audiences are made up of visitors to the AAM customer's tagged web property. These can be sent to a Destination using both realtime and batch methods.
- Offline (On-boarded) Segments: These audiences are sourced from 1st or 3rd party data that is onboarded to AAM using batch uploads. These can be sent to a Destination only through a batch method -- realtime is not available.
Steps to map segments to a Destination
- Click Manage Data>Destinations
- Locate the destination
- Click on the destination and then edit it
4. In the Segment Mapping section, search for the segment you want to map to a destination and click Add:
5. In the Edit Mapping section, customer can select a start date and optional end date.
6. Mapping field can either be prepopulated with AAM segment ID or can be open text field depending on what was agreed as the segment mapping to be sent in the S2S transfer.
7. In case of open text field, customer can put whatever is the requirement for segment mapping.
The field "Mapping" in the above process, is the ID that represents the segments in the files/JSON message that you will receive. In this case, it is an AAM segment ID however, it can optionally be a segment ID that originates from the Partner platform.