Captchas and the Fast responses rule provide a high level of protection from robots.

To show a captcha to performers, set captcha frequency in the pool settings.

In Toloka, a captcha is normally shown once every 10 task suites. This is usually enough. If responses are given quickly and captchas get in the way, they can be shown every 20 task suites.

When to use

Restrict access to tasks for performers who fail to enter captcha several times in a row. This setting is necessary if you want to provide additional protection from robots.

Don't use it if:
  • There aren't very many tasks in the pools. For example, if the task is a survey on a single page, a captcha won't help you control the quality, since the minimum frequency of captcha display is every 10 task suites.
  • It's difficult or impossible to automate user actions: selecting areas, performing field tasks or any tasks where performers need to attach files or write meaningful texts.

Rule settings


The If and then fields in this rule are mandatory. If you don't fill in at least one field, you won't be able to save the rule.



Recent values to use

The number of times the performer was shown a captcha recently.

To calculate all captcha displays in all pool tasks, fill in the field in the rule for each project pool.

If this field is not filled in, only the captcha displays when completing tasks in the pool that uses this rule are counted in the calculation.


A condition for performing the action in the then field:
  • number of responses — The number of entered captchas (less than or equal to the number in the Recent values to use field).

  • correct responses (%) — The percentage of correct responses (from 0 to 100).

  • % incorrect answers — The percentage of incorrect responses (from 0 to 100).

To add multiple conditions, click .


Action to perform for the condition:

  • assign skill from the field — Save the percentage of the performer's correctly entered captchas in tasks as a skill value.

  • ban — Block access to the project or all of the requester's projects for the specified number of days. Only the requester can view the reason.

    If access to tasks is blocked temporarily (for example, for 7 days), the history of the performer's responses is not saved after the ban is lifted. The skill value is based on new responses.

  • suspend — Suspend the performer's access to the pool for the specified number of days. Only the requester can view the reason.

  • accept user's answers — Requires the non-automatic acceptance option to be set.

    Useful if the performer completes most tasks well. Example: The Toloker completed more than 80% of the tasks correctly and you are satisfied with this result. The rule will work automatically and accept all responses in the pool.

  • assign skill value — Assign a fixed value to the skill.

Rule example

Since a person can also make a mistake when entering a captcha, it's advisable to add the number of responses field and set a value greater than 1. Otherwise, the performer will be banned after the first captcha entry.

Blocking for incorrect captcha entries

If the performer entered a captcha at least 5 times and the percentage of correct answers is less than 65%, they are banned and can't complete your tasks for 10 days.


Should I create a skill for every pool?

It is better to use one skill in a project. You can choose the way to calculate the skill:

  • 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 values 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 values to use field in quality control rules in pools.

Can I use a skill beyond a particular pool or project and apply it to other projects as well?

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.

I set up a rule to ban users after the first incorrect captcha. This is to eliminate any bots. Is this too strict? What rule do most projects use?

Indeed, this rule is probably too strict. Even the most careful user can make a mistake, so you probably want to relax the rule. Besides the requester-specific bans, we have system processes that ban users who regularly fail captcha checks in Toloka.

Can I control the frequency of showing captchas to the performers? Some performers get a bit demotivated by that.
The frequency of issuing captchas is set up in the pool.
Don't show captchas.
Show a captcha after every 20 task suites.
Show a captcha after every 10 task suites.
Can I get more details on the best practices for using captchas? For which projects is it better to use captchas and how often?

Captcha is usually used in simple projects with automatic acceptance, like classification, categorization, or information search. These are cases where there are few response options and users don't need to upload files or write texts. It helps you filter out bots and sloppy performers.

The frequency of issuing captchas is configured in the pool.
Don't show captchas.
Show a captcha after every 20 task suites.
Show a captcha after every 10 task suites.
I found the following terms related to captcha in Help: “Percentage of correct responses” and “Percentage of incorrect responses”. Are they determined from the control sample?

The percentage of correct responses is based on the total number of captchas processed by the performer within the “range” specified in the Recent values to use field. If the value is empty, the percentage is calculated using all the captchas that are shown for the tasks in the pool which uses the captcha rule.