> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metricanic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Campaigns

> Connect a traffic source, tracking mode, costs, events, and destinations in one campaign.

A campaign defines how Metricanic handles a stream of traffic. It connects one traffic source to a rotator, chooses the tracking integration, and sets how visits and later events contribute to your results.

Use separate campaigns when traffic needs different source mappings, visit costs, event definitions, or reporting separation. Reuse a shared rotator when several campaigns should follow the same destination rules.

For example, two ad networks can promote the same offer through separate campaigns. Each campaign captures its network's parameters and costs. Both can use the same shared rotator to distribute visitors between two landing variants.

## Prepare the connected elements

Create the [traffic source](/tracking/traffic-sources) and at least one [offer](/tracking/offers). Add [landings](/tracking/landings) if visitors should see a page before the offer. You can build destination rules inside the campaign or prepare a shared [rotator](/tracking/rotators).

An active [tracking domain](/tracking/domains) is needed before launch. You can save the campaign without one while preparing the rest of its configuration.

## 1. Campaign settings

Open **Campaigns**, click **Create**, and complete **1. Campaign**.

| Setting          | What to choose                                                                |
| ---------------- | ----------------------------------------------------------------------------- |
| Name             | A name that distinguishes this campaign in reports                            |
| Traffic source   | The source whose parameter mapping matches the incoming URL                   |
| Domain           | The tracking hostname used in generated links and scripts                     |
| Integration mode | How the visitor's arrival is registered                                       |
| Country          | The country used to organize the campaign and check destination compatibility |
| Allow prefetch   | Whether requests marked as prefetch may register visits                       |
| Visit cost       | How cost is assigned when a visit is registered                               |

**302 Redirect Mode** registers a visit when someone opens the tracking link, then redirects to the selected destination. **Direct Script Mode** registers a visit from the script on a configured arrival page. Direct mode requires control of that page's code. See [tracking modes](/tracking/modes) for the routing differences.

**Country** is not a visitor filter. For a single-country campaign, use offers and landings marked **Global** or with the same country. A Global campaign can use assets from different countries, but its attached shared rotator must be Global. To make routing depend on the visitor's detected country, use a rotator condition.

Changing Country can make the attached rotator or selected assets incompatible. Review the removal confirmation and check the remaining paths before saving.

**Allow prefetch** applies to requests that identify themselves as prefetch. With **no**, those requests are skipped. This is not a general bot filter, because it depends on the request headers.

Choose **none**, **auto**, or **CPV** for visit cost. The [cost guide](/tracking/costs) explains when each model fits.

## 2. Events

In **2. Events**, choose the smallest configuration that describes the outcomes you need:

* **Simple** tracks Event ID `1` as a conversion and uses the incoming payout as revenue. You can set its event cost and outgoing postback.
* **Advanced** supports multiple event IDs and conditional event rules, with separate controls for conversion counting and revenue.

Use Simple for one primary result, such as a purchase reported with its payout. Use Advanced for a funnel with signup and purchase events or different event treatment for particular conditions. Configure these in [events and goals](/conversions/goals).

Saving an Advanced campaign in Simple mode keeps only Event ID `1`. Review the confirmation before making that change.

## 3. Rotator

Choose **Campaign-only Rotator** for rules that belong to this campaign. Add a usable path under **Default Paths** with an enabled offer.

Choose **Use existing rotator** to share routing with other campaigns. **Edit shared rotator** changes that shared object. To make an independent starting copy, use **Copy to campaign-only rotator**. Merely switching the radio selection to Campaign-only does not copy the shared rules.

## 4. Save and launch

Click **Save**, then open **4. Finish**. In redirect mode, copy **Tracking link** to the traffic source. In direct mode, follow the generated instructions for the arrival page, script, and CTA link.

The Finish instructions represent the saved configuration. Save again after changing source, domain, or destinations, and recopy affected integration values.

Before paid traffic, complete a visit and an incoming event. Verify the destination, source parameters, cost, and conversion in the campaign report. The [first campaign walkthrough](/start/first-campaign) provides a complete test.