> ## Documentation Index
> Fetch the complete documentation index at: https://hellotars.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Read campaign reports

> Follow a campaign's funnel, daily trends, recipient-level results, exports, and reply attribution.

export const urls = {
  app: "https://dashboard.hellotars.com",
  site: "https://hellotars.com",
  support: "mailto:support@hellotars.com",
  status: "https://status.hellotars.com"
};

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 <a href={urls.app}>the dashboard</a> and select the organization you want to work in.

* You have an audience campaign that has started sending. See [Create a campaign](/docs/guides/campaigns/create-a-campaign).
* A webhook campaign has no **Analytics** tab. It reports each call on its **Activity** tab instead. See [Run webhook campaigns](/docs/guides/campaigns/webhook-campaigns).

## Open the report

<Steps>
  <Step title="Open Campaigns and select your campaign">
    The campaign page opens with its **Edit** and **Analytics** tabs.
  </Step>

  <Step title="Select the Analytics tab">
    The report shows the funnel, daily trends, and the recipient table.
  </Step>
</Steps>

## 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**. 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. Admins and Members can also use **Search name or number…** to find one end user.

## Export recipient activity

Export the recipient activity to CSV from the report. The file downloads directly in your browser, and a toast reports how many recipient rows were exported.

## 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 campaign funnel table on the **Goals** page. See [Handle campaign replies](/docs/guides/campaigns/handle-replies).

## See campaigns inside Analytics

Campaign and ad-source data also appear in the organization-wide **Analytics** tab. In **Explore**, campaign is available as a breakdown dimension, so you can compare campaigns against other traffic sources. See [Explore](/docs/guides/analytics/explore).

## Verify

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

## Related pages

* [Campaigns overview](/docs/guides/campaigns/campaigns-overview)
* [Analytics overview](/docs/guides/analytics/analytics-overview)
* [Fund your campaign wallet](/docs/guides/campaigns/campaign-wallet)