Destinations overview overview
Destinations are pre-built integrations with destination platforms that allow for the seamless activation of data from Adobe Experience Platform. You can use destinations to activate your known and unknown data for cross-channel marketing campaigns, email campaigns, targeted advertising, and many other use cases.
Destinations and sources destinations-and-sources
One of the core functionalities of Platform is ingesting your first-party data and activating it for your business needs. Use sources to ingest data into Platform and destinations to export data from Platform.
Destinations steps steps
- Choose from a self-service catalog of all the destinations available in Platform.
- Use destinations to send audiences or datasets to marketing automation platforms, digital advertising platforms, and more.
- Schedule data exports to your preferred destinations at regular times.
Controls controls
The controls in the destinations workspace allow you to:
- Browse the catalog of destination platforms where you can activate your data;
- Create, edit, activate, and disable data flows to the destinations in the catalog;
- Create an account in a storage location or link Platform to the account in the destination platform;
- Select which audiences or datasets should be activated to destinations;
- Select which Experience Data Model (XDM) fields to export when activating audiences to certain destinations like email marketing destinations, CRM platforms, cloud storage locations, and more.
- Activate different types of profiles and audiences to destinations - people, accounts, and prospects.
Destination types and categories types-and-categories
With Experience Platform, you can activate data to various types of destinations, to satisfy your activation use cases. Destinations range from API-based integrations, to integrations with file reception systems, profile lookup destinations, and more. For detailed information about all available destinations, read the destination types and categories overview.
Adobe-built and partner-built destinations adobe-and-partner-built-destinations
Some of the connectors in the Experience Platform destinations catalog are built and maintained by Adobe, while others are built and maintained by partner companies using Destination SDK. A note at the top of the documentation page for each partner-built connector calls out if a destination is created and maintained by the partner. For example, the Amazon S3 connector is created by Adobe, while the TikTok connector is created and maintained by the TikTok team.
For partner-authored and maintained connectors, this means that issues with the connector might need to be resolved by the partner team (contact method provided in the note in the documentation page). For issues with Adobe-authored and maintained connectors, contact your Adobe representative or Customer Care.
Destinations and access controls access-controls
The destinations functionality in Platform works with Adobe Experience Platform access control permissions. Depending on your user’s permission level, you can view, manage, and activate destinations. For information about the individual permissions, go to access control in Adobe Experience Platform and scroll down to the table at the bottom of the page.
The following table outlines the permissions and permission combinations required to perform certain actions on destinations.
The diagram below visually displays which permissions you need depending on the operations that you want to perform on destinations.
For more information about access controls, see the Access control user guide.
Attribute-based access control for destinations attribute-based-access
Attribute-based access control in Adobe Experience Platform allows administrators to control access to specific objects and/or capabilities based on attributes.
With attribute-based access control, you can apply mapping configurations to fields that you have permissions to. Furthermore, you cannot export data to a destination if you do not have access to all fields in the dataset.
For more information on how destinations work with attribute-based access controls, read the attribute-based access control overview.
Destinations monitoring destinations-monitoring
After establishing a connection to a destination and completing the activation workflow, you can monitor the data exports to your reception system. Read the guide on monitoring dataflows to destinations in the UI for more information.
You can also validate if data is coming through successfully to your destination. Most destination documentation pages in the catalog have a Validate data export section, which indicates how you can check in the destination platform that data is being successfully brought in from Experience Platform. View an example of this section for the Amazon Ads destination.
Data governance restrictions on activating data to destinations data-governance
Data governance is enforced for Platform destinations through:
- Marketing actions that you can select in the create destinations workflow;
- Data usage policies that restrict data containing certain usage labels from being activated to destinations with certain marketing actions.
See the Data Governance in Platform documentation for more information about marketing actions and resolving data policy violations.
For more information about selecting marketing actions in the create destination workflow, see the following pages for the different destination types in Platform:
For more information about data policy violations in the audience activation workflow, see the Review step in the following guides:
Terms and conditions terms-and-conditions
By using any of the Destinations labeled as beta (“Beta”), You hereby acknowledge that the Beta is provided “as is” without warranty of any kind.
Adobe shall have no obligation to maintain, correct, update, change, modify, or otherwise support the Beta. You are advised to use Informative and not to rely in any way on the correct functioning or performance of such Beta and/or accompanying materials. The Beta is considered Confidential Information of Adobe.
Any “Feedback” (information regarding the Beta including but not limited to problems or defects you encounter while using the Beta, suggestions, improvements, and recommendations) provided by You to Adobe is hereby assigned to Adobe including all rights, title, and interest in and to such Feedback.
Submit Open Feedback or create a Support Ticket to share your suggestions or report a bug, seek a feature enhancement.