> 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.md).

# Sample Challenges

In this section, you will learn practical applications of Challenges and how to use them to address your business's needs.

### Business case

Challenges allow you to gamify members' experiences, encouraging them to work toward a reward by completing specific actions – such as making purchases, logging custom events, or referring friends.

The following setups are blueprints for different industries and can be modified to address your business goals.

{% hint style="warning" %}
Some setups depend on features that typically require additional configuration.

Review these first if a scenario feels advanced:

* [Creating Challenges](/campaigns/challenges/creating-challenges.md) – the basis of every Challenge setup
* [Custom Events](/members-and-activity/custom-events.md) –  for logins, workouts, and other tracked actions
* [Transactions](/members-and-activity/transactions.md) – for spend-based and purchase-based challenges
* [Referral Programs](/faq/referral-programs.md) – for referee-based challenge setups
  {% endhint %}

Below are practical uses that apply to different industries.

<table><thead><tr><th width="52">#</th><th width="185">Name</th><th>🧩 Setup</th><th>💡 Business case</th></tr></thead><tbody><tr><td>1</td><td><a href="/sample-setups/sample-achievements/1-celebrate-summer-configuration-buy-5-times-between-june-and-august.md">Celebrate Summer</a></td><td>Buy 5 times between June and August</td><td>Boost seasonal frequency</td></tr><tr><td>2</td><td><a href="/sample-setups/sample-achievements/2-place-10-orders-above-50eur-configuration-complete-10-transactions-for-more-than-50eur-each.md">Frequent Buyer</a></td><td>Complete 10 transactions above €50</td><td>Boost average basket</td></tr><tr><td>3</td><td><a href="/sample-setups/sample-achievements/3-ambitious-player-configuration-log-in-to-the-game-3-times-per-week-for-8-consecutive-weeks.md">Consistent Player</a></td><td>Log in 3 times per week for 8 weeks</td><td>Build login habits</td></tr><tr><td>4</td><td><a href="/sample-setups/sample-achievements/4-sku-abc-configuration-spend-total-of-100usd-on-products-with-sku-abc132-in-september.md">SKU Sell-off</a></td><td>Spend $100 on one SKU in September</td><td>Inventory clearance, product launches</td></tr><tr><td>5</td><td><a href="/sample-setups/sample-achievements/5-workout-configuration-track-a-workout-of-at-least-30-minutes-for-5-days-in-a-row-get-250-points.md">Workout Streak</a></td><td>Work out 30 minutes for 5 days in a row</td><td>Build daily habits</td></tr><tr><td>6</td><td><a href="/sample-setups/sample-achievements/6-4-referees-made-the-transactions-for-2-consecutive-days-configuration.md">Shopping Buddies</a></td><td>Get 4 referees to transact for 2 weeks</td><td>Boost referral quality and ACV</td></tr><tr><td>7</td><td><a href="/sample-setups/sample-achievements/7-2-referees-made-a-transaction-configuration.md">Referral Boost</a></td><td>Get 2 referees to make a purchase</td><td>Accelerate first referrals</td></tr></tbody></table>


---

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