When thinking about the export behavior to Experience Platform destinations, you need to consider three separate levels on which configurations act.
This page describes or links out to all the common and the configurable export settings for destinations, on the three levels outlined above.
Destination export behavior is consistent across destinations belonging to a destination type with regard to what triggers a destination export and what is included in the destination exports. Destination exports are triggered by notifications that the destinations service receives from the upstream Real-time Customer Profile service.
What is included in the destination exports varies slightly between destination types. Read more about the common export behavior patterns per destination type. These settings cannot be edited by destination developers or Real-Time CDP users.
Destination developers can use Destination SDK to create custom or productized (private or public) destinations. Destination SDK provides developers with great flexibility to configure destinations based on the downstream capabilities of their API endpoints and file reception systems. Based on the downstream capabilities, destination developers have the following configuration options available when configuring a destination using Destination SDK:
On top of the non-editable settings that depend on destination type and the settings configured by the destination developer, there are certain export settings that users can configure in the activation workflow. These settings relate to the export schedule for a certain dataflow to a destination, the attributes and identity fields that should be exported in a dataflow, or the file formatting options for exported files.
The settings that are available to users when connecting to a destination depend on how the destination was configured by the destination developer and which settings they made available to users.
For example, for streaming destinations, a destination developer may configure which identities their destination accepts and only those identities will be displayed to the user in mapping step of the activation workflow, as shown below:
Similarly, for file-based destinations, the destination developer may determine which filename append options they want to make available for their destination, or which file formatting options they want to make available, and the user will be able to select from these options only, as shown below:
Read more about the different options and steps available in the activation workflow:
After reading this document, you now know which export settings for destinations are common across destination types, which can be configured on an individual destination level by developers, and which settings can be edited by users in the activation workflow.
Next, you can read more detailed information about the common export behavior patterns per destination type.
For destination developers, you can get started with Destination SDK. For users looking to activate data, you can check out all the available destinations in the catalog.