DocumentationTutorialsUse Cases & Blueprints

Set up streaming destination

Last update: September 11, 2026

CREATED FOR:

  • Developer
  • User
NOTE
Skip to the next step if you have already configured your streaming destination!

Get webhook URL

NOTE
We are going to use a webhook here so we can see if the data has arrived at the Destination we are sending to. In a real world scenario, we would log into that destination instead and use their tools to see what has arrived.
  1. Open the following link in a new tab in your browser -> https://webhook.site
  2. Copy the unique URL you see and save it somewhere safe

Webhook.site copy your unique URL

Configure HTTP API destination

NOTE
We are using a Streaming Destination as a proxy for sending this data to a 3rd party (e.g. Facebook). In a real world scenario, you would use a Facebook Destination in place of an HTTP API Destination to send data to Facebook.

In the Experience Platform UI navigate to the destinations catalog by doing the following

  1. Click on Destinations in the left rail
  2. Click on Catalog on the top rail
  3. In the search box enter http
  4. Click on the Set up button to configure the HTTP API destination

Navigate to the HTTP API destination and initiate the setup

NOTE
You are using the HTTP API streaming destination for the lab(s) to demonstrate how a real world streaming connector would work.

Configure

  1. Connection type None

  2. Click on Connect to destination

    Connect to destination

    note
    NOTE
    Typically we would add any authentication credentials at this stage, but none are required for this webhook.

  3. Fill in the configuration details of your destination as follows:

  • Name -> Streaming DEP Webhook - [Your Initials]
  • Description -> [your webhook endpoint you copied above]
  • Endpoint -> [your webhook endpoint you copied above]
  • Query Parameters -> leave blank
  • Headers -> leave blank
  • Include segment names -> toggle on
  • Include segment timestamps -> toggle on

When done ensure your configure matches what you see below. If it looks good click the Next button in the upper right to continue to the next step

Configure destination fields including name, description, endpoint, and toggles

CAUTION
The endpoint, header and query params cannot be changed in the UI once saved

Define governance

  1. Select Cross Site Targeting from the Marketing Actions
  2. When done click the Next button to continue to the next step

Governance screen for destinations

NOTE
You can learn more about governance policies in Experience League
https://experienceleague.adobe.com/docs/experience-platform/data-governance/policies/overview.html?lang=en#core-actions

Select Audiences

  1. Select all audiences
  2. When done click the Next button to continue to the next step

Select all audiences

Add mappings

NOTE
Here we are adding a field from Profile. If that field has no data, we may see nothing passed to the Destination. Multiple updates over time across Profile and Events sometimes can cause the Destination to trigger multiple times and send multiple payloads.
  1. Click on Add new field to add a field to the schema
  2. Type model into the schema field input box and select the _dep.activeProducts[0].model field from the list of fields that appears
  3. Change the [0] to [*] in the field name. Your final field should now show as _dep.activeProducts[*].model
  4. When done click the Next button to continue to the next step

Select Model Field

Final Model Field

NOTE
This is mapping a field on Profile, not Experience Event. Even though we are sending profiles to a Destination based on Audience Qualification, we have to keep in mind what is happening.
  1. An event comes in
  2. Audience qualifies the Profile based on rules
  3. Qualification is stored on the Profile
  4. The Destination is notified the Profile has qualified
  5. The Destination sends the Profile. What this means is when the Destination goes to send the Profile it no longer has awareness of the Event that triggered the Audience evaluation.

Review step

Validate your final destination looks good and then click the Finish button

Destination review screen

NOTE
The destination is now configured and waiting for segment qualifications from all the segments added based on their evaluation speeds:
  • Edge
  • Stream
  • Batch
NOTE
When initially setting up a Destination the following are important to remember:
  • It takes up to 2hrs for any backfill (existing qualified profile) to start activating
  • It takes up to 20mins for a newly added audience to start activating
recommendation-more-help
blueprints-learn-help-blueprints