At a glance
Sum of spend on StackAdapt campaigns that recorded zero conversions across the entire window. Campaign-level twin of Wasted Spend (which is placement-level). A whole campaign with zero conversions is a bigger problem than a bad placement; it usually means goal, audience, pixel, or creative are fundamentally misaligned. Excludes campaigns younger than 7 days to avoid penalising still-learning BidCore runs.
| What it counts | Spend (account currency) summed across campaigns where conversions = 0 AND clicks > 0 OR impressions > 1000 AND campaign_age >= 7 days. |
| Cost basis | Whatever the campaign was bidding on (CPM, CPC, BidCore CPA target). |
| Currency | Account currency. |
| Conversion attribution | Click-through + view-through. A campaign that drove activity which converted via another channel is zero-conv here unless StackAdapt’s pixel claimed it. |
| Attribution window | 30/1 default. |
| Bot / invalid traffic | IVT-filtered. |
| Time window | 30D. Campaigns younger than 7 days are excluded. |
| Alert trigger | >$0 on any campaign >7D old. Practical: any campaign with >$1,000 spent and zero conversions across 7+ days should be paused or fundamentally restructured. |
| Roles | owner, marketing, finance |
Calculation
Calculated automatically from your StackAdapt data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The same US homeware brand. Window 02 Apr 26 to 01 May 26.| Campaign | Channel | Age (days) | Spend ($) | Conversions | Status |
|---|---|---|---|---|---|
| Display Prospecting | Display | 84 | 12,400 | 142 | OK |
| CTV Awareness “Spring Living” | CTV | 28 | 18,200 | 22 (view-through) | OK |
| Native Article Distribution | Native | 102 | 5,400 | 84 | OK |
| Audio Spotify Sponsorship | Audio | 21 | 3,200 | 14 | OK (mixed) |
| Retargeting | Display + Video | 56 | 4,800 | 318 | OK |
| CTV “Outdoor Living” (test) | CTV | 18 | 1,400 | 0 | ZERO-CONV ALERT |
| Programmatic Audio test | Audio | 14 | 620 | 0 | ZERO-CONV ALERT |
| New Display Test (creative C) | Display | 4 | 280 | 0 | Excluded (<7d) |
| Total zero-conv (this card) | $2,020 | 0 | 4.6% of total spend |
- CTV “Outdoor Living” test ($1,400) is the bigger problem. 18 days, no conversions on a CTV view-through campaign suggests one of: (a) view-through window set to 1-day instead of 7 (a classic config error on test campaigns); (b) the conversion pixel isn’t tracking the right event; (c) the audience targeting is genuinely wrong. Action: check view-through window first (5-minute fix), then pixel config, then audience. Pause as last resort.
- Programmatic Audio test ($620) at 14 days zero-conv is borderline. Audio is structurally hard to attribute (no clicks; the user heard the ad while driving and bought a week later via Branded Search). The campaign may be working but credit is going to other channels. Action: check if Branded Search volumes ramped during the audio campaign window; if yes, the campaign is incremental despite zero StackAdapt-attributed conversions; classify as awareness and continue. If no, pause.
- The new Display Test (4 days old) is excluded by design. BidCore needs 7+ days to exit learning phase; flagging earlier creates noise.
- 4.6% zero-conv spend is on the borderline of healthy. Healthy DSP runs 2, 5%; 4.6% is at the upper end. Fixing the CTV view-through config alone would drop it to 1.4%, well within healthy.
- Don’t confuse this card with Wasted Spend. That one is placement-level; this one is campaign-level. The two should be read together: a healthy campaign can have wasted placements; a zero-conv campaign has structural issues.
- One campaign zero-conv with high impressions = pixel/goal misconfig OR audience mismatch.
- Multiple campaigns zero-conv simultaneously = global tracking outage; check pixel sitewide.
- CTV campaign zero-conv = check view-through window first (1d vs 7d) before anything else.
- Audio campaign zero-conv with rising Branded Search = working but incremental, not direct.
- Zero-conv campaign older than 30 days = past learning, no signal; pause and restructure.
Sibling cards merchants should reference together
| Card | Why pair it with Zero-Conversion Spend |
|---|---|
| StackAdapt Wasted Spend | Placement-level twin. Read both for full picture. |
| StackAdapt Clicks vs Conversions | The pixel-health canary. Healthy clicks + zero conversions = tracking issue. |
| StackAdapt Total Spend | Context. 44k account is yellow; same on $10k account is critical. |
| StackAdapt Conversions Trend | If account-wide conversions are also dropping, suspect a global tracking outage. |
| StackAdapt Conversion Actions | What conversion events does the campaign expect? Sometimes the campaign tracks an event the site doesn’t fire. |
| The Trade Desk Zero-Conversion Spend | If both DSPs show zero-conv, suspect site-side issue (pixel, checkout, goal config). |
Reconciling against the vendor’s own dashboard
Where to look in StackAdapt: StackAdapt → Reports → Campaigns, sort by Conversions ascending. Campaigns with zero conversions and >7 days of activity are the action set. StackAdapt does not surface “zero-conversion spend” as a single number; this card derives it. Why our number may legitimately differ from a manual cut:| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Account TZ vs UTC. |
| Long-tail conversion | Card slightly high | A campaign labelled zero-conv today may pick up 1, 2 conversions in days 7, 14. The 7-day age threshold mitigates but doesn’t eliminate. |
| View-through window changes | Direction depends | If view-through is set too short for CTV, more campaigns appear zero-conv than would otherwise. |
| Campaign age threshold | None | Both this card and a reasonable manual analyst cut would exclude <7-day campaigns. |
| Pixel + server-side dedup | None | StackAdapt dedupes pixel and server-side events. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
the_trade_desk.the_zero_conversion_spend | Independent. If both fire simultaneously, suspect site-side issue. | Different campaigns. |
google_analytics.ga_revenue_by_channel | Zero-conv campaigns should still show GA4 sessions if pixel fire is the issue. | If GA4 sessions present but no DSP attribution, the DSP pixel is broken. |
shopify.total_revenue | Zero-conv on DSP doesn’t mean zero Shopify revenue; conversions may be credited to other channels. | Multi-touch attribution complicates the read. |