> 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/3-ambitious-player-configuration-log-in-to-the-game-3-times-per-week-for-8-consecutive-weeks.md).

# #3 Consistent Player - Log in to the game three times per week for eight consecutive weeks

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

### Business case

Reward members for logging in constantly and consistently. This setup works well for apps, games, and portals that depend on repeat usage.

Use a completion effect to grant points, a badge, or another loyalty reward.

**💡 Useful for** creating habits by rewarding consistent engagement.
{% endhint %}

{% hint style="warning" %}
This setup uses custom events to track logins.

Learn more: [Broken mention](broken://pages/-MhwU9vuj9jlFAx19huA)
{% endhint %}

### 🛠️ Step by step

{% stepper %}
{% step %}

### Step 1: Challenge info

* **Name:** Log in to the game three times per week for eight consecutive weeks
* **Availability:** Always available
* **Status:** Active
  {% endstep %}

{% step %}

### Step 2: Milestone

* **Milestone type:** Direct milestone
* **Trigger:** Custom event
* **Event type:** `LogInCheck`
* **Progress tracking:** Number of event occurrences
* **Goals:**
  * Occurrence: Streak
  * Streak type: Weekly streak
  * Goal per week: 3
  * Streak period: 8 weeks in a row

**Rules & Effects**

* **Trigger type:** Challenge completion
* **Effect:** Add units to wallet, grant a badge, or trigger 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/3-ambitious-player-configuration-log-in-to-the-game-3-times-per-week-for-8-consecutive-weeks.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.