Generate shareable performance reports

An agency wrapping up a month-long festive campaign for a retail client needs to hand over a proper summary — what went out, how it performed, the top posts — and the alternative is an account manager spending an evening screenshotting posts into a slide deck, hoping nothing's misquoted before the client opens it.

Campaign reporting groups posts under a named campaign and produces a report with a performance chart, top posts and combined metrics across platforms for a chosen date range, exportable as a PDF or shareable through a read-only link. The report carries the client's own branding rather than Socie's, because a client-facing deliverable needs to look like it came from the agency — and because a shared link is effectively a public URL the moment it exists, it needs to be genuinely revocable, not left open once the campaign is long over.

A shared read-only link is, functionally, a public URL from the moment it's generated — anyone who has it can open the report, intended recipient or not, unless it carries genuine access control. This is why sharing needs a revocable token and optional expiry built in from the start, not added once a link has already been forwarded unintended. An agency finishing a client engagement should revoke that client's old report links as part of offboarding, rather than leaving months-old data accessible at a forgotten URL.

The numbers inside a report have to reconcile with the underlying analytics data a client could check independently. If a report's totals don't match a client's own spot-check — because it was generated from a stale cache, or metrics had settled further by the time they looked — the report loses credibility precisely when it's meant to build it. A report generated too soon after a campaign ends risks this, since some metrics keep settling for days after a post goes live.

For an agency managing several clients, the branding requirement isn't cosmetic — it's core to the report's purpose. A retail client paying for campaign management expects a deliverable reading as coming from that agency, and different branding undermines the relationship, however accurate the numbers are. Cross-client boundaries matter too: a report for one client must never surface another's data, so generation needs the same access scoping as everything else in a shared workspace.