> For the complete documentation index, see [llms.txt](https://docs.tracknow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tracknow.io/integrations-and-tracking/tracking-url-passed-parameters.md).

# Tracking URL Passed Parameters

Each [landing page](/campaigns/landing-pages.md) you create in Tracknow automatically generates a unique tracking URL for every affiliate with access to that page.

Affiliates use this URL to promote the landing page by sharing it across their channels. When a user clicks the tracking link, they are redirected to the corresponding landing page.

By default, the tracking URL looks like this:

```
https://{YOUR NAMESPACE}-tracking.tracknow.info/click?campaign_id={VALUE}&ref_id={VALUE}
```

You can also setup a [custom sub-domain](/customizations/custom-domain.md) so that tracking URLs will appear from your domain, for example:

```
https://example.yourdomain.com/click?campaign_id={VALUE}&ref_id={VALUE}
```

***

### Default Parameters

Tracking URLs always include the following parameters:

* `campaign_id` – identifies the Tracknow campaign associated with the landing page
* `ref_id` – identifies the specific affiliate link that was clicked

When a user clicks on the tracking URL, Tracknow generates a click record and stores these parameters on that click record.

Whenever a conversion postback is sent to our system indicating a specific `click_id` (a click record identifier), the conversion attribution is based on these parameters.

* The `campaign_id` value will determine under which campaign this conversion will be added
* The `ref_id` value will determine which affialite will receive the commission for that conversion.

Click records can be seen on your Tracknow dashboard under **Logs** → **Clicks**

***

### Additional Parameters

You can also append additional parameters to a tracking URL, which will be captured and stored with the click record.

When a conversion is later reported via postback using the corresponding `click_id`, it inherits all parameters associated with that click, including any custom values passed in the original tracking URL.

Navigate to **Campaigns** → Click on the name of the relevant campaign → **Tracking Tools / Creatives** → **Landing Page** section → Click the small **arrow** at the top right corner to reveal supported parameter keys

<figure><img src="/files/r05L7O0vcc1RU3PtZbBn" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="154">Field</th><th width="144">Parameter Key</th><th>Description</th></tr></thead><tbody><tr><td>UTM Source</td><td>utm_source</td><td>Google Analytics dedicated parameter. Used to pass a UTM Source value</td></tr><tr><td>UTM Medium</td><td>utm_medium</td><td>Google Analytics dedicated parameter. Used to pass a UTM Medium value</td></tr><tr><td>UTM Content</td><td>utm_content</td><td>Google Analytics dedicated parameter. Used to pass a UTM Content value</td></tr><tr><td>Goal</td><td>goal</td><td>Allows you to pass a <a href="https://docs.tracknow.io/payouts/goal-based-payouts">goal value</a> that is stored with the click record. When a conversion postback is later received with the corresponding <code>click_id</code>, the system uses this stored goal value to trigger the payout configured for that specific goal.</td></tr><tr><td>Sub 1</td><td>sub1</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 2</td><td>sub2</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 3</td><td>sub3</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 4</td><td>sub4</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 5</td><td>sub5</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 6</td><td>sub6</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 7</td><td>sub7</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>Sub 8</td><td>sub8</td><td>A parameter for any text or values you want to pass that don’t have a dedicated parameter</td></tr><tr><td>IDFA</td><td>idfa</td><td>IDFA is a random device identifier assigned by Apple to a user’s iOS device</td></tr><tr><td>GAID</td><td>gaid</td><td>Google Analytics dedicated parameter. Used to pass a Google Advertising ID value</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tracknow.io/integrations-and-tracking/tracking-url-passed-parameters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.