Sponsored Conversations Analytics
Advertiser-facing rollup for the campaigns the API key’s tenant owns: summary KPIs, daily timeline, plus per-campaign, per-prompt, and click-type breakdowns. Numbers match the Dappier platform dashboard for the same filters.
X-RateLimit-* headers are returned, 429 with Retry-After when exceeded) and cached server-side for up to 30 minutes (send Cache-Control: no-cache to skip the cache read; the X-Cache response header reports HIT, MISS, BYPASS, or DISABLED).Authorizations
Bearer token authentication using your Dappier API key. Get your API key at https://platform.dappier.com/profile/api-keys.
Query Parameters
Inclusive start of the analytics window, formatted YYYY-MM-DD (UTC). Optional — if either start_date or end_date is omitted, both default to the trailing 7-day window ending today_UTC (i.e., start_date = today_UTC - 6).
"2026-04-01"
Inclusive end of the analytics window, formatted YYYY-MM-DD (UTC). Optional — if either start_date or end_date is omitted, both default to the trailing 7-day window ending today_UTC. Must be on or after start_date; the total range must be ≤ 365 days.
"2026-04-30"
External campaign id (e.g. cp_...).
"cp_xxx"
AI model external id (e.g. am_...). Validated against the tenant — an unknown or other-tenant id returns 400 agent_id not found.
"am_01j06ytn18ejftedz6dyhz2b15"
External placement id.
External prompt id (e.g. pm_...).
DSP-served ad creative id (GAM/Dianomi) that triggered the sponsored conversation.
"391487"
DSP-served line item id.
Publisher id. Present on Dianomi-served events only — filtering by this scopes results to Dianomi-derived traffic.
Response
Sponsored-conversation rollup for the requested window and filters.
Always true for a 200 response.
true
Echoes back only the filters you supplied in the request.
Rollup for the window. Internally self-consistent; percentages rounded to 2 decimals.
Mirrors the dashboard "Performance Timeline".
Per-campaign rollup, sorted by impressions desc. creative_ids is the list of DSP creative IDs configured on the campaign (from campaign setup, not per-event data) — use it to cross-reference your DSP/ad-server reports.
Top rows by engagement, grouped by prompt text (not prompt id). Configured sponsored prompts appear with impressions > 0; user-typed follow-ups inside the SC appear with impressions == 0 and queries > 0. prompt_id is currently always "" (reserved for a future release).
One entry per click type present.

