> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/getting-insights.md).

# Insights

Once you send an email campaign, you can track the detailed results about its recipients.

### Overview

Once you send an email campaign, you can follow and see:

* Which emails were **delivered**
* Which emails were **bounced**
* Which emails were **opened**
* Which emails were **clicked**
* Which emails were **unsubscribed**

These metrics help you understand what’s working and who is engaging—so you can follow up with the right people at the right time.

You can also view delivery and open activity at the individual contact level directly within each contact’s History tab.

{% embed url="<https://rechatq.wistia.com/medias/7r3rlafh0n>" %}

### Getting Basic Stats on Campaigns

{% tabs %}
{% tab title="🖥️ Desktop" %}
Navigate to **Marketing → Insights → Sent** to view a list of your email campaigns.

![](https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJZySovZjoLVT1XAonI%2F-MKEIYx-MJsL4-fD9_sA%2F-MKEXSDJH0uIr3BbGP2r%2FScreenshot_20201022_020029.png?alt=media\&token=6ad7651b-aa2c-4b9f-a1ae-413811a178ab)

In this example:

* **403 recipients** were targeted
* **391 delivered**
* **151 opened**
* **3 clicked**

{% hint style="info" %}
These metrics are counted per unique recipient. Multiple opens or clicks from the same person are only counted once.
{% endhint %}
{% endtab %}
{% endtabs %}

### Viewing Recipient-Level Engagement

You can drill into any campaign to see how individual recipients engaged with your email.

{% tabs %}
{% tab title="🖥️ Example: See who clicked on your email" %}

1. Go to **Marketing → Insights**
2. Select a campaign
3. Use the **Sort** option (top right)
4. Choose **Most Clicked** (or other filters)

This allows you to quickly identify your most engaged contacts.

{% hint style="success" icon="star" %}
***Pro Tip:*** Combine this with Contact History to see a full timeline of that contact’s activity.
{% endhint %}
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**Understanding Open Tracking**

Open rates are tracked using a small, invisible image embedded in each email.

Because of this:

* Open tracking depends on the recipient’s email client
* If images are blocked, opens may not be recorded

*This means open rates are a helpful indicator—but not always 100% precise.*
{% endhint %}

{% content-ref url="/pages/fMBmcjgtFPrvzx5bdcmB" %}
[Understanding Bounces and Unsubscribes](/guides/marketing/email-deliverability/understanding-bounces-and-unsubscribes.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rechat.com/guides/marketing/getting-insights.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.