> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/measurement-and-attribution/measure-and-optimize/track-your-campaign/measure-campaign-performance.md).

# Measure campaign performance

Read what a campaign delivered while it runs, and who it reached.

## Your goal

Know how a campaign is delivering while it is live: impressions, clicks, and the users it reached, before you get to whether it converted anyone.

## Expected outcome

A performance view for the campaign over time, and the reach of its exposed and clicker segments.

## Read delivery over time

On the **Display** tab you can see the performance of your campaign over time.

## Read the reach of the exposed and clicker segments

Every tracked campaign automatically maintains an exposed segment and a clicker segment. Read their size and composition the way you would for any segment: see **Check your audience reach and stats** in the **Audience & Activation** section, under *Analyze your data*.

{% hint style="warning" %}
Segment counts displayed in the platform are recalculated once a day, even though campaign segment membership updates in real time. If you need the exact figure at a given moment, query the segment directly rather than reading the displayed count. The query is on [Campaign tracking](/measurement-and-attribution/measure-and-optimize/track-your-campaign/campaign-tracking.md#what-it-produces).
{% endhint %}

## Verify

* The Display tab shows non-zero impressions and clicks once the campaign is live.
* The exposed and clicker segment counts move as the campaign delivers.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Measure attribution</strong></td><td>Delivery is not conversion. Decide how to credit the outcome.</td><td><a href="/measurement-and-attribution/measure-and-optimize/track-your-campaign/measure-attribution.md">Measure attribution</a></td></tr><tr><td><strong>Analyze conversions</strong></td><td>Conversion volumes and revenue once goals are firing.</td><td><a href="/measurement-and-attribution/measure-and-optimize/analyze-conversions.md">Analyze conversions</a></td></tr><tr><td><strong>Campaign tracking</strong></td><td>The segments this page reads.</td><td><a href="/measurement-and-attribution/measure-and-optimize/track-your-campaign/campaign-tracking.md">Campaign tracking</a></td></tr></tbody></table>

{% hint style="info" %}
To put the exposed or clicker segment next to another audience, see **Compare segments** in the **Audience & Activation** section, under *Analyze your data*.
{% endhint %}


---

# 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.mediarithmics.io/measurement-and-attribution/measure-and-optimize/track-your-campaign/measure-campaign-performance.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.