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

# Track partner campaign attribution

> Wire affiliate links and end-user forms so partner-driven clicks, leads, and conversions attribute back to each partner in your CRM.

> For partner marketing and RevOps turning partner campaign activity into attributed pipeline.

A partner campaign is only worth running if you can see what it drove. This guide wires the attribution behind a through-channel campaign: affiliate links that tag every click to the partner, end-user forms that capture leads, and the tie-in to a commission plan and announcement that turns attribution into activation. The result is a closed loop from partner outreach to attributed revenue in your CRM.

## What you'll achieve

Partner-driven clicks and form submissions attributed to the right partner in your CRM, feeding reporting on the pipeline and revenue a campaign generated, with the campaign tied to an incentive so partners are rewarded for the demand they create.

## Before you start

<Steps>
  <Step title="Have a campaign kit ready to distribute">
    The assets partners will launch with should already exist. See [Enable partners with a campaign kit](/features/content/tcma/guides/enable-partners-with-a-campaign-kit).
  </Step>

  <Step title="Confirm affiliate and forms are available">
    You need affiliate links and forms on your plan to capture attributed traffic and leads.
  </Step>

  <Step title="Confirm permission to manage commissions">
    You need access to commissions if you tie the campaign to a dedicated plan.
  </Step>
</Steps>

## Steps

### Wire attribution

<Steps>
  <Step title="Create partner-attributed affiliate links">
    Generate affiliate links so each partner's traffic is tagged to them. See [Affiliate Links & Attribution](/features/affiliate/links-attribution).
  </Step>

  <Step title="Add an end-user form to capture leads">
    Attach a form to the campaign destination so end-user submissions are captured and mapped to the partner. See [Set up affiliate conversion tracking](/features/affiliate/conversion-tracking/guides/set-up-affiliate-conversion-tracking).
  </Step>

  <Step title="Include the links and form in the kit">
    Add the attributed links and form to the campaign assets so partners launch with attribution built in.
  </Step>
</Steps>

### Activate and reward

<Steps>
  <Step title="Tie the campaign to a commission plan">
    Enroll participating partners in a dedicated commission plan so they earn on the demand the campaign drives. See [Commissions & SPIFFs](/features/commissions).
  </Step>

  <Step title="Announce the campaign">
    Send an announcement so partners know the campaign is live and incentivized. See [Send an announcement](/features/portal/announcements/guides/send-an-announcement).
  </Step>
</Steps>

## Verify it worked

Launch a test through the attributed link and submit the form: the click and submission appear attributed to the partner in your CRM. As conversions land, they roll up under that partner, ready for reporting on campaign-sourced pipeline.

## What your partners experience

Partners launch the campaign in their own tooling using the attributed links and form. Every click and lead they drive is credited to them automatically, and they earn through the commission plan tied to the campaign, no manual reporting or claims.

## Related

<CardGroup cols={2}>
  <Card title="Affiliate Links & Attribution" icon="link" href="/features/affiliate/links-attribution">
    Generate the partner-attributed links behind the campaign.
  </Card>

  <Card title="Set up affiliate conversion tracking" icon="book-open" href="/features/affiliate/conversion-tracking/guides/set-up-affiliate-conversion-tracking">
    Capture end-user conversions from partner campaigns.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full through-channel marketing configuration options.
  </Card>
</CardGroup>