Skip to main content
Campaigns, under Intelligence in the sidebar, groups the work behind a single initiative so it can be reviewed and reported on as one thing. A campaign is a grouping, not a container. It links to records the rest of the product already owns — the brief that started the work, the pieces themselves, the calendar entries scheduling them, the approvals gating them, and the claims standing behind them. Nothing is copied, so a piece edited in Studio is the same piece the campaign reports on.

​
What can be linked

A link is only accepted if the record exists and belongs to you, so a campaign cannot accumulate references that were never valid.

​
The rollup

The rollup resolves every linked record and aggregates what has actually been measured.
Performance figures come from the ContentPerformance rows the publishing integrations wrote. Content with no measurements contributes nothing and is counted separately — a campaign of ten pieces where two are published reports “2 of 10 measured”, not ten pieces averaging near zero.
Engagement rate is recomputed from the summed totals rather than averaged across platform rows, so a platform with ten views does not count equally against one with ten thousand.

​
Records that no longer exist

Each link stores a label snapshot taken when it was made. If the record it points at is later deleted, the rollup reports it under dangling using that label, and states how many records the totals were computed from. This is deliberate. Silently skipping unresolved links would make a campaign’s measured performance fall when someone deletes a draft, and a vanished row would be indistinguishable from the campaign genuinely performing worse.

Content Requests

The intake that usually starts a campaign’s work.

Experiments

Test a variant of a piece inside a campaign.
Last modified on August 30, 2026