> 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-achievements/6-4-referees-made-the-transactions-for-2-consecutive-days-configuration.md).

# #6 Shopping Buddies – Four referees made transactions for two consecutive weeks

{% hint style="info" icon="cart-shopping-fast" %}

### Business case

Reward members only when they refer active, shopping users.

This setup encourages referred members to stay active for more than one week.

**💡 Useful for** increasing ACV (average customer value).
{% endhint %}

### 🛠️ Step by step

{% stepper %}
{% step %}

### Step 1: Challenge info

* **Name:** Four referees made transactions for two consecutive weeks
* **Availability:** Always available
* **Status:** Active
  {% endstep %}

{% step %}

### Step 2: Milestone

* **Milestone type:** Referral milestone
* **Trigger:** Purchase transaction
* **Progress tracking:** Number of event occurrences
* **Goals:**

  * Occurrence: Streak
  * Streak type: Weekly streak
  * Goal per week: 4 referees
  * Streak period: 2 weeks in a row
  * **Count only one transaction from each referee**: enabled

  ![](https://content.gitbook.com/content/JYxbcM03fnO79kn9uY8G/blobs/5Bgfn27TdvLDhCj7vH2F/image.png)

{% hint style="warning" %}
To meet this goal, transactions from any referees count. The qualifying referees can be different each week.
{% endhint %}

**Rules & Effects**

* **Trigger type:** Challenge completion
* **Effect:** Add units to wallet, issue a coupon, or grant another reward
  {% endstep %}

{% step %}

### Step 3: Limitation & Budget

* **Effect application per member:** 1 per year
* **Budget:** Unlimited, or set a cap if needed
  {% endstep %}

{% step %}

### Step 4: Review and Save

Review the setup, then save and activate the challenge.
{% endstep %}
{% endstepper %}


---

# 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-achievements/6-4-referees-made-the-transactions-for-2-consecutive-days-configuration.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.