Adobe Experience Platform Destination SDK
Use Adobe Experience Platform Destination SDK to build destination integrations that deliver audience and profile data to your endpoint or storage location. Choose your data and authentication formats, store configurations in Experience Platform, and retrieve them via API for updates.
Follow this documentation to configure, test, and release a productized destination integration with Adobe Experience Platform and list it in the destinations catalog. You can also use Destination SDK to build a private custom destination to export data tailored to your needs.
Quick start quick-start
Use these resources to configure and submit your destination via Destination SDK.
Productized and custom integrations productized-custom-integrations
As a Destination SDK partner, you can add your productized destination to the Experience Platform catalog to:
- Standardize integration configurations across customers using pre-configured parameters and simplify their setup experience.
- Give customers a branded destination card in the catalog for easier discovery and setup.
- Be listed as a productized integration with Adobe Experience Platform and Real-Time Customer Data Platform.
As an Experience Platform customer, you can also build a private custom destination to fit your activation needs.
Supported integration types supported-integration-types
Real-time (streaming) integrations real-time-integrations
Through Destination SDK, Adobe Experience Platform supports real-time (streaming) integrations with destinations that have a REST API endpoint. These integrations support:
- Message transformation and aggregation
- Profile backfill
- Configurable metadata integration to initialize audience setup and data transfer
- Configurable authentication
- A suite of testing and validation APIs to test and iterate your destination configurations
File-based integrations file-based-integrations
Through Destination SDK, you can also set up integrations to periodically export files to your preferred storage location. File-based integrations support:
- File export in several supported formats (CSV, Parquet, JSON)
- Configurable file formatting options to structure exported files to fit your downstream needs.
For technical requirements, see integration prerequisites. For all supported configurations, see configuration options.
Get access to Destination SDK get-access
Destination SDK access depends on your status as a partner or Real-Time CDP customer.
High-level process process
To configure your destination in Experience Platform, follow these steps:
- If you are an ISV or SI, see Get access to Destination SDK. Real-Time CDP Ultimate package customers can skip this step.
- Request to provision an Experience Platform sandbox and enable the destination authoring permission. For authentication credentials and access control setup, see Getting started with Destination SDK.
- Build your integration. Follow the instructions in the product documentation to configure streaming destinations or file-based destinations.
- Test your integration. Follow the instructions in the product documentation to test streaming destinations or file-based destinations.
- If you are an ISV or SI creating a productized integration, submit your integration for Adobe’s review. The standard response time is five business days.
- If you are an ISV or SI creating a productized integration, use the self-service documentation process to create a product documentation page on Experience League for your destination.
- For productized integrations, once Adobe approves your submission, your integration appears in the Experience Platform catalog.
- To update your integration, follow the same process.
Reference reference
Before building your integration, review the following Experience Platform documentation: