Activate an Audience to Delivr DSP

Use Case

• Push a saved audience to Delivr DSP for programmatic ad targeting
• Keep the activated list fresh by re-running on a schedule
• Choose the identifier and refresh strategy that fit your campaign

Activation has two parts: a Delivr DSP integration (the project's Delivr DSP account) and an export (which audience to push and how, pointed at that integration). Unlike a file export, a Delivr DSP destination delivers identifiers to a list in your Delivr DSP account rather than writing a file.

Prerequisites

• Organization API key + secret pair (Authentication). Create one at https://app.delivr.ai/{org_id}/settings/api-keys.
• A project id (the workspace the export lives in).
• An audience id to activate (Intent Audiences API).
• A Delivr DSP integration in that project. Every new project gets one automatically, so you do not need Delivr DSP credentials. Step 1 finds it.

Steps

1. Get the Project's Delivr DSP Integration

curl "https://api.delivr.ai/api/v1/integrations?project_id=YOUR_PROJECT_ID&type=delivrdsp" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "X-Api-Secret: YOUR_API_SECRET"

The response lists the project's Delivr DSP integration. Note its id.

[
  {
    "id": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
    "project_id": "YOUR_PROJECT_ID",
    "type": "delivrdsp",
    "name": "DelivrDSP",
    "has_credentials": true,
    "enabled": true,
    "created_at": "2026-06-25T18:00:00Z",
    "updated_at": "2026-06-25T18:00:00Z"
  }
]

If the list is empty, the project was created before Delivr DSP was set up automatically. A project admin can set it up in the dashboard:

1. In the project, open Activate > Connections. Click Add Connection and select Delivr DSP.
2. Click Set up Delivr DSP. The page opens the integration when it is ready.

Run this step again to get the id. If you cannot use the dashboard, contact support.

2. Create the Activation Export

Create an export that draws from your audience and activates to Delivr DSP. The destination selects the identifier and refresh mode.

curl -X POST "https://api.delivr.ai/api/v1/exports" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "X-Api-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "project_id": "YOUR_PROJECT_ID",
    "name": "Acme prospecting - Delivr DSP",
    "query": {
      "sourceType": "audience",
      "sourceId": "YOUR_AUDIENCE_ID"
    },
    "schedule": "daily",
    "run_time": "06:00",
    "destination": {
      "type": "delivrdsp",
      "integration_id": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
      "identifier": "hem",
      "mode": "cumulative",
      "list_name": "Acme prospecting"
    }
  }'

The response contains the export and its destination. The export runs daily at 06:00 UTC and keeps the Delivr DSP list in sync with the audience.

Destination Config Reference

Picking a mode

• cumulative - grow a list over time. It is good for ongoing prospecting.
• regenerative - the list should exactly mirror the audience each run. It is good when membership changes both ways.

A third mode, incremental, keeps visitors seen within lookback_days and removes the others each run. It is available for pixel-sourced exports, not audiences.

Notes

• One call creates both the export and its destination. The export references the integration from step 1 by integration_id.
• Delivr DSP responses use the delivrdsp type throughout. You never need to reference the underlying provider.
• lookback_days outside incremental mode returns 400.
• The project_id and integration_id must both belong to your key's organization.

Next Steps

• Integrations API: list Delivr DSP integrations, and create and manage S3 destinations
• Exports API: create, list, get, update, and delete exports
• Export an Audience to S3, Email, or Slack: file-based delivery instead of activation
• Intent Audiences API: build the audiences you activate