> 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/11-shopping-spree.md).

# #11 Shopping Spree

Reward members who spend €100 in May with a discount coupon and tier-qualifying units.

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

### Business case

A limited-time spending threshold can increase basket value during a quieter period.

Members who spend €100 during May receive a discount coupon and progress toward a higher tier.

**💡 Useful for** creating revenue spikes while making tier benefits more attainable.
{% endhint %}

{% hint style="warning" %}
This campaign involves these mechanics:

* [Campaigns](/campaigns/campaigns/campaigns-and-referral-campaigns.md)
* [Purchase transaction triggers](/campaigns/campaigns/campaigns-and-referral-campaigns/creating-campaigns/trigger-types/purchase-transaction.md)
* [Rewards](/rewards-redemption/rewards/reward-list/creating-reward.md)
* [Tiers configuration](/gamification/tiers/tiers-configuration.md)
  {% endhint %}

### 🛠️ Step by step

{% stepper %}
{% step %}

### Step 1: Campaign trigger

* **Path:** Campaigns > Add campaign
* **Campaign type:** Direct campaign
* **Campaign trigger:** Purchase transaction

Learn more about creating campaigns:

{% content-ref url="/pages/HQuxPjB52QWPOej7zG7G" %}
[Broken mention](broken://pages/HQuxPjB52QWPOej7zG7G)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Step 2: Campaign info

* **Name:** Shopping Spree
* **Start date:** May 1, 12:00 am
* **End date:** May 31, 11:59 pm
* **Status:** Active
  {% endstep %}

{% step %}

### Step 3: Rules and effects

* **Condition:** Transaction gross value is greater than or equal to `100`.
* **Effect 1:** Give reward – select the discount coupon.
* **Effect 2:** Add units to the tier wallet – set units needed for the target tier.

{% hint style="info" %}
**In plain English**

A member who completes any purchase of €100 or more in May receives both a discount coupon and units allocated to the tier wallet.

{% endhint %}

Learn more about setting up tiers:

{% content-ref url="/pages/-MZBspk\_YeJoAJMpx6a5" %}
[Broken mention](broken://pages/-MZBspk_YeJoAJMpx6a5)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Step 4: Limitation and budget

* **Campaign limit:** `In total`, `1` per member.
* **Budget:** Set a coupon budget and a tier-unit budget, if required.

{% hint style="info" %}
**Control-cost tip**

Using a per-member limit controls campaign cost and prevents duplicate rewards.
{% endhint %}
{% endstep %}

{% step %}

### Step 5: Review and save

Review the May dates, spending condition, rewards, and tier configuration. Then save and activate the campaign.
{% endstep %}
{% endstepper %}

### Troubleshooting

#### The campaign did not apply to a purchase

Confirm that the purchase occurred during May and has a gross value of at least €100. Check that the campaign is active.

#### The member did not receive the discount coupon

Confirm that the selected reward is active and available. Check that its inventory or coupon pool has remaining stock.

#### The member did not reach the higher tier

Confirm that the campaign adds units to the configured tier wallet. 

Check that the member reached the target tier threshold and that tier recalculation is enabled.


---

# 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/11-shopping-spree.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.