Overview
The report focuses on programmatic-DSP advertising performance. It surfaces spend, impressions, click-through, and conversion metrics so teams can evaluate the efficiency of always-on programmatic investment without leaving the dashboard. Where a client runs more than one DSP, all of their in-scope DSPs appear together and the Metric Performance by Platform donut breaks spend down by platform. The Campaign dimension allows drill-down across the programmatic media mix.
Integrations Required
Any one of the following programmatic DSP feeds:
StackAdapt
The Trade Desk
Display & Video 360
Amazon DSP
Adelphic
Campaign Manager 360
MNTN
RTB House
A client sees the report if they have at least one of these connected, and the report shows data for every one of them that they run.
⚠️ Conversion tracking is configured per DSP, and not every DSP reports it. Spend, impressions, clicks, CPM and CTR are reliable for all in-scope DSPs. The Conversions and CPA cards, and the Conversions/CPA columns in Campaign Performance, only cover the DSPs that actually report conversions. Verified 2026-09-11:
DSP | Conversions reported? |
StackAdapt | Yes, on every client checked |
Display & Video 360 | On some accounts only — several large-spend accounts report none |
The Trade Desk | No — not currently delivered to the warehouse |
Campaign Manager 360 | No — not currently delivered to the warehouse |
Adelphic, MNTN, RTB House, Amazon DSP | No data flowing at time of check |
A blank or zero Conversions/CPA figure therefore means "this DSP does not report conversions", not "this campaign produced none". Spend for those DSPs is still counted in the Spend card, so a client running only The Trade Desk will see real spend alongside an empty CPA. Revenue and ROAS are not shown on this report for the same reason. Closing the Trade Desk gap is with Data Engineering.
⚠️ The riskiest case is a mixed view, where CPA computes but overstates. When the report covers a reporting DSP and a non-reporting one at the same time, CPA divides all their combined spend by only the reporting DSP's conversions. A worked example from live data: a client running StackAdapt ($237,803 spend, 31,215 conversions) alongside Campaign Manager 360 ($445,812 spend, 0 reported conversions) shows a blended CPA of $21.90, when the real StackAdapt CPA is $7.62 — a 2.9× overstatement, with no blank or zero to warn you. Use the Platform filter to isolate one DSP before judging efficiency.
Sections
Performance Overview: Period-over-period KPI cards covering Spend, Impressions, CPM, Clicks, CTR, Conversions, and CPA. This answers: "How is programmatic media performing versus the prior period?" and "Which efficiency metrics are improving or deteriorating?"
Metric Performance Over Time: Dual-axis trend chart showing the user-selected primary and secondary metrics across the analysis window. This answers: "How is the selected metric trending over the date range?" and "Do the primary and secondary metrics move in sync or diverge?"
Metric Performance by Platform: Distribution donut showing the selected additive volume metric broken down by DSP platform. This answers: "Which DSPs consume the most budget?" and "Where is the platform mix concentrated today?"
Note on drill-down dimensions. Use the Platform filter to isolate a single demand-side platform — the dropdown lists only the DSPs the selected client actually runs. The Account Name and Channel / Tactic filters are present but return no values for programmatic media (the underlying columns are not populated by the DSP feeds), so use Platform or Campaign instead.
Reading a blank CPA. CPA is intentionally left blank — not shown as $0.00 — when the DSPs in view report no conversions. See the conversion-tracking note under Integrations Required for which DSPs those are.
Campaign Performance: Detailed table of each programmatic campaign with Spend, Impressions, Clicks, CTR, CPM, CPC, Conversions, and CPA. This answers: "Which campaigns drive the most efficient conversions?" and "Which campaigns warrant deeper review or budget reallocation?"