An exposure count tells you how often a post was recorded as viewed or shown under a particular definition. It does not necessarily tell you how many different people saw it, read it carefully or acted on it.
Distinguish the main counts
| Term | Meaning | Do not infer |
|---|---|---|
| Native impressions | Exposures reported by a specific X analytics surface | A count of unique people |
| Public post views | Views displayed on an eligible post under X’s rules | Every private analytics field |
| Reach | A source-defined unique audience measure | That it equals summed views or follower counts |
| Engagements | Actions included by a report | That every action came from a different person |
Account for repeat views and missing data
X explains that repeat viewing can contribute to public view counts. A count of 200 views therefore does not establish 200 different readers. Some posts do not expose the same counts, and collection can fail.
Record the source and capture date. Do not replace unavailable unique reach with a public view count or treat missing views as zero.
Connect exposure to actions
Hypothetical example:1,000 recorded views and 30 public interactions gives a 3% actions-per-view rate. It does not establish that 3% of unique readers acted. Some people may view or act more than once.
For website goals, use separate visit or conversion tracking. A view is not a link click, and a click is not necessarily a completed visit or purchase.
Compare over time
Use the same source, post types and observation window. Keep totals beside sample sizes and typical per-post results. Avoid a fixed claim that a particular fraction of followers should see every post.
Tweet Archivist stores available public view counts for captured profile posts. It does not recover complete private impression history for arbitrary accounts. For diagnosing a change, read the exposure troubleshooting guide; for calculations, see engagement-rate formulas.
Sources and checks
Reviewed October 16, 2026. View counts.