> 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/audience-and-activation/build-your-audiences/segment-reference/segment-types/campaign-segment.md).
# Campaign segment
The two segments a tracked campaign creates for you: the users exposed to an ad, and the users who clicked it.
## What it is
**Campaign segments** are created automatically for every tracked campaign. You do not create them; tracking a campaign creates them for you, and they appear in the segments list with the type `Campaign`.
Each campaign produces two:
| Segment | Who is in it |
| -------------------------------- | ------------------------------------------------------- |
| *`campaign_name`* **- Exposed** | Every user that was exposed to an ad from the campaign. |
| *`campaign_name`* **- Clickers** | Every user that clicked on an ad from the campaign. |
## Why they matter
They are the raw material of retargeting. Most consumers need several exposures before they convert, so being able to separate "has seen this" from "has clicked this" lets you adapt the next message to the level of engagement rather than treating the whole audience the same way.
Typical uses:
* Get insight into the population exposed to a campaign, or the population that clicked.
* Cross a campaign segment with the audience you originally targeted, to see who you actually reached.
* Retarget an exposed-but-not-clicking audience with a different message.
## How they get populated
Campaign tracking works through two tags placed in your banners - one pixel for impressions, one tag for clicks - which bring impressions and clicks back into the platform. Generating them requires at least a campaign technical name, a sub-campaign technical name, and a creative technical name. Some activation tools provide macros that fill those technical names automatically when the pixels are embedded in a template.
Campaign tracking itself, including the pixel generation procedure, belongs to the **Measurement & Attribution** section.
{% hint style="warning" %}
Campaign auto-setup must be active on your account before the segments are created. Your Account manager confirms that, and provides your datamart token.
{% endhint %}
## Real-time membership, daily counts
This is the one behaviour to internalise about campaign segments:
* **Membership is real time.** Segments are populated as impressions and clicks arrive, and feeds activated on them share new users in real time too.
* **The count shown in the platform is not.** Segment counts are calculated once a day.
{% hint style="info" %}
To get the exact count at a given moment rather than yesterday's, query the segment directly in the query tool:
```sql
SELECT @count{} FROM UserPoint where { segments { id = "1234" } }
```
{% endhint %}
See [Check your audience reach and stats](/audience-and-activation/analyze-your-data/check-your-audience-reach-and-stats.md) for the wider version of that distinction.
## Related pages
Build your audience from live user activity
The other ways to build an audience that reacts as behaviour happens.
---
# 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/audience-and-activation/build-your-audiences/segment-reference/segment-types/campaign-segment.md?ask=&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.