> 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/campaigns/creating-campaigns.md).
# Creating Campaigns
Campaigns are the core unit for configuring and managing your affiliate program.
Typically, a separate campaign is created for each website where tracking is implemented. However, multiple campaigns can also be used for the same website when different setups or objectives are required.
Within a campaign, you can control:
* Which affiliates are eligible to participate
* Which landing pages affiliates can promote
* What tracking parameters are passed to each landing page
* The commission structure and payout terms
* Affiliate contests and performance incentives
***
### Campaigns Screen
Navigate to **Campaigns**
This screen displays the complete list of your campaigns.
From here, you can create new campaigns, edit existing ones, and manage their status, including activating, pausing, or disabling them.
You can also use the filter bar to quickly locate specific campaigns.
***
### Creating a New Campaign
Navigate to **Campaigns** → Click **Add Campaign**
---
# 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/campaigns/creating-campaigns.md?ask=&goal=
```
`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.