Skip to content

Analytics

Reach vs impressions vs views

These three numbers get used interchangeably in conversation and almost never match in a real analytics dashboard — because they measure genuinely different things. Reach counts unique accounts that saw a post; impressions count total times it was shown, including repeats to the same account; views is platform- and format-specific and often has its own qualifying threshold. This guide defines each term plainly and explains a quieter but common source of confusion: a platform reporting 0 for a metric is not the same as that platform reporting nothing for it at all.

All guides

By SkedCast Team · Updated · 5 min read

Key takeaways

  • Reach = unique accounts that saw the content at least once.
  • Impressions = total times the content was shown, including repeat views by the same account.
  • Views is the least standardized term — its definition (and minimum watch time to count) varies by platform and by content format on the same platform.
  • A metric reported as 0 means the platform measured it and the true count was zero; a missing or null metric means the platform did not report it for that post at all — treating the two the same silently hides real gaps in your data.
  • Meta has been consolidating "impressions" into "views" across its Instagram and Facebook APIs since early 2025 — a metric name that worked last year may not exist on the current API version.

Reach: unique accounts, counted once

Reach counts the number of distinct accounts that saw a post at least once in the measurement window, no matter how many times each one saw it. If the same 1,000 people each scrolled past your post three times, reach is 1,000.

Reach is the metric to watch when the question is "how many different people did this touch," which is usually the more useful number for judging how far content actually spread, as opposed to how much it was replayed to an already-reached audience.

Impressions: every time it was shown

Impressions count every time a post was displayed, including multiple times to the same account — a feed refresh, a Story replay, or an algorithmic resurface can all add another impression without adding a single new person to reach.

Impressions are always greater than or equal to reach for the same post and window; a large gap between the two usually means a smaller audience is seeing the content repeatedly, rather than the post spreading to new people.

  • Impressions ≥ Reach, always, for the same post and time window
  • A high impressions-to-reach ratio suggests repeat exposure to the same audience
  • A low ratio suggests the post reached mostly new accounts

Views: the least standardized of the three

Unlike reach and impressions, "views" has no single cross-platform definition. Video platforms typically require a minimum watch time or percentage of the content played before counting a view — and that threshold differs by platform and sometimes by content format on the same platform (a Reel and a feed video on the same app can use different view-counting rules).

Meta has been actively consolidating this: since early 2025 it has been deprecating the standalone "impressions" metric on Instagram in favor of a broader "views" metric across more content types. A metric name that worked in an older API version may return an error or an empty result on a newer one — check the platform’s own current API documentation rather than relying on a metric name that worked previously.

Zero vs null vs missing — a real and easy-to-miss distinction

A metric field holding the number 0 means the platform measured it and the real count was genuinely zero — a post that reached nobody in the window, for instance. A metric field that is null, absent from the response entirely, or returns an API error for that specific field means the platform did not report a value at all, for reasons ranging from insufficient data volume, a deprecated metric, insufficient permission scope, or the metric simply not applying to that content type.

Treating these the same — for example, defaulting every missing metric to 0 before displaying or summing it — silently turns "we don’t know" into "we know it was zero," which can understate an account’s real performance or mask a broken data pull rather than surfacing it. Any dashboard or report built on these numbers should be explicit about which case it is showing.

analyticsreachimpressionsviewsmetrics

FAQ

Why do reach and impressions never match for the same post?
Because they measure different things by design — reach counts unique accounts, impressions count total views including repeats. They would only match if every single account that saw the post saw it exactly once.
Which metric should I actually care about?
It depends on the goal: reach for measuring how far content genuinely spread to new people, impressions for measuring total exposure volume including repeats, and views specifically for video content where completion or watch-time matters.
Is a view the same thing as an impression for video content?
No — a view typically requires a minimum watch time or percentage played to count, while an impression counts as soon as the content is shown at all, regardless of whether it was watched.
Why did a metric that worked last year stop returning data?
Platform analytics APIs change metric names and availability over time — Meta’s ongoing consolidation of "impressions" into "views" on Instagram since early 2025 is a current example. Check the platform’s current API documentation rather than assuming an older metric name still works.
Does a 0 always mean the post genuinely had no reach?
Only if the platform actually reported the metric as the number 0. A null, missing, or errored field for that metric means the platform did not report a value at all, which is a different situation from a measured zero and should not be silently treated the same way.
Does this apply the same way across all 10 platforms SkedCast supports?
No — each platform’s analytics API defines and reports these metrics on its own terms, with its own quirks around missing data and deprecated fields. Treat this guide as the general vocabulary, and check each platform’s own current developer documentation for its specific behavior.

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.