To spend less time compiling campaign reports, decide before launch what the report has to answer, let software collect the same numbers for every post and compare each account with its own usual results, and keep your own time for the one decision the report exists to make: what the next campaign does differently.
Compiling is the part that can go. Finding the posts, exporting each platform's numbers, lining up dates, and building the slides are mechanical. Deciding what the numbers mean for the next brief is not, and it is the part that gets squeezed when compiling eats the afternoon.
This page is the short answer. The step-by-step setup is in how to set up a campaign reporting workflow, and the method for reading the numbers is in how to turn campaign results into a report.
Where the time goes
Most of the hours in a campaign report are spent before any thinking happens:
- Reconstructing the campaign. Working out after the fact which posts, emails, and pages belonged to it.
- Collecting. Logging into each platform, exporting, and copying numbers into one sheet.
- Normalizing. Making rates comparable when each platform counts views and engagement differently.
- Formatting. Turning the sheet into slides or a document someone will read.
- Re-litigating scope. Arguing about which dates and accounts count, because nobody wrote it down.
Each of these is either avoidable with planning or repeatable by software.
Five changes that cut the compiling
1. Write the question and the scope before launch
One question ("did carousels get more saves than single images on Instagram during the launch?"), the dates, the accounts, and the metric that answers it. A report with a written question has an obvious end. A report without one keeps growing.
2. Link the work to the campaign as you make it
Tag or link every post to the campaign when it is drafted, not when the report is due. The report then starts from a list instead of a search.
3. Let a tool pull the same fields for every post
Platform, date, format, opening line, length, views or reach, interactions, and engagement rate, for every post, every time. Copying these by hand is the slowest part of the report and the most error-prone.
4. Compare each account with its own baseline
An Instagram rate and a LinkedIn rate are not the same measurement. Comparing each post with the median of its own account's recent posts removes the normalizing step and gives a fairer answer. Mark missing numbers as unknown, never as zero.
5. End with one decision, written where the next brief will see it
A list of top posts is a scoreboard. Finish with what to keep, change, stop, and one test for next time, with the metric that will decide it. Put it in the next campaign's brief or notes, not in a slide deck nobody opens again.
What to automate and what to keep
| Automate | Keep with a person |
|---|---|
| Collecting metrics for every post | Choosing the question the report answers |
| Comparing each post with its account's usual results | Deciding whether a pattern is worth acting on |
| Flagging patterns and how many posts support each | Weighing results against things the data cannot see, such as a launch delay |
| Listing missing data | Choosing the change for the next campaign |
| Drafting the written summary | Approving what goes into the next brief |
A tool can tell you that question openers ran above your usual on one account. It cannot tell you whether that was the opener or the week a competitor went quiet. Keep that judgement with whoever owns the campaign.
How this works in Daoco
Daoco is our product. This is what it does, from its documentation.
- Campaign analytics combines the results of the posts linked to a campaign, and Refresh requests the latest numbers each platform will return. See Campaigns.
- /performance-review in brand chat refreshes the metrics for recent posts on each connected account, compares each rate within its own account, cites the posts behind every finding, and calls a pattern from too few posts a guess. It ends with what to keep, change, and stop, plus one test and the metric that decides it. An account it cannot read is listed as a gap.
- What's working is a brand document Daoco keeps current from your results, with no approval, one section per channel. Social lines compare a group of posts with that platform's median and need at least 8 posts before a pattern counts as a learning; email lines come from Mailchimp, Ghost, Kit, beehiiv, MailerLite, and Klaviyo results. See What's working.
- Automations can run /performance-review on a schedule, such as every Monday morning, and report to Daoco or your assistant. See Automations.
- The decision goes into the campaign. In a chat attached to the campaign, ask Daoco to add the decisions and the test to the campaign's Notes, and tell it to read the notes first so it keeps what is there.
Limits to know
- Metrics depend on each platform's API and the permissions you granted. Some arrive late, and a platform error leaves the last successful snapshot in place.
- Social engagement is not revenue. If the report has to answer for pipeline or sales, keep those source reports beside it.
- This flow covers organic social. Ad spend has its own review, /ads-review, on connected Google, Meta, and TikTok Ads accounts.
To try the comparison on your own accounts before signing up, the free social Wrapped tool connects up to three accounts, one per platform, and compares each with its own median.
Questions to ask any reporting tool
- Does it compare each account with its own baseline, or average across platforms?
- Does it show how many posts support each finding?
- Does it mark missing data as unknown?
- Can it run on a schedule and put the result where the team plans the next campaign?
- Does reporting cost extra on top of the plan you need?
Reporting depth often depends on the plan. The reporting table in content workflow platforms for small marketing teams shows which plans include analytics for Planable, StoryChief, CoSchedule, HubSpot, Buffer, Hootsuite, and Daoco. For side-by-side comparisons, see Daoco vs Hootsuite and Daoco vs Sprout Social.