Product Documentation
  1. Activate

Activate an Audience to DelivrDSP

Use Case

  • Push a saved audience to DelivrDSP 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 DelivrDSP integration (your account, set up once) and an export (which audience to push and how, pointed at that integration). Unlike a file export, a DelivrDSP destination delivers identifiers to a list in your DelivrDSP 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 DelivrDSP account: subdomain, account id, and login.

Steps

1. Create the DelivrDSP Integration

Create the destination once. Credentials are write-only: stored encrypted, never returned.

curl -X POST "https://api.delivr.ai/api/v1/integrations?project_id=YOUR_PROJECT_ID" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "X-Api-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "delivrdsp",
    "name": "DelivrDSP - Acme",
    "subdomain": "acme",
    "account_id": "10472",
    "username": "[email protected]",
    "password": "your-delivrdsp-password"
  }'

The response is the created integration. Note its id.

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

2. Create the Activation Export

Create an export that draws from your audience and activates to DelivrDSP. 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 - DelivrDSP",
    "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 DelivrDSP list in sync with the audience.

Destination Config Reference

FieldWhat it does
identifierWhat to push: hem, uid2, ip, or domain.
modeRefresh strategy. cumulative keeps adding to the list; regenerative replaces it each run. (incremental, which pushes only recent changes, applies to pixel sources, not audiences.)
lookback_daysWindow for incremental mode (1-365). Pixel sources only.
hem_scopeall_profile (default) or matched. Only applies to the hem and uid2 identifiers.
use_visitor_hemPixel sources only. Overrides hem_scope when set.
list_nameDelivrDSP list to write to. Defaults to the export name.

Picking a mode

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

A third mode, incremental (push only recent additions within a lookback_days window), is available for pixel-sourced exports, not audiences.

Notes

  • One call creates both the export and its destination. Create the integration first; the export references it by integration_id.
  • Credentials (username, password) are write-only. Responses return has_credentials: true.
  • DelivrDSP 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