Skip to main content
At the end of this page, you can tell how a campaign performed, down to a single recipient, and export the evidence.

Before you start

Before you start, sign in to the dashboard and select the organization you want to work in.
  • You have an audience campaign that has started sending. See Create a campaign.
  • A webhook campaign has the same report on its Analytics tab, with a request ID on each call. See Run webhook campaigns.

Open the report

1

Open Campaigns and select your campaign

The campaign page opens with its Edit and Analytics tabs.
2

Select the Analytics tab

The report shows the funnel, daily trends, and the recipient table.

What the report shows

The funnel has four stages: Sent, Delivered, Read, and Replied. It shows where recipients drop off between one stage and the next. A delivery that reaches Read or Replied also counts as Delivered, even when the provider skipped the earlier confirmation. A later stage therefore never exceeds an earlier one. Daily performance plots four series over time: Sent, Delivered, Read, and Responded within 24h. A range switch sets the period. The recipient table has the columns Recipient, Identifier, Status, Sent, Read, and Cost. On a webhook campaign, Called replaces Sent, because a refused call never sends. A failed row shows its error code next to the status. Hover the status to read the full error, which tells you whether a re-send can succeed. Filter by status to isolate one failure type. Roles that can read end users can also use Search name or number… to find one end user. Other roles see the totals without the recipient table.

Export recipient activity

Select Export CSV above the recipient table. The button appears for roles that can read end users and export data. The file downloads directly in your browser, and a toast reports how many recipient rows were exported.

Export the sends of a webhook campaign

A webhook campaign can send far more rows than a browser can build, so Export CSV on its Analytics tab opens a dialog and runs in the background. The button appears for roles that can read end users and export data.
1

Open the Analytics tab and select Export CSV

The Export CSV dialog opens.
2

Set the date range, the status, and for a usecase campaign the usecase

The date range starts as the last 7 days. The dialog shows how many rows match and previews the first rows.
3

Select Export

The export runs in the background. A download appears when the file is ready.
The row count is exact up to 5,000 rows. Above that, it reads 5,000+ rows. When a filter makes the count inexact, it reads At least N rows. The export itself checks every matching row, up to the limit below. The file lists the newest rows first and stops at 100,000 rows. The dialog warns about this when a lot of rows match, and the finished export and the file both say where it stopped. Its columns are Called at, Recipient, Number, Status, Error code, Error message, Request ID, Sent at, Delivered at, Read at, and Cost (credits). A campaign that sends usecases also has Usecase and Template columns after Called at. Recipient, Number, and Error message are blank for an end user whose data was erased. A file made before the erasure keeps these values until it expires, up to 7 days after the export. The export never includes the request data. After a reply, that data lives with the conversation. For a campaign that sends usecases, the Analytics tab also breaks results down by usecase. The breakdown shows sent, delivered, read, replied, failed, and cost for each usecase.

Reply attribution

Reply-to-delivery attribution connects each campaign delivery to the end user’s later responses. A reply is credited to the campaign that prompted it, so reply counts reflect real campaign impact. The same data drives the Replied column on the Campaigns card in Analytics. See Handle campaign replies.

See campaigns inside Analytics

Campaign data also appears on the organization-wide Analytics page. The Campaigns card lists each campaign with Sent, Delivered, Replied, and Reply rate. See Read the Analytics cards.

Verify

Export the CSV. The row count in the toast matches the number of recipients the table lists for the campaign.