> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/recruit-participants/dscout-scout-panel/participant-balance.md).

# Participant balance

To ensure your responses are balanced across major demographics (age, ethnicity, and gender), you can enable participant balance during recruitment.

{% hint style="info" %}
**Note:** This feature is only available when recruiting participants from Dscout's Scout Panel in the United States.
{% endhint %}

With this setting enabled, responses from any of the following segments will be capped at 65% of your total n-size:

| Segment category | Segment breakdown                                                                                                                                                                                                                                                                               |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Age**          | <ul><li>Under 13</li><li>13-17</li><li>18-24</li><li>25-34</li><li>35-44</li><li>45-54</li><li>55-64</li><li>65-74</li><li>75-99</li></ul>                                                                                                                                                      |
| **Ethnicity**    | <ul><li>American Indian or Alaska Native</li><li>Asian</li><li>Black or African American</li><li>Hispanic or Latinx</li><li>Middle Eastern or North African</li><li>Native Hawaiian or other Pacific Islander</li><li>White</li><li>Prefer to self-identify</li><li>Prefer not to say</li></ul> |
| **Gender**       | <ul><li>Woman</li><li>Man</li><li>Non-binary</li><li>Prefer to self-identify</li><li>Prefer not to say</li></ul>                                                                                                                                                                                |

## Enable participant balance

Participant balance can be enabled when recruiting US-based participants from the Dscout Scout Panel.

{% stepper %}
{% step %}
Navigate to the **Screener** or **Intercept** tab of your study.
{% endstep %}

{% step %}
Select **Standard targeting** in the left sidebar. The targeting attributes sidebar is displayed.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/0ey0EeD7HgfiCA1Jj1qh/47954790665236)
{% endstep %}

{% step %}
Click **Settings** in the right sidebar.
{% endstep %}

{% step %}
Set the **Balance participant demographics** toggle to **ON**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/bgb4xxcMYUTKuuA8bmko/47954784707988)
{% endstep %}

{% step %}
*(Optional, screeners only)* Click **Customize ethnicity balance** to enter custom percentages for each ethnicity segment. No ethnicity will be allowed to exceed its respective percentage of your total n-size when launched.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1gxKIeGfzlcE33AXyYNE/47954784709908)
{% endstep %}
{% endstepper %}

Now, participant balance is enabled for your screener or study. Once launched, no individual segment will be allowed to account for more than 65% (or your custom percentage if enabled on screeners) of your total number of desired responses.


---

# 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://help.dscout.com/recruit-participants/dscout-scout-panel/participant-balance.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.