> 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/guides/courses/from-usertesting-to-dscout/incentives-in-dscout-vs-usertesting.md).

# Incentives in Dscout vs UserTesting

Incentives play a critical role in motivating participants and ensuring you receive high-quality data. Unlike UserTesting, where incentives are standardized and preset, Dscout empowers you to choose incentive amounts you feel are fair for the effort you’re asking participants to put forth. This lesson explains how incentives are determined in Dscout as well as how participants are actually paid for completing a study.

## How are incentives set in Dscout?

In Dscout, incentives are set at the **study level**, giving you full control over how much participants are paid. For example, a usability test with thirty questions will typically warrant a higher reward than a media survey with fifteen questions. However, depending on the questions you’re asking, that may not always be the case. So, Dscout leaves it up to you to find an incentive you feel appropriate.

{% hint style="info" %}
**Tip:** While we leave determining incentives up to you, of course we have some recommendations. Reach out to your Research Advisor for guidance. Or for some standard recommendations, see [Recommended mission incentives](https://help.dscout.com/hc/en-us/articles/40200657423252-Recommended-mission-incentives).
{% endhint %}

## When are incentives paid in Dscout?

You’ll set a study’s incentive before you open the study to participants, and participants will see that incentive before they begin. However, when payments are processed depends on the study type. Here’s a breakdown:

| Study type         | Payments processed                                                                      |
| ------------------ | --------------------------------------------------------------------------------------- |
| **Media survey**   | Automatically after a seven-day hold in which you can review each response for quality. |
| **Usability test** | Automatically after a seven-day hold in which you can review each response for quality. |
| **Diary study**    | Upon request of the researcher. The Dscout team will take it from there.                |
| **Interview**      | Upon request of the researcher. The Dscout team will take it from there.                |

Now that we’ve covered how incentives differ between UserTesting and Dscout, you’re ready to move on. Next, we’ll recap what you’ve learned in this course and offer some next steps to kickstart your research in Dscout.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.dscout.com/guides/courses/from-usertesting-to-dscout/incentives-in-dscout-vs-usertesting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.