What reports are available?
The Reports page turns support conversations into merchant-facing operational intelligence. Where Analytics emphasizes volumes and resolution outcomes over time, Reports breaks down what customers ask about, where issues show up, and how support connects to business results.
Access Reports from Simple Chat in Shopify Admin and use the report tabs to switch lenses on the same underlying conversation data.
Report views included
Simple Chat provides report tabs for:
- Products — See which products generate the most support demand. Useful for merchandising, quality control, and sizing or fit documentation.
- Topics — Understand recurring themes in customer questions (shipping, returns, compatibility, etc.).
- Sentiment — Track emotional tone trends so you can spot rising frustration before it shows up in public reviews.
- Pages — See which storefront pages shoppers were on when they started a conversation—helpful for fixing confusing product pages or checkout friction.
- Subscribers — Track back-in-stock and similar sign-up activity tied to chat interactions.
- Revenue — Connect tracked chat interactions to orders when the required Shopify reporting data is available, so you can relate support work to sales outcomes.
Each tab answers a different “why are customers contacting us?” question. Product and topic reports are usually the first stop for operations; sentiment and page reports help marketing and UX teams.
How to use Reports in practice
A straightforward review loop:
- Pick a time range (Reports supports the same common windows as Analytics, such as 7–90 days).
- Start with Topics or Products to find what drove the most conversations in that period.
- Open Sentiment if you suspect frustration is climbing on a specific theme.
- Use Pages to tie issues to storefront locations, then fix content or policy clarity at the source.
- Check Revenue when you want to see whether high-touch conversations correlate with orders—especially for campaigns where chat assists conversion.
Drill into conversation counts from a report when you need examples for training or for filing a bug with your theme or fulfillment partner.
Reports vs Analytics
- Use Analytics for “how much” and “who resolved it” (volume, AI vs staff, validation, billing alignment).
- Use Reports for “what are they asking about” and “where on the store did it start” (products, topics, sentiment, pages, subscribers, revenue).
Together they give managers both operational efficiency and customer-insight narratives without exporting spreadsheets manually.
Limitations and data requirements to know
Reports are powerful, but a few constraints keep expectations accurate:
- Revenue reporting depends on Shopify order and attribution data being available for tracked chat interactions—if data is missing, revenue ties may be incomplete rather than zero support value.
- Subscriber metrics reflect sign-up flows Simple Chat tracks (such as back-in-stock interest), not every marketing list in your stack.
- Thematic reports aggregate many conversations; always drill into sample threads before changing product copy or refund policy based on a single spike.
When a report looks surprising, cross-check the same period in Analytics for volume changes—a topic can look “worse” simply because more customers reached chat, not because the underlying issue grew.
Changelog releases
This topic appears in the following release notes: