Reading your analytics reports

Who this guide is for: every seat that needs numbers — owners, administrators and teammates with the analytics-read permission (employees without it are refused; see the refusal table below).

How to read your business's messaging analytics in ConvoTide: open the report, change what it covers, trust what the numbers mean, dig into a bot's runs, and recover from errors, refusals or a changed session.

The examples are simulated test data. Businesses, campaigns, templates, bots and phone numbers shown here (names beginning SYNTHETIC…, the a2543000-… business, +9199… numbers) come from isolated synthetic test runs behind this guide — not live customer traffic.

Open the Analytics area

  1. Sign in and open your business's engagement area (sign in to the workspace, select your business, then Open Analytics).
  2. The Analytics page opens with a report subject selector and a period (calendar month) selector.
  3. You need a seat with the analytics-read permission for this business. If your seat lacks it, or your account is not a member of the selected business, the app refuses with a clear message — see When access is refused.

The same journeys work at desktop width and at phone width (390 px), with no sideways scrolling.

Read the campaign report

With a campaign selected and a month picked, the blended table shows one row per channel (WhatsApp, SMS) plus a blended total row. For each row you get counts of messages attempted, delivered, failed and unresolved:

Everything is scoped to the selected business only; counts never mix businesses.

Change the campaign or the month while a load is in flight

If you switch the campaign or the month while an earlier request is still loading, the report settles on your latest choice — the slower, older response cannot overwrite it. The report title and the attempted counts end up matching the campaign and month you last picked.

See the whole account for a month

Switch the report subject to account to drop the campaign filter:

Ask a range question

For an exact window instead of a calendar month:

  1. Enter a from day and a to day.
  2. Press Enter on Apply.

The range summary shows recorded / delivered / failed / unresolved for that window. The window includes the from instant and excludes the to instant (half-open), and a window with no traffic is a valid, empty answer — zeros, not an error.

Limits you can hit: the range can be at most 366 days, the to day must not be in the future, from must be before to, and both must be real ISO-8601 dates. Breaking a limit returns a plain refusal naming the rule (see When access is refused).

Compare two templates

Switch the subject to compare, choose the template kind, and fill in two template names plus the same from/to days:

Synthetic example: over one month, template synthetic2904_A recorded 3, delivered 2, failed 1 → 66.7% (denominator 3 shown); template synthetic2904_B recorded 2 with both still unresolved → 0%.

Look at a bot's runs

Switch the subject to bot (or open the Bots area, below) and pick a bot:

Desktop analytics page with a bot report subject selected: lifetime totals of 25 runs (20 completed, 5 failed), a table of the latest 20 runs with UTC recorded-at timestamps, a note that more runs exist beyond the 20 loaded, and honesty banners instead of guessed spend

The bot report at desktop width: lifetime totals, the latest-20 slice, and honest spend banners. Full-size image

The same bot report at phone width: totals, the runs table and the honesty banners stack vertically with no sideways scrolling

The same journey at 390 px phone width. Full-size image

Open a run's saved trace (Bots area)

In the Bots area, each bot lists its runs. To inspect one:

  1. Click the bot's row to load its runs list.
  2. Click open on a run. The detail shows the run's id, bot, trigger node, contact and trigger keyword, plus its saved trace — the steps that actually ran (kind, action, node), recorded verbatim (for example a trigger step "I am SYNTHETIC2904 trace 00").
  3. Press Escape to close the detail; keyboard focus returns to that run's open button.

Race safety, verified in the accepted journeys: opening a second run while the first's detail is still loading shows the run you opened last; closing a detail keeps it closed even if a late response arrives; and loading more runs then switching bots shows only the new bot's runs — the previous bot's next page cannot leak in.

Bots area run drilldown: the second bot is selected in the list and the flow editor, and its three recorded runs are listed with statuses and UTC timestamps

Run drilldown at desktop width after switching bots. Full-size image

The same run drilldown at phone width, with the bot list, runs table and editor stacked

The same journey at 390 px phone width. Full-size image

When a request fails: read the error and Retry

If a request genuinely fails (for example the network drops mid-load), the runs area shows an error banner — "cannot reach the API…" — while other parts that did load (such as the lifetime totals) stay visible.

Real error state in the runs list: the second bot is selected, its lifetime totals are shown, and a red banner says the API cannot be reached, with a Retry control

A genuine failed request, as you actually see it. Full-size image

The same real error state at phone width

The same state at 390 px phone width. Full-size image

When access is refused

Refusals are honest boundaries, not data loss. Each names its rule:

You see Why What to do
Authorization header required (401) The request carried no sign-in Sign in again
this action requires the "analytics:read" scope for your seat (403) Your seat lacks the analytics permission Ask your business administrator for a seat with the scope
This account is not a member of the selected business (403) Your account is not a member of the business you selected Switch to a business you belong to
campaign not found / bot not found / Resource not found (404) That id does not exist for your business Re-pick the campaign, bot or run from the list
period must be a YYYY-MM calendar month (400) The period was not a calendar month Pick a month from the period selector
from must be strictly before to (half-open [from, to)) or from and to must be ISO-8601 instants (422) The range days were reversed or not real dates Correct the from/to days and apply again
to must not be in the future (422) The to day is ahead of now Use a to day that has already happened
range must be at most 366 days (422) The window is too wide Narrow the range to at most 366 days
phone must be a plausible E.164 number (422) The number-activity phone was malformed Enter a full phone number in international format
windowDays must be 1..90 (422) The activity window was outside 1–90 days Choose a window between 1 and 90 days

A note on the number-activity view: querying one phone number's recent activity (with a 1–90 day window) is accepted at the service level in this guide's evidence — counts cover only that recipient within your business, over a half-open window ending "now", and a number with no traffic returns zeros, not an error.

If your session changes mid-work

If the portal credential behind your session is replaced while you work (in the accepted evidence: a second tab switches the principal from an admin to a viewer while an analytics response is still in flight):

The analytics area after the supported session switch to the viewer principal: the viewer identity is active, the page renders normally, and neither the old campaign report title nor any session-expired banner is present

The analytics area under the new (viewer) principal after the session replacement. Full-size image

What this chapter does not cover

Evidence and assets (appendix pointers)