Submitted answers
Sometimes it's important to involve as many performers as possible. You can limit the number of tasks in the pool per performer or set a limit on daily earnings in your customizable project.
When to use
Get responses from as many performers as possible (for this purpose, set a low threshold, such as one task suite).
Protect yourself from robots (for this purpose, the threshold should be higher, such as 10% of the pool's tasks).
- Usage recommendations
-
Don't set large values in pools where performers won't have time to complete the required number of tasks.
Rule settings
Field | Overview |
---|---|
If | A condition for performing the action in the then field:
|
then | Action to perform for the condition:
|
Field | Overview |
---|---|
If | A condition for performing the action in the then field:
|
then | Action to perform for the condition:
|
Rule example
Task: you're conducting an opinion poll. To collect responses from as many performers as possible, set up the Submitted responses rule.
- Correct settings
-
If the performer submits more than 20 assignments, they can no longer access the pool and can't complete your tasks.
Troubleshooting
Calculate the skill for each pool separately. The current skill value is the value of the skill in the pool the user completed last. This option is convenient if:
The pools are intended for different groups of performers (for example, there are filters by city or country).
Pools are started one by one and you don't want to take into account the responses in the previous pools to calculate the skill in the current pool.
This calculation method is used by default when adding a quality control rule to a pool. For the control tasks block, leave the Recent control task responses to use field empty.
Calculate skill based on all tasks in a project This option is good if the pools are small and you don't need to have skill calculated for each pool.
This option is available only for skills on control tasks. To use it, fill in the Recent control task responses to use field in pool quality control rules.
It is better to use one skill in a project. You can choose the way to calculate the skill:
Yes, of course — you can use the same skill for different projects. But most often, a skill is intended for a specific project. If the performer completes a certain task well, this doesn't mean that they will complete other ones successfully. Another disadvantage is that if you filter by skills that were set long ago, you will artificially limit the number of available performers.
Yes, if they can access both pools, they can do both of them. To restrict access to subsequent tasks for a performer, use the Completed tasks rule and select a ban at the project level.
If you pass texts to the input data, you can load 2 different tasks in the pool. In one task, pass Text 1 in the INPUT: <input field name>
field, and in the other task, use this field to pass Text 2. But if the text is in the HTML block of the task template, you need to clone the project. To let a performer do only one task in your project, use the Submitted responses rule. You can assign a skill or ban the performer after they submit one response.