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

# How to read the campaign report

> Metrics, delivery funnel, interactions by block, the per-contact list and the exports.

## What you will learn

What each section of the report shows and how to investigate from the aggregate number down to the individual contact. Metric definitions live in [Understand the metrics](https://docs.cliqo.io/en/relatorios/entenda-metricas.md) — this is the map of the screen.

## The top: campaign numbers

Seven cards: **Sent** (with delivered and the delivery rate), **Placed revenue** (all time), **Opens** (estimated ⓘ, % of delivered), **Clicks** (human, % of delivered), **AMP interactions** (people who acted inside the email, with the **AMP rate**: of the opens whose version was identified, how many were the interactive one), **Conversions** and **Avg. ticket**. Sent, revenue and opens compare with the WhatsApp report; the other four only exist for email. Right below, the **render type** shows how many opened AMP vs. HTML, and **From send to click** shows each step over the previous one (delivered, opens and clicks — the last one, over opens, is the CTOR).

If **"AMP disabled for this dispatch"** appears, the interactive part failed validation (or the validator failed to load on the server) and the send went out in the safety version (HTML) for everyone — the notice lists the errors found.

## Dispatch details

The **How it looks in the inbox** card brings together sender, subject and preheader, the way the recipient sees them. Under **Dispatch details**: **Audience** (deduplicated contacts and the lists and segments used), **Send window** (time and duration) and **Tracking** (the UTMs, with **Copy query string**); at the bottom, who sent it (a person or the automatic schedule) and the internal ID. The **Preview** button, at the top, opens the **dispatch preview** — what was sent in this dispatch, with AMP degraded to HTML.

## Delivery of sent

The funnel splits the sent into seven destinations that **always add up to the total**: delivered, soft bounce (temporary rejection), hard bounce (permanent), complaint (marked as spam), suppressed (blocked before going out), pending and failures. Below the sum, **After delivery** shows the **Unsubscribes from this campaign** — already counted in delivered.

Right below, **Excluded from send** explains who was in the audience and didn't receive, reason by reason: were already blocklisted, had already unsubscribed, hard bounce or complaint history, suppression, filtered by the segment, no consent. Campaigns sent up to October 1, 2026 may also show "collision with a recent flow": since then, a campaign no longer leaves out people who got an automation. Anyone who had already received it on a resume of the same send isn't counted there.

## Interactions by block

For interactive emails: each block (wheel, survey, form, carousel…) with unique and total interactions and the most frequent values — which prize came up most, how many spins, how many products selected. This is where interactivity turns into insight.

## By contact

The table lists every recipient: delivery, opened, clicked, interacted, **bought** (with the amount, when known) and which version they saw (render). Search accepts a name or email, and the filter makes investigating fast — only those who purchased, only those who complained, only delivery failures. Bot clicks and machine opens (Apple) appear **flagged**, not hidden. Clicking the email opens the contact's profile without leaving the report.

## Export and act

* **Export CSV** — at the top, the campaign summary; in the **By contact** card, the recipient list with whatever search and filter are active.
* **Send test** — straight from the report; the subject arrives with `[Test]` at the start, outside the metrics.
* **Resume sending** — shows up when the send failed or when the automatic resume stopped progressing; it sends only to the pending recipients, without duplicating.

## Related articles

* [Understand Cliqo's metrics](https://docs.cliqo.io/en/relatorios/entenda-metricas.md)
* [How to schedule and set the send pacing](https://docs.cliqo.io/en/campanhas/agendar-e-ritmo.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.