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.
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.
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 segments | Select this control to edit which segments are mapped to the destination, update export schedules, or add and remove mapped attributes and identities. See the guides on activating audience data to segment 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 segments 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. |
You can use the Enabled/Disabled toggle to start and pause all data exports to the destination.
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.
There is a difference in the displayed duration of dataflow runs between streaming and file-based 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.
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 segment.
For more information, read about dataflow runs to batch (file-based) destinations in the monitoring documentation.
The Activation data tab displays a list of segments 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 segment, select its name from the list.
To view and edit details about the attributes and identities mapped to a destination, select Activate segments in the right rail.
For details on exploring the details page of a segment, refer to the Segmentation UI overview.