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

# Connect CreatorTraffic to OnlyFans API Smart Links (/introduction/guides/creatortraffic-smart-links)

import { Step, Steps } from "fumadocs-ui/components/steps";

## What the CreatorTraffic integration does

CreatorTraffic is a traffic source for OnlyFans media buyers. This integration reports new subscribers attributed through a configured OnlyFansAPI Smart Link back to CreatorTraffic.

**Why connect it?** Once connected, OnlyFansAPI reports each attributed new subscriber with a captured CreatorTraffic click ID. No JavaScript is installed on OnlyFans, and the connection uses one CreatorTraffic API token.

## Watch the walkthrough

<iframe className="aspect-video w-full" src="https://www.youtube.com/embed/4hhq2JGdS-w" title="CreatorTraffic × OnlyFans API Smart Links integration walkthrough" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerPolicy="strict-origin-when-cross-origin" allowFullScreen />

## Step-by-step setup

<Steps>
  <Step>
    ### Open your CreatorTraffic settings

    Go to [ads.creatortraffic.com/settings](https://ads.creatortraffic.com/settings) and choose **Settings** from the sidebar.

        <img alt="CreatorTraffic settings menu" src={__img0} placeholder="blur" />
  </Step>

  <Step>
    ### Generate and copy your API token

    In **API Access**, click **Generate API Token**, then copy the token.

        <img alt="CreatorTraffic API token field" src={__img1} placeholder="blur" />

    <Callout type="warn">
      If the **Generate API Token** button is unavailable, ask your CreatorTraffic account manager to enable API access on your account.
    </Callout>
  </Step>

  <Step>
    ### Connect it in OnlyFans API

    First open **Smart Links → Traffic Sources** and create a **CreatorTraffic** source with an `utm_source` rule equal to `creatortraffic`. See [Traffic sources](/introduction/guides/onlyfans-meta-pixel-smart-links#traffic-sources) for the matching workflow.

    Then open **Smart Links → Tracking Pixels**, click **Add Pixel**, select **CreatorTraffic**, and paste the token into **API Token**. Choose **Specific traffic sources**, select CreatorTraffic, and click **Create**.

    Finally, open **Smart Links → Links**, edit the Smart Link, and select the CreatorTraffic connection in **Tracking Pixels**. A pixel created from the Tracking Pixels page is not attached to a Smart Link automatically.
  </Step>

  <Step>
    ### Add the click ID to your Smart Link URL

    Copy your Smart Link and append CreatorTraffic's click-ID parameters to the ad's destination URL so each conversion can be matched back to the click that drove it:

    ```text
    https://trk.of-traffic.com/go/YOUR_SMART_LINK_ID?ecid={clickid}&utm_source=creatortraffic
    ```

    Replace `YOUR_SMART_LINK_ID` with the ID from your Smart Links dashboard. CreatorTraffic replaces `{clickid}` with the click's ID at click time, and Smart Links reads it from the `ecid` parameter. Each attributed new-subscriber conversion sends that ID back to CreatorTraffic. The `utm_source=creatortraffic` value matches the traffic-source rule described above. Keep both parameters on the URL.

    <Callout type="warn">
      `{clickid}` must be placed where CreatorTraffic controls the URL so it can replace the macro. If you use a landing page or pre-lander between CreatorTraffic and the Smart Link, it must forward both `ecid` and `utm_source`. Built-in Smart Links pre-landers forward these parameters; an arbitrary link-in-bio page may not.
    </Callout>

        <img alt="CreatorTraffic ad destination URL with click ID parameters" src={__img2} placeholder="blur" />
  </Step>

  <Step>
    ### You're done

    New subscribers attributed to that Smart Link are now postbacked to CreatorTraffic using the click ID. They'll show up against the matching campaign in your CreatorTraffic reports.
  </Step>
</Steps>