Does null views mean zero views?
No. In a saved twitter.web.fetch_search_timeline response, null in data.timeline[].views means that observation returned no view value; only the string "0" represents a reported zero. Exclude null and absent views entries from averages, and state how many posts reported a view value alongside every average.
Check whether a post reports a view count
Inspect data.timeline[].views on each post. The published type of views is string or null:
The views field alone does not establish that a post was deleted, private, newly published, or never viewed.
How does missing coverage change a research report?
Take three sample posts with views values of "100", "0", and null. Report 2 of 3 with available views, an observed sum of 100, and a mean of 100 / 2 = 50 across the two posts with reported values. Dividing by all three posts treats null as zero, distorts the average, and conceals missing metric coverage. A mean of 50 applies only to those two reported posts—not the full audience, not unique reach, and not an estimate for all matching posts on X.
When comparing two keyword sets, show view availability next to each mean. A set where few posts report views cannot be compared directly with a set where nearly all posts report views. Save each query, sort mode, and observation time alongside the source response file. Across repeated snapshots, match by tweet_id and compute a delta only when both snapshots report a numeric string value; leave other deltas blank.
Make a coverage table from one saved search page
Start from a saved successful response collected via the keyword-search guide. views_coverage.py makes no calls to X or BeatAPI, fetches no extra pages, and invokes no model. Keep the original request manifest beside the output folder so reviewers can audit the query and sort settings. When the response includes a continuation cursor, views_coverage.py records continuation_available without following the cursor.
Save the script as views_coverage.py:
Run python3 views_coverage.py page-1.json ACTUAL_COLLECTION_TIME new-coverage-folder. Replace ACTUAL_COLLECTION_TIME with the timezone-aware timestamp recorded when the response was collected (for example 2026-11-16T10:00:00Z), using the real collection timestamp rather than the example value. The destination folder new-coverage-folder must not exist yet.
The output folder contains views.csv, summary.json, and a byte-identical copy of the input as raw-response.json. summary.json stores every ratio as an exact integer numerator and denominator so large counts avoid floating-point rounding. A page with zero reported values has no mean, and a successful empty page has no coverage fraction; an empty page and a page where every views value is null are distinct states. views_coverage.py exits before creating output on duplicate IDs, malformed values, failed calls, or missing timeline arrays. If views_coverage.py rejects an unexpected numeric value, inspect the original response instead of converting the value to a string by guesswork.
source_sha256 in summary.json fingerprints the saved response bytes without proving authenticity or verifying the manually entered timestamp. Import numeric-looking tweet_id values and large counts into spreadsheets as plain text to preserve precision. Re-running views_coverage.py consumes no API calls; refreshing data or following a cursor requires a new request.
Search-page CSV and original request manifest · Diagnose an empty search result
Contract reference: data:twitter.web.fetch_search_timeline.

