Campaign-only revenue over time. This line is spiky by design: each broadcast is a peak, and the gaps between sends are the flat valleys.
At a glance
Campaign Revenue Trend plots Klaviyo-attributed revenue from broadcast campaigns only, excluding always-on flows. Because campaigns fire on your schedule rather than on customer behaviour, this line is naturally spiky: each send creates a 1 to 5 day peak as its attribution window plays out, then falls back toward zero until the next send. That is the opposite of the steady flow baseline. Use this card to judge campaign cadence and tentpole performance, and read it next to Flow vs Campaign Revenue Mix to see how much of total Klaviyo revenue your broadcasts actually carry. Like all Klaviyo revenue, it is gross of refunds.
| What it counts | Klaviyo-attributed revenue from campaigns only, per day. Flow revenue is excluded, so the line falls to (or near) zero between sends. |
| API endpoint + statistics field | POST /api/campaign-values-reports reading the revenue statistic, aggregated per day. Flows are deliberately not included. |
| Attribution model | Klaviyo default: 5-day click-through plus 1-day view-through on the Placed Order event. Revenue is credited to the order date, which is why a single send produces a multi-day spike. |
| Email vs SMS aggregation | Combined. Campaign revenue blends email and SMS campaigns unless filtered by channel in Klaviyo. |
| Refunds / cancellations | NOT deducted. Campaign revenue is recorded gross at order time; a later refund is never subtracted from this line. |
| Chart type | Line (time-series, one point per day), spiky by nature. |
| Time window | Selected period (default 30 days), one data point per day. |
| Alert trigger | Decline in peak height for comparable sends versus the prior period, or unexpected flat stretches where sends were scheduled. |
| Roles | owner, marketing |
Calculation
Calculated automatically from your Klaviyo data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
An illustrative coffee subscription brand on BigCommerce using Klaviyo for campaigns and flows. The 30-day window covers 14 Mar 26 to 12 Apr 26. Figures are illustrative.| Campaign (illustrative) | Send date | Recipients | Campaign revenue |
|---|---|---|---|
| New roast launch | 17 Mar 26 | 48,000 | £9,800 |
| Mid-month restock | 26 Mar 26 | 51,000 | £6,400 |
| Easter weekend offer | 4 Apr 26 | 53,000 | £18,200 |
| Last-chance Easter | 8 Apr 26 | 49,000 | £7,100 |
| Window total (campaigns only) | £41,500 |
- Four sends, four peaks. Between sends the line drops toward zero because flows are excluded from this card. The valleys are expected, not a failure.
- The Easter weekend send is the tentpole. At £18,200 it dwarfs the routine restock. Concentrated, well-timed moments outperform high-frequency filler sends. This is Klaviyo’s strongest campaign pattern.
- Peaks last several days. The 4 Apr send keeps adding revenue through 8 Apr because of the 5-day click window, which is partly why the last-chance send on 8 Apr looks smaller: some of its early credit overlaps the tail of the previous peak.
- Compare like for like. The new roast launch (£9,800) and the restock (£6,400) had similar audiences but different revenue, pointing to creative and offer strength rather than reach. Use Revenue per Send to make that comparison cleanly.
- This is gross. If the Easter offer drove returns the following week, this line would not reflect it. Refunds are tracked separately and are not deducted here.
Sibling cards merchants should reference together
Read these alongside Campaign Revenue Trend to compare individual sends and to weigh campaigns against flows.| Card | Why pair it with Campaign Revenue Trend |
|---|---|
| Top Campaigns by Revenue | Ranks the individual sends that create the peaks in this line. |
| Flow vs Campaign Revenue Mix | Shows what share of total Klaviyo revenue these campaign spikes actually carry versus the flow baseline. |
| Email-Attributed Revenue | The all-source total. Campaign revenue is one component of it. |
| Revenue per Send | Normalises each peak by audience size so you can compare campaign efficiency fairly. |
| Send Cadence | Explains the spacing of the spikes and flags over- or under-sending. |
Reconciling against Klaviyo
Where to look in Klaviyo: Open Analytics → Campaigns and set the same date range with the Revenue column shown. Summing the per-campaign revenue across the window reproduces this line’s total. The Analytics → Performance dashboard also lets you isolate Campaigns from Flows to see the same campaign-only shape. Why our number may legitimately differ:| Reason | Direction of divergence |
|---|---|
| Time zone. Klaviyo aggregates in the account time zone; Vortex IQ defaults to UTC. A peak can shift by a day at the boundary. | Peak appears one day earlier or later |
| Page caps. Campaign reports paginate at 50 per call. Accounts sending more than 50 campaigns in the window may see truncated totals. | Vortex IQ marginally lower for very high-cadence senders |
| Attribution-window changes. Changing the conversion-tracking window mid-period re-attributes peaks differently between snapshots and a live read. | Small drift on changed-window accounts |
| Currency base. Klaviyo normalises to the account base currency with no live FX. | None; consistent |
| Refunds gross. Both Klaviyo and this card carry campaign revenue gross of refunds. | None |
| Flow exclusion. If you compare this card to Klaviyo’s all-source Performance number, this card will be lower because flows are excluded by design. | Expected; not an error |