Adobe Experience Platform Destination SDK

Overview

Adobe Experience Platform Destination SDK is a suite of configuration APIs that allow you to configure destination integration patterns for Experience Platform to deliver audience and profile data to your endpoint, based on data and authentication formats of your choice. The configurations are stored in Experience Platform and can be retrieved via API for additional updates.

The Destination SDK documentation provides instructions for you to use the Adobe Experience Platform Destination SDK to configure, test and release a productized destination integration with Adobe Experience Platform, and have your destination become part of the ever-growing destinations catalog.

Destinations catalog overview

Productized and custom integrations

As a Destination SDK partner, you can benefit from adding your productized destination to the Experience Platform catalog:

  1. Standardize integration configurations across customers with pre-configured parameters and simplify the setup experience for customers.
  2. Introduce a branded destination card in the Experience Platform destinations catalog for simplified customer setup and awareness.
  3. Be featured as a productized destination integration with Adobe Experience Platform & Real-time Customer Data Platform.

As an Experience Platform customer, you can author an own private custom destination, which can best suit your activation needs.

Destination SDK visual diagram

Types of integrations supported

Through Destination SDK, Adobe Experience Platform supports real-time integrations with destinations that have a REST API endpoint. The real-time integration with Experience Platform supports capabilities like:

  • Message transformation and aggregation
  • Profile backfill
  • Configurable metadata integration to initialize audience setup and data transfer
  • Configurable authentication
  • A suite of testing & validation APIs for you to test and iterate your destination configurations

Read about the technical requirements on the destinations side in the integration prerequisites article.

Get access to Destination SDK

Destination SDK access varies based on your status as a partner or Experience Platform customer. Please see the table below for more information.

Type of partner or customer How to access Destination SDK
Independent Software Vendor (ISV) Join the Adobe Exchange program and request to get an Experience Platform sandbox provisioned to access Destination SDK.
System Integrator (SI) You need to be at either Gold or Platinum level in the Adobe Solution Partner Program, and you will get an Experience Platform sandbox provisioned and access to Destination SDK.
Experience Platform customer on the Activation package By default, you get access to Experience Platform sandboxes and Destination SDK.
Experience Platform customer on the Real-time CDP package You do not have access to Destination SDK, but you have access to all the productized destinations configured by other companies using Destination SDK and published across Experience Platform organizations.

High-level process

The process to configure your destination in Experience Platform is outlined below:

  1. If you are an ISV or SI, see the getting access information in the section above. Adobe Experience Platform Activation customers can skip this step.
  2. Request to provision an Experience Platform sandbox and enable the destination authoring permission.
  3. Build your integration following the product documentation.
  4. Test your integration following the product documentation.
  5. Submit your integration for Adobe’s review (the standard response time is 5 business days).
  6. 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.
  7. Once approved by Adobe, your integration will show up in the Experience Platform catalog.
  8. If you’d like to update your integration, follow the same process.

Reference

Adobe recommends that you read and understand the following Experience Platform documentation:

On this page