> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/playbook/sample-setups/sample-campaigns/5-refer-a-friend-and-get-100-points.md).

# #5 Refer a friend and get 100 points

### #5 Refer a friend and get 100 points

**Business goals:**&#x20;

* Customer acquisition

**Loyalty mechanism:** Currency Referrals

**Description:**&#x20;

* With this campaign, members get bonus points for referring a friend.
* Reward points are added only when a new referred customer purchases something.
* Referral campaigns will allow you to constantly generate a stream of new customers referred by existing members.
* To configure this campaign we will have to use the referral type of the campaign and define a rule for the referrers.

**Default configuration:**&#x20;

<figure><img src="https://content.gitbook.com/content/JYxbcM03fnO79kn9uY8G/blobs/4PXt49UaPFCD6i34cIw3/image.png" alt=""><figcaption></figcaption></figure>

* **Campaign type:** Referral
* **Trigger:** Referee’s transaction
* **The rule for referrer:**
  * **Conditions:** The referee has done the first transaction *(Referee’s first transaction date -> Is after the date when the campaign was started)*
  * **Effects:** Give 100 points *(Add units -> Wallet type: Points wallet -> Calculation formula: 100)*

{% hint style="info" %}
**Actionable tips:**

* Avoid rewarding referrals based only on the registration in the loyalty program.
* Experiment with different types of effects like discount coupons instead of loyalty currency.
* Set up a limit for the number of referrals a day to avoid fraud e.g. 5 friends per customer daily.
* Consider setting up a minimum value for the referee's transaction to avoid generating a low-quality customer base.
  {% endhint %}

### Campaign JSON file to import

{% file src="/files/HN2QcCyWT6chUyRTmytw" %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/playbook/sample-setups/sample-campaigns/5-refer-a-friend-and-get-100-points.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 `build a script that syncs our docs to a CMS` 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.
