Twitter Statistics: Build a Reproducible Report

Document the sample, time period and available fields before turning archive data into a statistics report.

Choose the dataset

An uploaded X ZIP provides aggregate account and posting statistics from the files it contains. A paid collected archive provides stored public posts and available counters. Do not combine these as if they were the same dataset.

Choose the source that fits the question. Posting volume can describe activity; it does not by itself measure impact, conversions or unique reach.

Write a short methods note

• Account handles or input post URLs.
• Source type: uploaded archive or public collection.
• Requested and observed date range.
• Collection date and applied filters.
• Metric definition and denominator.
• Known gaps and unavailable fields.

Check changes over time

Compare periods with similar coverage and avoid interpreting missing posts as inactivity. Interaction counters can grow after collection. Follower counts are snapshots, so changes before the first snapshot cannot be reconstructed from later counts.

Weekly profile updates are periodic collection. They do not provide real-time statistics or guarantee that posts removed between runs were captured.

Make a useful handoff

For a paid collected archive, export the filtered sample as CSV, XLSX or JSON, up to 50,000 rows per export. Keep the methods note with the file. Upload insights are an aggregate dashboard rather than a collected-record export.

For a client or research report, add other first-party metrics only after checking matching periods and definitions. Read the metric selection guide for denominator examples.

Choose the next step

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