> 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/reports/challenge-overview.md).

# Challenge Overview

The Challenge Overview Report provides businesses with insights into the performance of their challenges by tracking key engagement metrics. This report helps businesses analyze participation, completion rates, and opt-outs to refine their challenge strategies and optimize member engagement.

#### Report Columns

The Challenge Overview Report includes the following data columns:

* **Challenge:** The name of the challenge being reported.
* **Invited:** The total number of people invited to the challenge via email.
* **Joined:** The number of people who joined the challenge.
* **Completed:** The number of participants who successfully completed the challenge. This will include customer that did not join the challenge. Customers that did not join the challenge did not get the reward.
* **Joined and Completed:** The number of participants who both joined and completed the challenge.
* **Opted Out:** The number of participants who opted out of the challenge after joining.

#### Report Filters

* **Challenge Selection:** The report includes a filter to select specific challenges by name, allowing businesses to generate insights for one or multiple challenges.


---

# 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/reports/challenge-overview.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.
