How do you import reviews into ReviewProof by CSV?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
Prepare a CSV with a header row: a body column (body, review, text or comment), rating, reviewer, date, source, and — where you hold them — a verified-transaction flag and a transaction reference. Upload the file or paste its text in the audit desk, name the location, and ReviewProof analyses the rows, seals each with a certificate identity, and logs import, transaction-link, analysis and kept-by-default moderation events. Free imports up to 500 reviews at a time for one location; Pro raises that to 5,000.
What is a review CSV import?
A CSV review import is the bulk loading of review rows from a spreadsheet file into the audit system. It is the moment raw history becomes a record: each row acquires a stable review identity, a fingerprint from its reviewer handle and source, computed risk signals, a provenance chain, and a verified or UNLINKED status determined by the transaction data that arrived with it. The import is therefore only as honest as the file — it will faithfully preserve a good export and faithfully expose a sloppy one.
The columns that matter, and what happens without them
Column names are matched flexibly — reviewer, author or name; rating or stars; body, review, text or comment; date, review_date or created_at; source or platform; verified_txn or verified; txn_ref, transaction or order_id — but flexibility about names is not flexibility about content. A missing date column disables burst reading for the file. A missing source column flattens fingerprints. Missing transaction columns cap the entire import at UNLINKED, however genuine the reviews are. Before the first import, spend ten minutes on one sample row per source and confirm each value lands where the sample says it should: the dashboard counter and the report's verified count will tell you immediately whether the file arrived as intended.
A detail worth knowing before you start: ReviewProof analyses what you give it. The CSV importer reads reviewer, rating, title, body, date and source columns, plus a verified-transaction flag and a transaction reference when you have them. Reviews with a transaction link are marked verified; reviews without one are marked UNLINKED — kept in the audit, visible in the report, but excluded from the verified-experience widget, which only displays reviews that are both transaction-linked and in a kept or published state. That single rule is the difference between a widget that markets and a widget that proves.
Split large histories by plan, not by convenience
Import caps exist per plan — 500 rows on Free, 5,000 on Pro, 50,000 on Agency — and the applied cap keeps the first rows of the file, so an oversized paste silently truncates the tail. For a first historical import larger than your cap, split by date into chronological chunks and import them in order: chains stay readable, burst detection is not distorted by chunk boundaries the way random splits distort it, and any file error is localised to one chunk. After the history is in, switch to the monthly rhythm of current-period files, where the cap will never bind a single location's genuine volume.
ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.
Mistakes that undo the work
Importing a hand-edited spreadsheet without noting the edits tops the list — tidy files produce tidy-looking lies in the chain. Second: testing the import with invented rows mixed into the real file, where they become permanent fake reviews in your own record. Third: re-importing the same full history monthly, duplicating rows and fingerprints instead of importing only the new period.
The workflow is the same on every plan, and the free tier does the complete job for one location: import by CSV upload or paste (up to 500 reviews per import on Free), read the full risk analysis and report, open a provenance certificate for any review, and publish the verified-experience widget. Pro ($29/month, 3 locations, 5,000 reviews per import) adds the full provenance chain detail, the evidence export, AI reply drafts and the reviewer-fraud graph. Agency ($79/month, 50,000 reviews per import) is the multi-location tier. Nothing about the free audit is a sample or a teaser — the report you get free is the real analysis of your real rows.
Worked example: a bookstore imports nine years in four chunks
A fictional worked example, written to show the numbers and the decisions in practice.
A bookstore held 1,940 reviews in exports from two platforms and its own webshop. On the Pro plan (5,000 per import) one file would have fitted, but the owner split by year anyway to sanity-check each era. The third chunk surfaced the lesson: its dates had exported as month names the importer could not parse as dates, so that chunk's reviews arrived dateless and burst analysis skipped them. Because the split isolated the fault, she fixed the format for one file and re-imported one chunk, instead of contaminating the whole history. Final state: 1,940 reviews, 71% transaction-linked — the webshop years, where order references survived, at 94%.
Your five-action checklist
- Build the CSV with header row and one row per review, all sources included
- Include date, source and reviewer columns — and transaction references wherever held
- Test with the sample format first and confirm counts on the report
- Split histories larger than your plan cap chronologically, oldest first
- From then on, import only the new period on your monthly rhythm
Frequently asked questions
What columns are required?
A body column is essential — rows without review text are skipped. Rating, reviewer, date and source make the analysis meaningful; verified flag and transaction reference make provenance possible.
How many reviews can I import at once?
500 per import on Free (one location), 5,000 on Pro (3 locations), 50,000 on Agency (multi-location).
What happens to a transaction reference on import?
It marks the review verified and is logged in the chain. For published provenance results, only a SHA-256 hash and masked form are retained — never the raw reference.
Can I paste instead of uploading a file?
Yes — the audit desk accepts pasted CSV text as well as a file upload, under the same caps and the same parsing.
Keep reading
Related guides from the ReviewProof library:
- Paste import or file upload: which should you use?
- How do you read a ReviewProof risk report?
- How does the verified-experience widget decide what to show?
- How should you use AI-drafted replies to reviews?
- How do you ask customers for reviews without breaking the rules?
- How do you write a review-request email that does not gate?
- How do you audit reviews across multiple locations?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.