Trustpilot Review Data: 25 Export Fields Explained

A spreadsheet full of review text is useful, but structured review data is much more powerful. When ratings, dates, replies, reviewer context, company metadata, and source links have separate columns, you can filter, group, validate, and analyze them without repeatedly returning to the page.

Trustpilot Reviews Scraper exports 25 fields from a Trustpilot business review page. This reference explains what each field represents, how it can support analysis, and what you should not assume from it.

The 25 Exported Fields at a Glance

The columns fall into four practical groups:

• Review content and status
• Reviewer information
• Company information
• Dates, traceability, and collection metadata

CSV and XLSX exports use the readable column names shown below. JSON exports contain the corresponding structured keys.

Review Fields

1. Review Id

A source identifier for the review. Use it to remove exact duplicates when you append multiple exports or refresh an existing dataset.

Do not generate a replacement ID when the value is missing. A generated value would no longer be a source identifier.

2. Rating

The review's star rating. This supports rating distribution, low-rating versus high-rating comparisons, and trend analysis.

Avoid using the average alone. Always consider the number of reviews and the full distribution from one to five stars.

3. Review Title

The short headline written for the review. Titles often summarize the customer's main point, but they should be read with the full content before assigning a theme.

4. Review Content

The written review body. This is the primary source for qualitative analysis, theme tagging, complaint classification, and identifying language customers use to describe their experience.

Keep the original text intact. Put analyst summaries and categories in new columns instead of overwriting it.

5. Reply

The business's public reply, when one is available. An empty value means no reply was present in the exported source data; it does not prove that the customer received no private support.

This field can support public reply coverage, tone review, escalation analysis, and consistency checks.

6. Verification Level

The verification label associated with the review in the source data. Treat it as descriptive metadata, not a complete measure of truthfulness or customer value.

7. Likes

The number of likes associated with the review at collection time. Likes can help locate feedback that other visitors found useful, but older or more visible reviews may have had more opportunity to receive them.

8. Language

The review's language value. Use it to route reviews for translation or language-specific analysis. Automated language labels can still require validation, especially for short or multilingual comments.

9. Review Link

A direct URL to the individual review, built from its source ID. Keep this column in analysis files so findings can be traced back to the public source when context needs to be checked.

Reviewer Fields

10. User Id

The reviewer's source profile identifier. It can help distinguish records during data preparation, but it should not be used to build intrusive profiles or combine personal information across unrelated contexts.

11. User Name

The display name shown for the reviewer. A display name may not be a verified legal name. Minimize its use in reports and avoid publishing it unless there is a legitimate, permitted reason.

12. User Avatar

The image URL associated with the reviewer's profile, when available. Most aggregate review analysis does not need this field, so consider removing it from working copies if it serves no analytical purpose.

13. User Country Code

The country code associated with the reviewer in the source data. It can support broad geographic segmentation, but it should not be treated as precise location information or used to make assumptions about an individual's background.

Company Fields

14. Company Id

The source identifier for the Trustpilot business unit. This is helpful when combining exports or maintaining an internal source registry.

15. Company Name

The business display name attached to the exported reviews. If you combine several companies into one dataset, retain this column and add your own clearly defined source label if needed.

16. Company Icon

The public profile-image URL associated with the business. It may be useful for internal dashboards, but a remote image can change or become unavailable. Do not rely on it as the only business identifier.

17. Company Stars

The company's displayed star value at the time of collection. This is company-level metadata rather than the rating of the individual review.

Keep Company Stars and Rating clearly separated in reports: one describes the business profile, while the other belongs to a specific review.

18. Company Trustscore

The TrustScore value associated with the business at collection time. Because this value can change, pair it with Scraped At when using it in a historical snapshot.

19. Company Contact Info

Public contact information present in the company data. In tabular exports, nested values are converted into readable text. Use this information only for legitimate business purposes and follow relevant privacy and communications rules.

20. Company Website

The website URL associated with the company profile. This helps validate that similarly named companies have not been mixed together.

21. Company Categories

The exported company category value. Categories can support grouping, but check comparability before benchmarking companies: two businesses placed in a broad category may still serve different markets or business models.

22. Company Verification

The company verification information available in the source data. In a CSV or Excel file, structured verification values are converted to readable text.

Treat this as source metadata and avoid turning it into claims that go beyond what the value explicitly says.

Date and Collection Fields

23. Experienced Date

The date associated with the customer's experience. Use it when investigating when an operational event occurred—for example, whether reviews mention a particular launch or delivery period.

24. Published Date

The date the review was published. Use it for review-volume reporting, publication trends, and public reply workflows.

Experienced Date and Published Date answer different questions, so do not substitute one for the other without explaining the choice.

25. Scraped At

The timestamp recorded when the extension collected the review. It helps document dataset freshness and provides context for company-level fields that may later change.

Scraped At is not the publication time or experience time. Think of it as the timestamp for your data snapshot.

Which Fields Do You Need for Common Tasks?

Basic customer feedback analysis

Keep:

• Review Id
• Rating
• Review Title
• Review Content
• Experienced Date
• Published Date
• Review Link

Add your own theme, sentiment-detail, and analyst-note columns without altering the source fields.

Public reply analysis

Keep:

• Review Id
• Rating
• Review Content
• Reply
• Published Date
• Review Link

This set lets you measure public reply coverage and assess whether replies respond to the issue described. It does not reveal private customer-service activity.

Market or competitor research

Keep:

• Company Id
• Company Name
• Company Website
• Company Categories
• Rating
• Review Content
• Reply
• Published Date
• Review Link
• Scraped At

Use the same sampling and filtering rule for every company. Our competitor review analysis workflow explains how to compare percentages and preserve limitations.

Monthly reporting

Keep:

• Review Id
• Rating
• Review Content
• Reply
• Experienced Date
• Published Date
• Review Link
• Scraped At

Use Review Id for deduplication and Published Date for publication-period charts. If the report concerns operational timing, analyze Experienced Date separately.

How the Formats Represent the Data

CSV

CSV stores one review per row and one field per column. It is portable and easy to import, but it does not retain formatting, formulas, or charts.

XLSX

Excel output uses the same readable columns and is convenient for filters, tables, PivotTables, and business reporting. See our Excel review analysis tutorial for a complete workflow.

JSON

JSON is best when software will process the export. The structured keys map to the same review, reviewer, company, and date concepts described in this article.

Need help choosing? Our Trustpilot review export guide compares all three formats.

Data Quality Checks Before Analysis

Before calculating metrics or feeding the data into another tool:

1. Confirm the expected business name and website.
2. Count unique Review Id values and investigate duplicates.
3. Check for active rating or language filters.
4. Validate that date columns are interpreted as dates.
5. Distinguish empty replies from missing or incomplete rows.
6. Preserve the original export and document any transformations.
7. Keep the collection date and source URL with your analysis notes.

Blank values are not automatically errors. A reviewer may not provide an avatar, a company may not reply, or a source field may not be present for a particular record.

Privacy and Responsible Use

The fact that information appears on a public page does not remove every obligation related to its collection, storage, and use. Apply data minimization: if your analysis needs ratings, text, and dates but not names or avatars, remove unnecessary personal fields from working copies.

Protect exported files, define a retention period, limit access, and follow Trustpilot's Terms of Service, applicable laws, and agreements governing your access. Do not use reviewer information for harassment, intrusive profiling, or unsolicited outreach.

Export the Fields You Need

Trustpilot Reviews Scraper turns public business reviews into stable columns that can be used in spreadsheets, scripts, reporting workflows, and internal research.

Export Trustpilot review data to CSV, XLSX, or JSON →

Trustpilot Reviews Scraper is an independent tool from ExtensionsGod and is not affiliated with or endorsed by Trustpilot. Trustpilot and related marks belong to their respective owners.