Quick answer
Reach estimates people or accounts exposed; impressions count display opportunities; views count platform-defined consumption events; watch metrics describe depth of consumption; engagement records audience actions. Platform definitions and availability differ, so preserve the original metric, source, and window before normalizing any cross-platform summary.
Use this guide when interpreting creator analytics screenshots, combining results across platforms, or explaining why one top-line exposure number cannot be compared blindly with another.
What matters most
Unique reach is usually modeled or platform-reported and cannot be added across creators without double-counting shared audience. Sum it only when the source explicitly deduplicates.
A view threshold, autoplay behavior, loop, and eligible placement can differ by platform and format. Keep short-form, long-form, story, livestream, and feed consumption distinct.
Engagement mixes actions with different effort and meaning. Comments, saves, shares, clicks, reactions, follows, and chat participation should remain available beneath any total.
A practical workflow
- 01
Record the exact platform label and definition for every imported metric.
- 02
Capture the content age and reporting window.
- 03
Keep format-specific consumption metrics separate.
- 04
Calculate rates only with a defensible denominator from the same source and window.
- 05
Aggregate cross-platform results with caveats and component metrics visible.
Why reach does not add up
Reach estimates unique people. Adding one creator's reach to another's assumes the two audiences share nobody, and in any well-constructed campaign the opposite is true: creators selected for the same audience will have been watched by many of the same people.
The overlap is largest exactly where campaigns concentrate, among creators in the same niche who collaborate and share a community. So the summed total is most wrong in the cases where it is quoted most confidently, and it can overstate genuine unique reach substantially with no way to tell from the number itself.
Report impressions when you want a total, since impressions are display opportunities and adding them is legitimate. Report reach per creator, and where a campaign-level unique figure is genuinely needed, it has to come from a source that deduplicates across creators. If nothing does, say so rather than adding.
Every metric has an age
Platform metrics accumulate, at wildly different rates by format. Short-form content front-loads almost everything into the first days. Long-form video on a search-driven platform can still be gaining views a year later. Livestream metrics stop the moment the broadcast ends.
This means a snapshot taken on reporting day compares content of different ages, and the resulting ranking partly measures who published first. The creator who published on day one of a four-week campaign is being credited with four weeks of accumulation against someone who published last Thursday.
Fix it by measuring from each post's own publication time at a fixed age, and label every figure with that age. Where you must show a same-day snapshot, show the content age in the same row. The discipline sounds pedantic and it is the difference between a comparison and a coincidence.
Presenting a cross-platform total honestly
Someone will always ask for one number across every platform, and refusing is not a useful answer. The honest version is possible; it just requires the components to stay visible.
Present the total as a sum of clearly labelled parts, each with its platform, its metric name as that platform defines it, and its measurement window. Add a plain sentence saying these counts are not equivalent units and the total is indicative rather than a count of anything. That sentence costs one line and prevents the number being quoted later as a measurement.
Then give the reader something that actually is comparable underneath: the outcomes measured in your own systems. Clicks, sessions, conversions and code redemptions are counted the same way regardless of which platform sent them, which makes them the only genuinely cross-platform figures in most campaign reports.
Common mistakes
- Adding creator-level reach and calling the sum unique people.
- Treating every platform view as the same amount of attention.
- Combining high-effort and low-effort actions into one unexplained engagement total.
- Comparing lifetime metrics with seven-day metrics.
Working checklist
- Original platform definitions are preserved.
- Content age and window are consistent or labeled.
- Format and placement differences remain visible.
- Rates share source, scope, and denominator.
- Cross-platform totals disclose non-equivalence and overlap.
Questions and answers
- Can you compare views between platforms?
- Not directly, because each platform defines a view differently, counts autoplay and loops differently, and applies different thresholds by format. A view on one platform can represent a second of muted autoplay and on another a deliberate click into long-form content. Compare outcomes measured in your own systems and keep platform counts labelled by source.
- What is a good view-through or completion rate?
- It depends entirely on format and length, and cross-format comparison is meaningless: a fifteen-second clip and a twenty-minute video are not measuring the same behaviour. Build your own benchmark from comparable content you have run, and compare a creator against their own median rather than against a published figure of unstated provenance.
- Should you report one total reach number?
- Only if the source deduplicates across creators, which most do not. Summed per-creator reach double-counts everybody who follows more than one creator in your campaign, and that overlap is largest in exactly the tightly-matched rosters campaigns aim for. Report impressions for a total, reach per creator, and say plainly when a deduplicated figure is not available.
- Why do platform figures differ from third-party ones?
- Because they measure different things by different methods. Platform analytics see the actual delivery; third-party tools estimate from public signals; creator screenshots show a specific view of a specific window. None is simply correct. Record the source alongside every figure and never average across sources, which produces a number that describes no measurement at all.
Sources and verification
Written by Nick Lombardi, Co-Founder & CTO, Streamforge. Published September 2, 2026; last verified September 2, 2026. Platform rules change, so confirm details against the primary sources below.

