- Destinations overview
- Destination types and categories
- Destinations (Activation) guardrails
- How destinations work
- API tutorials
- Activate data to file-based destinations by using the Flow Service API
- Connect to streaming destinations and activate data using the Flow Service API
- Connect to file-based email marketing destinations and activate data using the Flow Service API
- (Beta) Activate audiences to batch destinations via the ad-hoc activation API
- Edit destination
- Update destination dataflows
- Delete destination accounts
- Delete destination dataflows
- Export datasets
- Sort and filter API responses for destinations
- UI guides
- Destinations workspace
- Create a new destination connection
- Activate data to destinations
- Activation overview
- Activate audiences to streaming audience export destinations
- Activate audiences to streaming profile export destinations
- Activate audiences to batch profile export destinations
- Activate audiences to edge personalization destinations
- Activate audiences to curated destinations based on LiveRamp identifiers
- Activate prospect audiences to destinations
- (Limited availability) Activate account audiences to destinations
- (Beta) Export files on-demand to batch destinations using the Experience Platform UI
- Export datasets using the Experience Platform UI
- (Beta) Use calculated fields to export arrays in flat schema files
- View destination details
- Update destination accounts
- Delete destination accounts
- Edit activation dataflows
- Delete destinations
- Monitor dataflows
- Configure file formatting options for file-based destinations
- Subscribe to in-context destination alerts
- Destinations catalog
- Destinations catalog overview
- Adobe destinations
- Advertising destinations
- Advertising destinations overview
- Adobe Advertising Cloud connection
- Adobe Advertising Cloud extension
- (Beta) Amazon Ads connection
- Awin Advertiser Conversion Tag extension
- Awin Advertiser Mastertag extension
- Bing Ads Universal Event Tracking (UET) extension
- Branch extension
- (Beta) Criteo connection
- DoubleClick Floodlight (Beta) extension
- Facebook Pixel extension
- Flashtalking OneTag extension
- Google Ads connection
- Google Ads extension
- Google Ad Manager connection
- (Beta) Google Ad Manager 360 connection
- Google Customer Match connection
- Google Display & Video 360 connection
- Google gtag extension
- LinkedIn Insight Tag extension
- LiveRamp - Onboarding connection
- LiveRamp - Distribution connection
- Microsoft Bing connection
- Pinterest Conversion Tracking extension
- Pinterest Customer List connection
- Snapchat Ads connection
- The Trade Desk connection
- (Beta) The Trade Desk CRM connection
- Twitter Universal Website Tag extension
- Yahoo/Verizon DataX connection
- Analytics destinations
- Analytics destinations overview
- Adform Website Tracking extension
- Adobe Analytics extension
- Adobe Media Analytics for Audio and Video extension
- Clicktale extension
- Contentsquare extension
- Decibel extension
- Demandbase extension
- DialogTech extension
- Google Global Site Tag extension
- Google Universal Analytics extension
- JW Player Analytics (Beta) extension
- Nielsen BSDK extension
- Nielsen IMA Handler extension
- Nielsen VideoJS Player Handler extension
- Parse.ly Analytics extension
- Quantum Metric extension
- SessionCam extension
- TMMData extension
- Yext Conversion Tracking extension
- Cloud storage destinations
- Customer Relationship Management (CRM) destinations
- Data Management Platform destinations
- Email destinations
- Email marketing destinations
- Email marketing destinations overview
- Adobe Campaign connection
- Adobe Campaign Managed Cloud Services connection
- Mailchimp Interest Categories
- (API) Oracle Eloqua connection
- (Files) Oracle Eloqua connection
- Oracle Responsys connection
- (API) Salesforce Marketing Cloud connection
- (Files) Salesforce Marketing Cloud connection
- Salesforce Marketing Cloud Account Engagement
- SendGrid connection
- Tag extensions
- Mobile engagement destinations
- Personalization destinations
- Personalization destinations overview
- Adobe Commerce connection
- Adobe Target connection
- Adobe Target extension
- Adobe Target v2 extension
- Beemray extension
- Custom personalization connection
- D&B Visitor Intelligence extension
- Experience Cloud ID Service extension
- Gainsight extension
- KickFire extension
- Marketo Web Personalization extension
- Pega Customer Decision Hub connection
- Pega Profile connection
- Social destinations
- Streaming destinations
- Survey destinations
- Voice of the customer destinations
- Destination SDK
- Overview
- Integration prerequisites
- Getting started with Destination SDK
- Functionality
- Configuration options
- Destination server components
- Destination configuration components
- Customer authentication configuration
- OAuth2 authorization
- Customer data fields
- UI attributes
- Partner schema configuration
- Identity namespace configuration
- Supported mapping configurations
- Destination delivery
- Audience metadata configuration
- Aggregation policy
- Batch configuration
- Historical profile qualifications
- Rate limiting and retry policy for streaming destinations
- Audience metadata management
- Guides
- Use Destination SDK to configure a streaming destination
- Use Destination SDK to configure a file-based destination
- Submit for review a destination authored in Destination SDK
- Configure file-based destinations
- Configure file formatting options
- Configure an Amazon S3 destination with predefined file formatting options and custom file name configuration
- Configure an Amazon S3 destination with custom file name and formatting options
- Configure an Azure Blob Storage destination with custom file formatting options and custom file name configuration
- Configure an Azure Data Lake Storage destination with custom file formatting options and custom file name configuration
- Configure an Data Landing Zone (DLZ) destination with custom file formatting options and custom file name configuration
- Configure an SFTP destination with predefined file formatting options and custom file name configuration
- Destination authoring API reference
- Audience metadata API reference
- Credential configuration API reference
- Destination testing API reference
- Destination publishing API reference
- Document your destination
- Frequently asked questions
- Platform release notes
View destination details
Overview
In the Adobe Experience Platform user interface, you can view and monitor the attributes and activities of your destinations. These details include the destination’s name and ID, controls to activate or disable the destinations, and more. Details also include metrics for activated profile records, identities activated, failed, and excluded, and a history of dataflow runs.
The destinations details page is part of the Destinations workspace in the Platform UI. See the Destinations workspace overview for more information.
View destination details
Follow the steps below to view more details about an existing destination.
-
Log in to the Experience Platform UI and select Destinations from the left navigation bar. Select Browse from the top header to view your existing destinations.
-
Select the filter icon
on the top left to launch the sort panel. The sort panel provides a list of all your destinations. You can select more than one destination from the list to see a filtered selection of dataflows associated with the selected destination.
-
Select the name of the destination that you want to view.
-
The details page for the destination appears, showing its available controls.
Right rail
The right rail displays the basic information about the selected destination.
The following table covers the controls and details provided by the right rail:
| Right rail item | Description |
|---|---|
| Activate audiences | Select this control to edit which audiences are mapped to the destination, update export schedules, or add and remove mapped attributes and identities. See the guides on activating audience data to audience streaming destinations, activating audience data to batch profile-based destinations, and activating audience data to streaming profile-based destinations for more information. |
| Delete | Allows you to delete this dataflow and unmaps the audiences that were previously activated, if any exist. |
| Destination name | This field can be edited in order to update the destination’s name. |
| Description | This field can be edited in order to update or add an optional description to the destination. |
| Destination | Represents the destination platform that audiences are sent to. See the destinations catalog for more information. |
| Status | Indicates whether the destination is enabled or disabled. |
| Marketing actions | Indicates the marketing actions (use cases) that apply for this destination for data-governance purposes. |
| Category | Indicates the destination type. See the destinations catalog for more information. |
| Connection type | Indicates the form by which your audiences are being sent to the destination. Possible values include Cookie and Profile-based. |
| Frequency | Indicates how often the audiences are sent to the destination. Possible values include Streaming and Batch. |
| Identity | Represents the identity namespace accepted by the destination, such as GAID, IDFA, or email. For more information on accepted identity namespaces, see the identity namespace overview. |
| Created by | Indicates the user who created this destination. |
| Created | Indicates the UTC datetime when this destination was created. |
Enabled/Disabled toggle
You can use the Enabled/Disabled toggle to start and pause all data exports to the destination.
Dataflow runs
The Dataflow runs tab provides metric data on your dataflow runs to batch and streaming destinations. Refer to Monitor dataflows for details and metric definitions.
- Destinations monitoring functionality is currently supported for all destinations in Experience Platform except the Adobe Target, Custom personalization and Experience Cloud Audiences destinations.
- For the Amazon Kinesis, Azure Event Hubs, and HTTP API destinations, the metrics related to identities excluded, failed, and activated are estimated. Higher volumes of activation data lead to higher accuracy of the metrics.
Dataflow runs duration
There is a difference in the displayed duration of dataflow runs between streaming and file-based destinations.
Streaming destinations
While the Processing duration indicated for most streaming dataflow runs is about four hours, as shown in the image below, the actual processing time for any dataflow run is much shorter. Dataflow run windows stay open for longer in the event that Experience Platform needs to retry making calls to the destination and also ensure to ensure it does not miss out on any late arriving data for same time window.
For more information, read about dataflow runs to streaming destinations in the monitoring documentation.
File-based destinations
For dataflow runs to file-based destinations, the Processing duration depends on the size of the data being exported and the system load. Notice also that the dataflow runs to file-based destinations are broken down per audience.
For more information, read about dataflow runs to batch (file-based) destinations in the monitoring documentation.
Activation data
The Activation data tab displays a list of audiences that have been mapped to the destination, including their start date and end date (if applicable), and other relevant information for the data export, such as export type, schedule, and frequency. To view the details about a particular audience, select its name from the list.
To view and edit details about the attributes and identities mapped to a destination, select Activate audiences in the right rail.
For details on exploring the details page of a audience, refer to the Segmentation UI overview.
Resources
Adobe Account
