Overview of Toloka

After registering in Toloka, you can create tasks for performers. When designing tasks, follow the requirements and recommendations. Define how tasks look, customize their distribution, and set up quality control for the responses. When the tasks are ready, they are sent to performers. Payment for completed tasks is deducted from your Toloka account. You can get performers' responses in a TSV results file.

Tasks in Toloka

A task is part of a web page that can include various objects, such as images, text, and input fields. The performer reads the instructions on the page, completes the task and enters responses. You can use Toloka for any tasks that meet the requirements.

When creating tasks, you need to make settings such as the fields included, the data types, the logic for validating responses, and so on. To launch tasks, you need to define:

Input data is uploaded to Toloka in a TSV file. The tasks that are formed from this TSV file are sent out for completion simultaneously. This group of tasks is called a pool. You can get performers' responses in a TSV results file.

Task page

An HTML page can display just one task, or multiple tasks. Putting multiple tasks on a page allows you to:

  • Reduce costs. The performer is paid for completing the entire task page (this means that the task price can be lower than the minimum rate of $0.01).

  • Speed up the results. The performer makes fewer transitions between pages.

Distributing tasks

You can restrict the list of performers to whom the tasks are distributed. To do this, configure the pool filters by region, skill, device used and other characteristics of the performers.

For more reliable results, tasks should be overlapped so that each task is completed by several performers.

Controlling the quality of responses

To increase the quality of responses:

  • Train the performers.

    Performers will train to complete your tasks. If the answer is incorrect, they will see a hint explaining which answer is correct and why.

  • Control the quality.

    You can set quality criteria so that tasks are assigned only to performers who meet these criteria.

    Examples: “If the percentage of correct responses in the pool is less than 60%, block project access”, or “If the performer skipped 5 tasks in a row, suspend access to the pool”.

  • Review assignments.

    You can manually check tasks and reject responses with poor quality. Rejected tasks are not paid for.