> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/agency/reports/ad-email-report.md).

# Ad email report

The **Ad Email Report** provides detailed performance insights into ad emails — including sends, opens, and clicks — organized by advertiser, campaign, and creative. It helps ad agencies understand how users engage with email ads at different levels of granularity.

***

## 🧾 Report Structure

Each row in the report represents totals for ads at different levels of specificity:

* **Creative-level**: If the **Creative** column is filled, metrics apply to that creative.
* **Advertiser-level**: If both **Creative** and **Campaign** are blank, metrics roll up to the advertiser.

The **last row** summarizes metrics across all advertisers, campaigns, and creatives included in the report.

***

## 📋 Columns Explained

| **Column**                 | **Description**                                  |
| -------------------------- | ------------------------------------------------ |
| **Advertiser**             | The advertiser responsible for the ad campaign.  |
| **Campaign**               | The advertising campaign that the ad is part of. |
| **Creative**               | The specific ad variation (image and text).      |
| **Sent**                   | Number of ad emails sent.                        |
| **Recipients**             | Number of people who received the ad email.      |
| **Total opens**            | Total number of times ad emails were opened.     |
| **Unique opens**           | Number of distinct emails opened once.           |
| **Percent unique opens**   | Unique opens ÷ total opens.                      |
| **People opened**          | Number of people who opened an ad email.         |
| **Percent people opened**  | People who opened ÷ people who received.         |
| **Total clicks**           | Total number of email ad clicks.                 |
| **People clicked**         | Number of people who clicked on an ad email.     |
| **Percent people clicked** | People who clicked ÷ people who received.        |

***

## 🧰 Filtering Options

These optional filters allow you to refine which emails are included in the report:

| **Filter**               | **Description**                                           |
| ------------------------ | --------------------------------------------------------- |
| **Email sent from date** | Earliest date from which emails should be included.       |
| **Email sent to date**   | Latest date to include in the report.                     |
| **Date ranges timezone** | Timezone applied to date filtering.                       |
| **Businesses**           | Limits the report to emails sent to specified businesses. |
| **Advertisers**          | Filters the report by advertiser.                         |
| **Campaigns**            | Filters the report by specific campaigns.                 |

> ℹ️ **Note:** The date filters apply **only to email send dates**. **Open and click metrics are not restricted** to the same range.


---

# 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://docs.perkville.com/features/agency/reports/ad-email-report.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.
