> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/sell-on-lid/links-and-campaigns.md).

# Links and campaigns

Tracked links and reward campaigns: define the result, fund the pool, let anyone share, and the sharer's reward becomes payable when you approve the result.

Create a tracked link, define what counts as a result, and pay the people who bring results.

## Tracked links

Open **Campaigns** in your [dashboard](https://lid.pro/dashboard), pick the site your link points to (or add it), and create a short link. You see clicks, events and results per link. Use links on their own or inside a reward campaign.

## Reward campaigns

1. Create a campaign and define the result that counts: a signup, a purchase, any event you name.
2. Fund the reward pool. The pool stays in your control until a result verifies.
3. Open it up. Anyone can click **Generate my link** to get their own version.
4. When a visitor hits the goal, the result lands in your dashboard for review. The moment you approve it, the reward becomes payable from the pool to the sharer who brought it, and it shows as paid once the payment confirms.

Each sharer sees their own clicks, results, and earnings under **My shared links**, in **Affiliates**.

## FAQ

<details>

<summary>How long does a sharer get credit for a visitor?</summary>

You set the window per campaign, from 1 to 90 days. The default is 7 days.

</details>

<details>

<summary>Is there a fee?</summary>

The flat 3% applies to the budget when you fund the pool, the same as a challenge.

</details>

Start a campaign at [lid.pro](https://lid.pro). That is the link if you want to sell.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lid.pro/sell-on-lid/links-and-campaigns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.