> 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/setup-your-campaign.md).

# Setup your campaign

Choose between serving your campaign in mediarithmics and tracking one served elsewhere, then get it running.

## Your goal

Get a campaign object live in mediarithmics, ready to receive exposures and, later, conversions.

## Expected outcome

A campaign that is either a DCO campaign set up in mediarithmics, or mirroring impressions and clicks from the adserver you already use.

## Which route to take

<table data-search="false"><thead><tr><th width="200">Take this route</th><th>When</th></tr></thead><tbody><tr><td><strong>Display campaign</strong></td><td>You want a DCO campaign, so the message can adapt to the user from your CDP data.</td></tr><tr><td><strong>Campaign tracking</strong></td><td>The campaign already runs through a DSP, a social platform, or a publisher's adserver, and you only need its exposures in your datamart.</td></tr></tbody></table>

{% hint style="danger" %}
Campaign tracking requires **campaign auto-setup** to be activated on your account first. Check with your account manager, and ask them for your **Datamart Token** at the same time: you need it for the pixels.
{% endhint %}

## Set it up

{% tabs %}
{% tab title="Display campaign" %}
You set up a DCO campaign in mediarithmics.

{% stepper %}
{% step %}

### Import your creative

Go to **Creatives** and add a new display ad. Choose **Html**, the type for a DCO campaign.
{% endstep %}

{% step %}

### Create the campaign

Go to **Campaigns**, create a new campaign, and add the creatives you just imported.
{% endstep %}

{% step %}

### Get your snippet

Open the campaign and use **Get your Snippets** to select the adserver you will implement it in, and get the matching macro.
{% endstep %}
{% endstepper %}

See [Display campaigns](/measurement-and-attribution/measure-and-optimize/track-your-campaign/display-campaigns.md) for the full walkthrough.
{% endtab %}

{% tab title="Campaign tracking" %}
You serve the campaign elsewhere and mirror it here with two pixels.

{% stepper %}
{% step %}

### Decide your technical names

You need a campaign technical name, a sub-campaign technical name, and a creative technical name. Some activation tools provide macros that fill these in automatically.
{% endstep %}

{% step %}

### Generate the impression pixel and the click tag

One pixel for viewers, one click-tracking URL for clickers.
{% endstep %}

{% step %}

### Add them to your banners

Once triggered, they populate the campaign's exposed and clicker segments in real time.
{% endstep %}
{% endstepper %}

See [Campaign tracking](/measurement-and-attribution/measure-and-optimize/track-your-campaign/campaign-tracking.md) for the full walkthrough.
{% endtab %}
{% endtabs %}

## Verify

* The campaign appears in **Campaigns**, findable by its campaign name.
* For a display campaign, the snippet resolves and serves the creative in a test placement.
* For campaign tracking, triggering the pixel and the click tag creates the two campaign segments, and they populate as expected.

## 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 campaign performance</strong></td><td>Once it is live, read what it delivered.</td><td><a href="/measurement-and-attribution/measure-and-optimize/track-your-campaign/measure-campaign-performance.md">Measure campaign performance</a></td></tr><tr><td><strong>Goals and attribution</strong></td><td>Attach goals so conversions get credited to this campaign.</td><td><a href="/measurement-and-attribution/measure-and-optimize/track-your-campaign/goals-and-attribution.md">Goals and attribution</a></td></tr></tbody></table>


---

# 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/setup-your-campaign.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.