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

# Create your first campaign

> Build a simple redirect campaign and verify a visit and conversion from start to finish.

This walkthrough creates a campaign that redirects to one offer and records a test conversion. It uses a page you control so you can see the click ID before connecting an affiliate network.

The result is a verified attribution path:

```text theme={null}
Tracking link → your offer page with a click ID → test event → campaign report
```

You do not need a landing for this test. If your traffic must open a page directly, follow [Direct Script Mode](/tracking/modes) and [script installation](/tracking/landings) instead.

## 1. Prepare a domain and destination

[Add a tracking domain](/tracking/domains) and complete its DNS setup until it is active. Use a dedicated subdomain such as `trk.example.com`.

Have an accessible HTTPS page ready. The example below uses `https://offer.example.com/checkout`. Replace it with your own page. It must preserve the query string long enough for you to read the test click ID.

## 2. Add a test traffic source

Open **Traffic sources**, click **Create**, and choose **Custom**. Name it `Tracking test`.

In **Parameters**, configure the **Click ID** row:

| Field | Test value    | Meaning                            |
| ----- | ------------- | ---------------------------------- |
| Param | `extid`       | Incoming query parameter           |
| Macro | `test-ad-001` | A fixed value for this manual test |

Leave **Postback URL** empty and save. The fixed value lets you verify the source ID without buying traffic. Replace it with the actual source macro before using this source for ads. [Traffic sources](/tracking/traffic-sources) explains that mapping.

## 3. Add the offer

Open **Offers** and click **Create**. Enter a name such as `Test checkout`, choose **Global** for **Country**, and use this URL with your own hostname:

```text theme={null}
https://offer.example.com/checkout?tracker_id={click_id}
```

An affiliate network is optional for this example. Save the offer. Metricanic will replace `{click_id}` when it sends a visitor to this URL.

## 4. Connect the campaign

Open **Campaigns** and click **Create**.

1. In **1. Campaign**, enter a name, select `Tracking test`, and attach the active domain. Choose **302 Redirect Mode**, **Global**, and **Visit cost** → **none**.
2. In **2. Events**, choose **Simple**. This mode tracks Event ID `1` as a conversion and uses its incoming payout as revenue. Keep **Event cost** at **No event cost** and **Outgoing postback** off for the test. The conversion and revenue controls are preset in Simple mode.
3. In **3. Rotator**, select **Campaign-only Rotator**. Under **Default Paths**, add or select a path. Set **Path Destination** to **Offers only** and select `Test checkout`. Keep the path and offer enabled with their default weights.
4. Click **Save**, then open **4. Finish** and copy **Tracking link**.

## 5. Send one visit and one event

Open the tracking link in a browser. You should reach your offer page with a real value in `tracker_id`. Copy that complete value.

Replace `SIGNED_CLICK_ID` below with it and use your tracking hostname. Open the resulting URL once:

```text theme={null}
https://trk.example.com/event/SIGNED_CLICK_ID?idx=1&payout=12.50&txuid=test-order-001
```

A successful event request returns a tiny image, so the browser may look blank. A successful HTTP response alone does not verify the reporting result.

Use the Metricanic click ID from the destination URL. The example source ID `test-ad-001` is not valid in the event URL. Each genuinely new test transaction needs a new `txuid`. Repeating one transaction is not a reliable way to create another conversion.

## 6. Verify the report

Open the campaign report, choose a date range containing the test, and refresh after processing. For an otherwise unused campaign with one completed test, check:

| Metric      | Expected result                                   |
| ----------- | ------------------------------------------------- |
| Visits      | `1`                                               |
| Clicks      | `0`, because this flow has no tracked landing CTA |
| Conversions | `1`                                               |
| Revenue     | `12.50`                                           |
| Cost        | `0`                                               |

Test traffic and test revenue are real report data. Keep this campaign separate from production reporting.

If there is no visit, check the [tracking link and domain](/troubleshooting/no-visits-or-clicks). If the visit appears but the conversion does not, check the [click ID and event settings](/troubleshooting/no-conversions).

Once the test works, connect the real source's parameters and the advertiser's [incoming event callback](/conversions/incoming-events). If the advertiser uses an affiliate network, configure its [click ID handoff](/tracking/affiliate-networks).