> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/settings/challenges/challenge-progress-activities.md).

# Challenge Progress Activities

Challenge Progress Activities define the specific actions or achievements required for customers to complete a challenge. Each activity outlines what the customer needs to do and how it contributes to challenge completion.

{% hint style="info" %}
**No manual Join required with automatic enrollment**

Enable **Automatically enroll eligible customers** in the challenge settings before launching. An eligible customer's first qualifying activity enrolls them and counts toward progress. They can earn configured milestone rewards as they reach each goal without selecting **Join**. [See automatic enrollment setup](/features/challenges/automatic-enrollment-into-challenges.md).
{% endhint %}

#### Adding Challenge Progress Activities

When adding or editing a Challenge Progress Activity, configure the following fields:

* **Earning Rule or Progress Activity**: Select the type of [earning rule](/features/earning-rules.md) or [progress activity](/features/earning-rules/activities.md) (e.g., check-in, class attended, appointment attended, amount spent). This specifies what action the customer needs to complete.
* **Number of Times Required**: Define how many times the customer must complete the selected earning rule or progress activity to meet this requirement.
* **Display Name**: Provide a descriptive name for the activity (e.g., "Attend 5 classes"). This name will be shown to the customers.
* **Optional Description**: Add a description for additional details about the activity (optional). This helps customers understand what they need to do.
* **Optional Detail URL**: Provide a URL that offers more information about this activity or goal. When used, the title of this activity will link to the specified URL.
* **Display Priority**: Set the order in which this progress activity will be shown to customers. Lower numbers will display higher on the list (e.g., a value of 1 will appear first).

#### Optional reward when a requirement is completed

Use **Award a reward when this goal is reached** to add a milestone reward to this requirement:

1. Set the switch to **Yes**.
2. Under **Reward**, enter the number of points, select one or more instant rewards, or choose both. Use **Create instant reward** if you need to create a new reward.
3. Save the activity.

Leave the switch at **No** to track progress without a milestone reward.

For example, an **Attend 5 classes** requirement can award 25 points and a free smoothie when the customer reaches five classes. This reward is awarded once for completing the requirement, rather than once for each class. Any points from the underlying earning rule are separate.

#### Enrollment and milestone rewards

**Enrollment does not have to be a step the customer takes.** A customer must be enrolled and complete the requirement, but enrollment can happen in either of these ways:

* **Automatic enrollment enabled:** The first qualifying activity recorded in Perkville enrolls an eligible customer and counts toward progress. Milestone rewards are awarded as their requirements are met, with no need to select **Join**.
* **Automatic enrollment disabled:** The customer must select **Join**. Qualifying progress may be recorded before they join, but it does not award a milestone reward by itself. If a requirement is already complete when an eligible customer joins an active challenge, its configured milestone reward can be awarded then.

Both options follow the challenge's dates and participation restrictions. See [Automatic enrollment into challenges](/features/challenges/automatic-enrollment-into-challenges.md) for setup.

Set milestone rewards before launching whenever possible. Adding or changing a reward after an enrolled customer has already completed the requirement does not trigger a retroactive payout. Changing a reward that has already been issued does not issue it again.

#### Example: rewards at the 1st, 3rd, and 6th check-ins

To award these milestones without a separate customer sign-up step:

1. Enable **Automatically enroll eligible customers** in the challenge settings.
2. Add three Challenge Progress Activities using the same qualifying check-in activity. Set **Number of Times Required** to **1**, **3**, and **6**, respectively.
3. For each requirement, set **Award a reward when this goal is reached** to **Yes** and choose its points, instant rewards, or both.
4. Configure the challenge's dates, eligibility restrictions, and final completion reward, then launch it.

An eligible customer's first qualifying check-in enrolls them, counts toward progress, and earns the configured 1-check-in milestone reward. The 3-check-in and 6-check-in milestone rewards are earned when their total qualifying check-ins reach those goals. No **Join** action is required. Each milestone reward is awarded once for that requirement; the final completion reward is separate.

#### What customers see

The challenge page shows each requirement's progress and any points or instant rewards available for completing it. A requirement's progress checkmark means the goal has been reached; it should not be read as a reward receipt. For a completed requirement while the customer is not yet enrolled, the reward shows **Join to earn** without a reward checkmark. With automatic enrollment enabled, an eligible customer's first qualifying activity handles enrollment for them.

#### Completing the Challenge

Businesses can add multiple Challenge Progress Activities to a single challenge. Customers must complete all listed activities to successfully complete the challenge.\
\
If the earning of an earning rule or progress activity is automated in your loyalty program, usually through an integration with your point of sales or membership system, then it will also be automated for the challenge.

By setting up clear and achievable progress activities, businesses can effectively drive customer engagement and ensure a rewarding challenge experience.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/features/settings/challenges/challenge-progress-activities.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 `automate deployments from our CI pipeline` 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.