Skip to main content
Simio provides a full analytics dashboard to help you understand how your WhatsApp campaigns and automations are performing. This page covers the dashboard home, the analytics page, per-campaign drill-downs, and how to export your data.

Dashboard home page

The dashboard is the landing page after login. It includes:
  • Recommended campaigns: a fixed, hardcoded list of campaign template suggestions (e.g. “Welcome with promo code”, “Win back inactive customers”). This list does not currently change based on company data or behavior; it is the same static set of suggestions for every company.
  • Needs Your Attention: a widget surfacing issues that require action, described in detail below.

”Needs Your Attention” widget

This widget shows hard-blocking issues that a company should resolve, grouped by type. Every active alert is shown, with no cap or limit (if there are 10 alerts of the same kind, all 10 are listed) because these represent things actively preventing messages from going out or credentials from working. Each alert type is grouped under its own header with a count. Groups are never merged, collapsed, or truncated, by design, since these are meant to represent real blockers on outgoing communication.

The Analytics page

A full dashboard summarizing message performance across all campaigns and automations for a date window (the platform currently defaults this window to the last 30 days; there is a from/to date range supported by the underlying data, but as of now the analytics page in the product does not expose date pickers to change it, so users see a rolling 30-day view). Users can filter by connected messaging account (for example, a specific WhatsApp number) or leave it on “All accounts.” The page is made up of the following sections:

Metric cards

A row of headline metrics, each showing:
  • The current value.
  • A percent change compared to the equivalent prior period (e.g. this 30 days vs. the previous 30 days).
  • A small sparkline chart showing the daily trend over the period.
  • Whether an increase in this metric is good or bad news (used to color-code the change, since for some metrics like “failed” a decrease is the good direction).

Overview cards

Three summary figures for the selected period:
  • Cost: total messaging cost (based on per-message pricing) across the period.
  • Opt-ins: number of contacts who opted in during the period.
  • Opt-out rate: opt-outs as a proportion of messages sent.

Funnel (Sent / Delivered / Opened / Clicked / Failed)

A step-by-step funnel of what happened to sent messages, each stage with a count and a rate: Rate formulas (consistent everywhere in the product):
  • Delivered rate = Delivered ÷ Sent
  • Opened rate = Opened ÷ (Sent minus Failed)
  • Click rate = Clicked ÷ Opened
  • Failed rate = Failed ÷ Sent
All formulas are explained as tooltip in each cards. How “clicked” is counted: a click is counted per unique contact, not per click event. If a contact clicks a link and also taps a reply button in the same message, that still only counts once toward the click total (this avoids double-counting engaged contacts). This is deliberate: summing clicks by type separately would inflate the numbers.

Deliverability cards

The same five stages (Sent, Delivered, Opened, Clicked, Failed) shown again as standalone cards, each with its rate and the raw numerator/denominator behind it. This is the same underlying data as the funnel, presented in a card format rather than a step funnel.

Per-campaign and per-automation tables

Two separate tables (campaigns are listed separately from automations) showing, per row: name, last time it sent, number sent, open rate, click-through rate, opt-out rate, failed rate, and (for automations only) whether the automation is currently active and when it was last updated.

Per-campaign analytics

Every campaign and automation has its own scoped analytics view, showing the exact same categories of data (funnel, deliverability, metric cards) but filtered to that single campaign/automation. This view is available in two forms depending on where it’s opened from:
  • As a slide-in panel from most places in the product (e.g. from a campaign list).
  • Embedded directly as a tab inside the campaign/automation editor itself (next to the “Scenario”/flow-builder tab), so a user can flip between editing the flow and reviewing its performance without leaving the editor. Chatbots do not yet have this analytics tab; it is present but disabled for chatbots today, since chatbots don’t currently have an analytics data model behind them.

Exporting analytics data

From the analytics page, a user can export a single campaign’s or automation’s data as a file:
  • Formats: CSV or XLSX (Excel).
  • Contents are configurable via toggles: the export can include summary stats, contact-level detail, custom field values, and button click detail, in any combination the user selects.
  • Date filtering: the export can be scoped to a specific date range, independent of whatever is currently shown on screen.
  • Exports run as background jobs. A list of past export jobs is shown, with status (pending/processing/done) automatically refreshing every few seconds while a job is still running, and a download link appears once ready.

A note on metric definitions and consistency

Because the same metrics (sent, delivered, opened, clicked, failed, and their rates) are calculated and displayed in several different places (the main dashboard funnel, the deliverability cards, the per-campaign/automation tables, the sparklines on the metric cards, and the single-campaign drill-down), the platform’s internal rule is that any change to how a metric is defined must be applied consistently everywhere it appears, or the same-named number will show differently in different parts of the product depending on where you look. If numbers for the same metric ever appear inconsistent between two screens that should logically agree, that is worth flagging to engineering as a possible inconsistency bug, with the exception of the campaign-vs-dashboard drill-down nuance described in section 2 above, which is a known and accepted difference rather than a bug. Simio provides a full analytics dashboard to help you understand how your WhatsApp campaigns and automations are performing. This page covers the dashboard home, the analytics page, per-campaign drill-downs, and how to export your data.