> 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/exclude-recent-participants-from-studies.md).
# Exclude recent participants from studies
Study type
Availability
Screeners
true
Usability tests (auto-recruit)
true
Media surveys (auto-recruit)
true
Intercept studies
true
AI moderated studies (auto-recruit)
true
Recruiting from the Dscout Scout Panel is a fast and easy way to find participants for your research. However, if you’re running similar studies close together, you may want to ensure you hear from new voices—not the same Scouts who’ve already shared their insights.
With **activity filters** in screeners, usability tests, and media surveys, you can prevent Scouts from participating in your studies if they’ve already done so in the last 90 days. This ensures you’re recruiting a fresh group of Scouts every time.
{% hint style="info" %}
**Note:** Activity filters are only available when auto-recruiting from Dscout’s pool of participants (known as Scouts). When using any other recruitment method, invite only participants you want to participate in your studies.
{% endhint %}
## Activity filter options
Activity filters are enabled on screeners and studies individually, but you can choose to apply them in one of two ways:
* **Within this project:** Applies your selected filters only to Scouts who have taken part in a screener or study in this same Dscout project.
* **Within this account:** Applies your selected filters to Scouts who have taken part in any screener or study across your Dscout account, regardless of project.
From there, you can choose to exclude participants who fall into the following categories:
* **Study participants from the last 90 days:** Scouts who have participated in a study in the last 90 days.
* **Qualified screener applicants from the last 90 days:** Scouts who have applied to and qualified for a screener in the last 90 days, regardless of study completion. Keep in mind that Scouts who have applied to screeners in the last 90 days but have not qualified will not be excluded by this filter.
* **Both:** Excludes all Scouts who fall into either of the above categories.
The following options are selected by default:
| Screener default activity filters | Study default activity filters |
| --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
Within this project.
Qualified screener applicants from the last 90 days.
|
Within this project.
Study participants from the last 90 days.
|
## Access activity filters
{% stepper %}
{% step %}
Navigate to the **Screener** tab of your screener or study.
{% endstep %}
{% step %}
Click **Targeting attributes** in the left sidebar. The Targeting attributes side panel is displayed.
{% endstep %}
{% step %}
Click **Settings** in the Targeting attributes side panel.
{% endstep %}
{% step %}
Here, customize the activity filters to fit your research needs.
{% endstep %}
{% endstepper %}
Now, when you launch your screener or study, only the Scouts in Dscout’s pool who meet your criteria will be able to apply to your study.
---
# 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/exclude-recent-participants-from-studies.md?ask=&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.