View destination details
Overview 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.
View destination details view-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
-
Select the name of the destination that you want to view.
-
The details page for the destination appears, showing its available controls.
Right rail 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:
GAID, IDFA, or email. For more information on accepted identity namespaces, see the identity namespace overview.Enabled/Disabled toggle enabled-disabled-toggle
You can use the Enabled/Disabled toggle to start and pause all data exports to the destination.
Dataflow runs 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 dataflow-runs-duration
There is a difference in the displayed duration of dataflow runs between streaming and file-based destinations.
Streaming destinations streaming
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 file-based
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 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.
BetaExport multiple files on-demand to batch destinations bulk-export
You can export multiple files on-demand from the Activation data page. To do this, select the audiences for which you want to export files on-demand and select the Export file now control to trigger a one-time export which will deliver a file for each selected audience to your batch destination.
BetaEdit activation schedules for multiple audiences exported to batch destinations bulk-edit-schedule
To edit the existing activation schedule of multiple audiences at the same time, select the desired audiences and then select Edit schedule. For detailed information on how to define or edit an export schedule, read the schedule audience export section.
