Analytics, reporting, and attribution overview

Use analytics and reporting to understand what happened after Hellotext sent a message, activated a playbook or route, or linked activity back to your store.

This section connects three related questions:

How did a campaign, playbook, or route perform?
Which customer actions happened after the message?
Which revenue was attributed to Hellotext?

Revenue report

The Revenue report shows purchases completed during the selected period, including total revenue and the portion attributed to eligible Hellotext activity.

Use it when you need to compare revenue attributed to AI or classified as team-managed, inspect credited Campaigns and Playbooks, or reconcile individual attributed purchases.

Keep reading: Revenue report guide.

Performance report

The Performance report follows conversations from their start through later conversion and escalation outcomes.

Use it when you need to compare conversion rate, time to conversion, escalation rate, and AI-only versus team-managed conversion paths.

Keep reading: Performance report guide.

Demand insights

Demand insights identifies product requests that could not be fulfilled, the products and variants affected, and the estimated value of those missed opportunities.

Use it when you need to prioritize inventory, catalog, availability, or alternative-recommendation problems based on observed customer demand.

Keep reading: Demand insights guide.

Campaign reports

Campaign reports help you review delivery, engagement, clicks, conversions, replies, and attributed revenue for a one-time send.

Use campaign reporting when you need to evaluate a campaign, compare message performance, or decide what to improve before the next campaign.

Keep reading: Campaign reporting.

Playbook and route reports

Playbook reporting helps you review always-on workflows, AI agents, and journey routes after they start receiving real customer activity.

Use playbook reporting when you need to compare attributed revenue, conversion behavior, time to conversion, escalation rate, and the handoff quality behind the numbers.

Keep reading: Playbook reporting.

Service quality report

The Service quality report compares AI and team resolution, SLA compliance, unresolved conversations, response-time distribution, and agent performance.

Use it when you need to understand how conversations are being resolved and whether a service problem is concentrated in a channel, team, teammate, AI agent, or resolution path.

Keep reading: Service quality report guide.

Workload & capacity report

The Workload & capacity report compares active load, handled and resolved work, concurrency, assignments, transfers, capacity pressure, session efficiency, and the current operational queue.

Use it when you need to understand how Inbox work is distributed during a period and what needs attention right now.

Keep reading: Workload & capacity report guide.

Attribution

Attribution explains when Hellotext receives credit for a sale and when it does not.

Use attribution guidance when you need to understand source precedence, eligible evidence, attribution windows, team participation, and supported order changes.

Keep reading: Sales attribution.

Tracking data

Reports are stronger when Hellotext receives useful customer activity from your store, site, integrations, or API as signals.

If your store is connected through a supported integration, many events may be tracked automatically. If you have a custom setup, use Hellotext.js or the API to send events.

Keep reading:

Before comparing results

When reviewing performance, check:

The audience and channel used.
Whether links and tracking were configured correctly.
Whether the report is measuring clicks, replies, conversions, or attributed revenue.
Whether the order contains a recognized external source that takes precedence.
Whether checkout ownership or path-specific team participation affected the decision.

If you are reviewing your first launch, start with Measure success in your first 7 days.