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

# Campaigns

> Stand up a referral campaign in minutes - a destination, a conversion form, partner links, and a reward - all tracked end to end.

> A campaign is the container for a referral program: pick a destination and a conversion form, decide how partners earn, and generate the links that make it all trackable.

## What it does

An affiliate campaign defines a referral program in one place. You set the destination partners
send traffic to, choose the conversion form that captures a result, and decide how partners are
rewarded, either a fixed amount per conversion or through a commission plan. You then generate
trackable links for the partners you enroll, and the campaign tracks clicks, conversions, and
commission from there.

Each campaign is self-contained, with tabs for its general settings, commission, links,
conversions, traffic quality, and installation. Partners can see their own campaign view in the
portal once you generate their links. The whole program is run by your team, no engineering
required beyond installing a small tracking snippet.

## The problem it solves

Referral programs usually mean untracked links and guesswork about who drove what:

* **Referrals are untracked** → A campaign generates trackable links per partner.
* **Rewards are manual** → Pay a fixed amount per conversion or use a commission plan.
* **You cannot see what works** → Each campaign tracks clicks, conversions, and commission.
* **Partners have no visibility** → Partners see their own campaign view in the portal.

## From problem to solution

Campaigns make referral programs measurable. Define the destination, form, and reward, generate
links, and track everything in one place. Partners get visibility, and you get attributed results
tied to your CRM and commissions.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  define["Define destination, form, reward"] --> links["Generate links"]
  links --> track["Track results"]
  track --> crm["Tied to CRM and commissions"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Launch a referral program" icon="circle-check">
    Set up a campaign in minutes.
  </Card>

  <Card title="Reward conversions" icon="circle-check">
    Pay per conversion or via a plan.
  </Card>

  <Card title="Track end to end" icon="circle-check">
    See clicks, conversions, and commission.
  </Card>

  <Card title="Give partners visibility" icon="circle-check">
    Show each partner their campaign performance.
  </Card>
</CardGroup>

## Impact

* **Time to value** - Spin up a campaign and its tracked links the same day, so a new push goes live while the moment is hot.
* **CRM-native** - Conversions and rewards reconcile to your CRM and commissions.
* **Low total cost of ownership** - Partner marketing runs campaigns with no engineering.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Marketing" icon="user">
    Designs and launches referral campaigns.
  </Card>

  <Card title="Partner Operations" icon="user">
    Configures campaigns and enrolls partners.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Links & Attribution" icon="share-nodes" href="/features/affiliate/links-attribution">
    Each campaign issues tracked links.
  </Card>

  <Card title="Conversion Tracking" icon="share-nodes" href="/features/affiliate/conversion-tracking">
    Measure a campaign by the conversions it drives.
  </Card>

  <Card title="Commission Plans" icon="hand-holding-dollar" href="/features/commissions/commission-plans">
    Pay campaign conversions out on a plan.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>
