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?

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.

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.