Documentation Experience Platform Destinations Guide

Destination delivery

Last update: September 9, 2026

CREATED FOR:

User
Admin

To offer more control over where the data exported to your destination lands, use Destination SDK to specify destination delivery settings.

The destination delivery section indicates where the exported data goes and what authentication rule is used in the location where the data will land.

To understand where this component fits into an integration created with Destination SDK, see the diagram in the configuration options documentation or see the following destination configuration overview pages:

You can configure destination delivery settings via the /authoring/destinations endpoint. See the following API reference pages for detailed API call examples where you can configure the components shown in this page.

This article describes all the supported destination delivery options that you can use for your destination.

IMPORTANT

All parameter names and values supported by Destination SDK are case sensitive. To avoid case sensitivity errors, use the parameter names and values exactly as shown in the documentation.

Supported integration types supported-integration-types

See the table below for details on which types of integrations support the functionality described on this page.

Integration type

Supports functionality

Real-time (streaming) integrations

Yes

File-based (batch) integrations

Yes

Supported parameters supported-parameters

When configuring your destination delivery settings, you can use the parameters described in the table below to define where the exported data should be sent.

Parameter

Type

Description

authenticationRule

String

Indicates how Experience Platform should connect to your destination. Supported values:

CUSTOMER_AUTHENTICATION: Use this option if Experience Platform customers sign in to your system via any of the authentication methods described in the customer authentication documentation.
PLATFORM_AUTHENTICATION: Use this option if there is a global authentication system between Adobe and your destination and the Experience Platform customer does not need to provide any authentication credentials to connect to your destination. In this case, you must create a credentials object using the credentials API configuration and set the authenticationId parameter to the credential object ID value.
NONE: Use this option if no authentication is required to send data to your destination platform.

authenticationId

String

The instanceId of the credential object’s configuration ID to use for authentication. This parameter is only required when you need to specify a particular credentials configuration.

destinationServerId

String

The instanceId of the destination server that you want to export data to.

deliveryMatchers.type

String

When configuring destination delivery for file-based destinations, always set this to SOURCE.
When configuring destination delivery for a streaming destination, the deliveryMatchers section is not required.

deliveryMatchers.value

String

When configuring destination delivery for file-based destinations, always set this to batch.
When configuring destination delivery for a streaming destination, the deliveryMatchers section is not required.

Destination delivery settings for streaming destinations destination-delivery-streaming

The example below shows how the destination delivery settings should be configured for a streaming destination. Note that the deliveryMatchers section is not required for streaming destinations.

{
   "destinationDelivery":[
      {
         "authenticationRule":"CUSTOMER_AUTHENTICATION",
         "destinationServerId":"{{destinationServerId}}"
      }
   ]
}

style

shade-box

Destination delivery settings for file-based destinations destination-delivery-file-based

The example below shows how the destination delivery settings should be configured for a file-based destination. Note that the deliveryMatchers section is required for file-based destinations.

{
   "destinationDelivery":[
      {
         "deliveryMatchers":[
            {
               "type":"SOURCE",
               "value":[
                  "batch"
               ]
            }
         ],
         "authenticationRule":"CUSTOMER_AUTHENTICATION",
         "destinationServerId":"{{destinationServerId}}"
      }
   ]
}

style

shade-box

Platform authentication configuration platform-authentication

When using PLATFORM_AUTHENTICATION, you must specify the authenticationId parameter to link your destination configuration to the credentials configuration.

Set destinationDelivery.authenticationRule to "PLATFORM_AUTHENTICATION" in your destination configuration.
Create the credential object.
Set the authenticationId parameter to the credential object’s instanceId value.

Example configuration with platform authentication

The example below shows a destination delivery configuration that uses PLATFORM_AUTHENTICATION.

{
   "destinationDelivery":[
      {
         "authenticationRule":"PLATFORM_AUTHENTICATION",
         "authenticationId":"<string-here>",
         "destinationServerId":"<string-here>"
      }
   ]
}

style

shade-box

Next steps next-steps

Next, configure the other destination components. To learn more, see the following articles:

recommendation-more-help

experience-platform-help-destinations