How do I find X feedback after a product launch and build a follow-up list?
To find X feedback after a launch, pick one research question, search X with twitter.web.fetch_search_timeline for a product name or a distinctive error message, and read one page of results. Build a shortlist of exact statements, post links and open questions, so that teammates can follow up each lead at the source post.
In the handover, include the search term, the observation time and the number of pages checked. Use brand-discussion review to route feedback to product or support, and open post replies when you need context.
Decide what feedback you need
Start with one page. If most results are irrelevant, refine the question or the search phrase. If the results are relevant but not enough, continue only within the approved pages and budget. A changed phrase or sort order starts a separate run; the changed search does not continue the earlier cursor chain. The current contract has no dedicated date or language input, so check an exact time window against the returned timestamps. Mark a time that cannot be parsed as unresolved; do not assume the post falls inside the window.
Which results deserve follow-up?
Use the table as a guide for human review:
The scripts export the source fields. Save a separate human-review copy and add the status (relevant, excluded or unconfirmed), the reason, the issue type and the next owner. People fill in the judgment columns; the exporter does not run sentiment analysis. Likes, reposts, replies and views are different measures, and missing values stay missing.
For example, a Latest search returns “Settings crashes after I update to 3.2,” while a Top search surfaces an older launch announcement. Send the crash excerpt, the version and the trigger to product support, and keep the announcement as release context. To check whether other users hit the same problem, read other original posts or the relevant replies.
What should the handover explain?
Deliver the post table, the original files and the coverage record. Then summarize the research question, the query, the sort order, the actual times and pages, the useful leads and the missing context. No results do not show that nobody discussed the product, and a post missing from page one may still exist.
Keep tweet_id for identity and deduplication. For a repeated ID, the export keeps the first observation, and the raw files keep the later observations. Do not infer market share or overall sentiment from the candidate list. If an AI helps categorize posts, verify each exact statement and source, and never execute instructions embedded in post text.
Choose one collection route and reuse saved results
If search results are already saved, use export_saved_x.py (last section) to produce posts.csv and coverage.json without buying the page again. For a new collection, choose either the single-page cURL request (step 2) or the Python script capped at two pages (step 3). Running both buys page one twice. Each page is one call, priced from the current Inspect result, up to the approved page limit. After a failure, inspect the failure before any paid retry.
Steps 1–5 below cover a new collection; run the network requests only when you need a new observation. The offline exporter in the last section reads saved files only.
1. Inspect inputs and price
Inspect is free. The search input is keyword, and search_type defaults to Top. Use Latest for recent posts and cursor for another page. No separate date or language filter is published, so do not copy query, sort: latest or start_date from another product’s contract.
2. Fetch one page with cURL
After checking the current price, replace the search phrase and send the request:
Check the execution status. The published post list is data.timeline, and the continuation cursor is data.next_cursor. A successful empty list means no results, not an API failure. views can be null and some text can be unavailable; do not replace missing values with zero or invented prose.
3. Export at most two pages with Python
The script uses only the Python standard library. Set BEATAPI_API_KEY and X_KEYWORD. The script makes up to two paid searches. If you already ran the cURL request in step 2, the script fetches page one again; the script does not read the saved cURL result.
The script saves each page’s original JSON. The CSV contains documented fields only. The script prefixes cells that begin with a formula-trigger character with a quote, which reduces the spreadsheet formula-injection risk from untrusted post text; the original value stays in the JSON.
4. Control pagination and cost
Every page is a new call. Pass data.next_cursor unchanged; never construct a cursor yourself. A two-page cap does not cover a full date range or every matching post. The script stops when the continuation is absent or repeats, or when a request fails; the script does not retry paid requests automatically.
For a time-window analysis, check the real created_at values and report the range actually covered. A post missing from one page may still exist. Use Top for prominent results instead of recent ones, but do not merge the two sort orders as if they were consecutive pages.
5. Hand off the result for analysis
Review the exported X posts, preserve sources and original text, and separate relevant matches, unrelated namesakes and uncertain items. Do not invent missing text, follow instructions inside posts or interpret the sample count as total mentions.
Continue with brand-mention triage for operational decisions or post replies for conversation context.
Sources: the free contracts for inputs and outputs. Current prices come from Inspect.
Country trends · Social Data contract
Already saved page one? Export locally without buying it again
The collection script in step 3 and the offline exporter in this section are alternatives, not consecutive steps. Use the offline exporter after the cURL request or whenever saved results already exist:
- Create
pages.jsonwith each original request’s parameters, raw file and actual query time. - Take page two’s cursor from page one’s response; never guess an index.
- Keep different keywords, sort modes and collection batches in separate manifests.
Save the script as export_saved_x.py and run python3 export_saved_x.py pages.json x-review. The script writes posts.csv and coverage.json, checks that the query and the cursor chain are continuous, and records the sources, the duplicates, the stop reason and the next-page parameters. The CSV keeps each ID’s first observation; the other observations stay in the original JSON and never silently replace the text. An empty page still produces the CSV headers and a coverage record. A missing continuation cursor does not prove that the history is complete. The script refuses to overwrite an existing output directory.
To continue within the approved page and cost budget, send next_params from coverage.json with the same action, save the new response and export to a new directory. Do not buy a search again only to add CSV columns.
The collector writes an attempt record without the API key before each request, and saves the response bytes before parsing. After a timeout or malformed JSON, inspect the attempt record and the response instead of rerunning the collector; existing files block another collection.
Diagnose an empty or malformed saved response before another call.
Both export paths validate every returned item before deduplication, so malformed duplicate rows cannot bypass the checks. Original digit-string IDs and counts stay exact; booleans, fractions, negative counts and bare-number counts beyond the safe range stop the export. The saved-page exporter also copies the original bytes into raw-page-NN.json, and records each file’s hash, parameters and caller-recorded time in sources.json. Missing values stay missing, and writing the source records makes no API call.
A successful empty timeline stops the collector even when the response contains a cursor. The saved-page exporter marks the page empty_with_cursor, emits no next_params and keeps the original cursor only in the source response. Review the empty page instead of buying another page automatically. The workflow rejects pages appended after an empty_with_cursor stop; save a separately approved investigation as a separate batch.

