Twitter Stats: Read the Numbers in Context

Choose posting-history statistics or collected public-post counters, then check the source and date before comparing results.

Which stats do you need?

Use archive upload insights for personal posting volume, active days and counts derived from your X export. Use paid public-profile collection for available stored likes, reposts, replies and view counts. These workflows use different sources and should be labeled separately in a report.

Read follower counts carefully

A follower list in an uploaded archive describes the snapshot in that file. Paid profile analytics can show counts recorded in profile snapshots over time. Neither source reconstructs every historical follow or unfollow.

For example, a change between two observed counts does not reveal which post caused it. Keep the two snapshot dates beside the result.

Make a fair period comparison

1. Choose matching start and end dates.
2. Check whether the sample contains posts throughout that period.
3. Use the same interaction definition for both periods.
4. Record collection dates: counters can change after collection.
5. Describe gaps before explaining an apparent trend.

Take the next step with the right data

Upload your personal ZIP for a free summary and activity heatmap. Paid plans add further aggregate charts. For searchable records and CSV, XLSX or JSON exports, use a paid collected archive. Exports contain at most 50,000 records each.

Choose the next step

Archive upload insights · Public-post collection · Plans and limits · Screenshot maker