> 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.md). # Track your campaign Bring a campaign into mediarithmics, whether you serve it yourself or run it through another adserver, and measure what it did. ## Your goal Get one view of a campaign inside your CDP: its delivery, the users it reached, and the conversions it drove, whatever adserver actually serves it. ## Expected outcome A campaign object in mediarithmics that either serves your creatives directly or mirrors a campaign served elsewhere, with impressions and clicks landing on your users' timelines and available for segmentation, performance reporting, and attribution. ## What a campaign is A **campaign** in mediarithmics is the object you track delivery, exposure, and conversions against. There are two ways to get one.

Approach
Display campaign	You set up a dynamic creative optimisation (DCO) campaign in mediarithmics, driven by the data already in your CDP.
Campaign tracking	You serve the campaign through another adserver, and mirror it in mediarithmics with two pixels so the exposures land in your datamart.

Whichever route you take, every campaign you track automatically produces two segments: everyone exposed, and everyone who clicked. Crossing them with your own attributes or with other segments is what turns delivery into audience insight. These are **Campaign segments**, documented in the **Audience & Activation** section under *Build your audiences > Segment reference > Segment types > Campaign segment*. {% hint style="info" %} A display campaign can use the data mediarithmics already holds to show the right product or message to the right user. Common cases: display the last products the user viewed, display products from the same category, or display your best sellers in a category the user has already shown interest in. It can also draw on data sources beyond what your CDP collects, such as a product feed. {% endhint %} ## How the job breaks down The three pages below walk through the job end to end.


Setup your campaign	Choose your route and get the campaign running.	Setup your campaign
Measure campaign performance	Read delivery and reach once it is live.	Measure campaign performance
Measure attribution	Decide how to credit conversions back to the campaign.	Measure attribution

Each relies on one of the following mechanisms, documented in full for reference.


Display campaigns	Creating the creatives and the campaign for DCO.	Display campaigns
Campaign tracking	Mirroring a campaign served elsewhere with impression and click pixels.	Campaign tracking
Goals and attribution	Defining goals and the attribution model that credits conversions to a campaign.	Goals and attribution

## Related pages


Analyze conversions	Reading conversion volumes and revenue once goals are firing.	Analyze conversions
Build funnels	Following the steps between exposure and conversion.	Build funnels
Set up an A/B test	Isolating the campaign's incremental effect rather than just crediting it.	Set up an A/B test

--- # 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.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.