> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/referral-program/campaign.md).

# Campaign Setup

Your campaign is the strategy behind your referral program, written as rules — who can refer, what each side earns, how people share, and when a reward lands. One campaign record applies to every referral. Edit it from the **Campaign** tab.

> **Best practice:** Decide your reward economics *before* you open the campaign editor. Work out what a referred customer is worth to you, then set the combined referee + referrer reward below that number so every successful referral stays profitable.

### What a campaign controls

* **Who can refer** — see [Target audience](/referral-program/target-audience.md).
* **What both sides earn** — see [Referrer and referee rewards](/referral-program/rewards.md).
* **How referrers share** — see [Referral methods](/referral-program/referral-methods.md).
* **When rewards are issued** — minimum requirements, review period, and expiry, inside the rewards sections.

#### The four decisions, side by side

| Decision             | Wider / more generous     | Tighter / leaner                        |
| -------------------- | ------------------------- | --------------------------------------- |
| Who can refer        | More reach, more shares   | Higher-trust referrals, less fraud risk |
| What each side earns | More motivation to share  | Better margin per referral              |
| How they share       | Reaches more channels     | Simpler, but suppresses some shares     |
| When rewards land    | Fast, frictionless payout | More control, fewer bad payouts         |

At launch, lean toward the generous side of every lever to gather data; tighten selectively once you can see where the program leaks margin or trust.

### Set up your campaign

1. Open the **Campaign** tab.
2. Open **Target audience** and choose who can join as a referrer.
3. Open **Referrer reward** and **Referee reward** and set what each side earns.
4. Open **Referral method** and turn on a referral link, a referral code, or both.
5. Save.

### What triggers a reward

A referrer shares their link or code; a referee uses it and gets a discount. When the referee's order is marked paid in Shopify and passes your minimum requirements and fraud checks, the **referrer reward** is created. Sharing alone never issues a reward — only a real purchase does.

### When a reward is issued

Two settings control timing: the **review period** (a delay in hours before approval, `0` for instant) and any **minimum requirements** on the order. Suspicious orders go through a separate mandatory hold regardless of these settings.

### A worked example

*Illustrative, not measured Bloop results.* A subscription coffee store sets the audience to **customers with a completed order**, gives referees 25% off their first month (\~$10) and the referrer $10 store credit (against \~$20 profit per referred subscriber), turns on both link and code, and sets a 0-hour review period with no minimum and a 30-day code expiry. Then they track results in [analytics](/referral-program/analytics/analytics.md) and refine with an [A/B test](/referral-program/ab-testing.md).

### Common mistakes to avoid

* **Configuring rewards before knowing your numbers.** Work out the profit on a referred order first — that's the most expensive lever to guess at.
* **Starting narrow to "play it safe."** A tight audience or heavy minimums at launch starves the program of the data you need.
* **Turning off both sharing methods.** At least one of link or code must stay on, or the program stops entirely.

### Next steps

* Configure the two-sided rewards in [Referrer and referee rewards](/referral-program/rewards.md).
* Set who can refer in [Target audience](/referral-program/target-audience.md).
* Prove which setup wins with [A/B test your referral rewards](/referral-program/ab-testing.md).


---

# 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.bloop.plus/referral-program/campaign.md?ask=<question>&goal=<endgoal>
```

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