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

# Offers

> Add destination URLs, preserve attribution, and choose how offers enter a campaign.

An offer is the destination you want visitors to reach, such as a purchase page, signup form, or affiliate offer. Metricanic stores its URL and uses it in a campaign's rotator.

Creating an offer does not send traffic to it. Add the offer to a campaign path and use the campaign's tracking integration. That is where Metricanic registers the visitor and expands its URL macros.

## Choose the right route

A rotator path has two destination choices:

| Choice           | Visitor journey                                                  | When to use it                                                      |
| ---------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------- |
| Offers only      | Campaign arrival goes straight to an offer                       | The offer page is the intended first destination                    |
| Landers & Offers | Visitor sees a landing, then follows its tracked CTA to an offer | A presell, comparison, or explanation page belongs before the offer |

These are path destinations. **Direct Script Mode** is a separate campaign integration choice that registers arrivals through a page script.

For a redirect campaign, an external affiliate offer does not require you to install code on the offer page. To use the offer page as an arrival page in Direct Script Mode, you need access to install the script and the page must be configured in an eligible Offers only path. See [tracking modes](/tracking/modes).

## Add an offer

1. Open **Offers** and click **Create**.
2. Enter **Name** and the complete **URL**. Use an HTTPS URL that visitors can open.
3. Choose **Country**. Use **Global** for an offer you intend to reuse across countries, or the specific country used by the campaign or rotator.
4. Select **Affiliate network** if the offer belongs to one. It is optional for your own destination.
5. Add the required tracking macros and save.

The URL must start with `https://`. Embedded username/password credentials, localhost, and private IP destinations are rejected. For a local development page, use an accessible HTTPS test deployment.

Country controls which assets can be combined in a campaign or rotator. It does not block visitors from other countries. Use [rotator rules](/tracking/rotators) when the visitor's country should affect routing.

## Pass the Metricanic click ID

A conversion sender needs the Metricanic click ID to attribute its callback. Include `{click_id}` in the offer parameter that sender will preserve.

For a page you control:

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

Your page receives the expanded click ID in `tracker_id` and the first captured source token in `creative`. Your backend can store them with the lead or order, then return the click ID in an [incoming event](/conversions/incoming-events).

For an affiliate network, use its supported parameter instead. Selecting a network with click ID defaults can enable **Append click ID** and add the suffix automatically. The offer URL remains the value to inspect. When the helper is enabled, its parameter must appear exactly once with `{click_id}` as its value.

Use **Macros for this URL** to insert supported Metricanic macros. The [macro guide](/tracking/url-macros) explains their values and the difference between Metricanic and source placeholders.

## Add it to a campaign

Open the campaign's **3. Rotator** tab. In a campaign-only rotator, select a path under **Default Paths**, then select the offer in that path. For a shared rotator, edit the shared configuration or copy it to a campaign-only rotator first.

Start with one enabled offer. Add more offers and adjust their relative weights when you are ready to compare destinations. With multiple landings and offers in one path, any landing can be paired with any offer. Use separate paths if particular landings must lead only to particular offers.

Offer records can be reused. Editing a shared offer URL changes the destination configuration for the routes using that offer. Create a separate offer when a test should have its own URL and reporting identity.

## Check the complete handoff

Open the saved campaign link, or the direct page's generated Traffic URL, and follow the intended journey. Verify the final destination and the request containing the click ID. If a landing is involved, test its tracked CTA rather than opening the offer URL manually.

If the offer is missing from a selector, check its country and archive status. If a conversion cannot be attributed, check the actual expanded click ID and whether the destination preserved it through subsequent redirects or form submission.

Finally, send one attributed test event and confirm the result in the campaign report. An offer URL loading successfully does not by itself verify conversion tracking.