> For the complete documentation index, see [llms.txt](https://tgtaps.gitbook.io/tgtaps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tgtaps.gitbook.io/tgtaps-docs/blocks/tasks.md).

# Tasks

Tasks are needed for your app monetization. Via tasks, you can increase audience in your Telegram groups, channels, YouTube and other social networks. Moreover, you can sell places in the tasks lists to sell your audience to the other apps.

## Content

* How to work with tasks?
* Tasks with the word confirmation
* How tasks confirmation works?

## How to work with tasks?

To add tasks, select the block and add tasks:

<figure><img src="/files/7ScLZLP5vovUXhwSbFKy" alt=""><figcaption></figcaption></figure>

For the task, you can define the following fields:

* Image (popular social logo) or upload your own image (choose “custom image”).
* URL where the task will lead to (can be omitted if you require only word confirmation).
* Name which will be displayed in the application.
* Reward for the task in points.
* Task order in the list (the higher order number, the higher task in the list).

Also, you need to check the tasks you want to be visible in the current list:

<figure><img src="/files/ZRrygkSQ99u7v8zReMHY" alt=""><figcaption></figcaption></figure>

This is needed to create several lists on the page. For example, app tasks and partners' tasks.

## How tasks confirmation works?

When the user clicks the link and goes to Telegram channel or external website, the internal invisible timer starts to count and **“Check” button appear**.

If the user returned to the application and clicked “check” faster than within 10 seconds, the message “task is not completed” appears with the 30 seconds red timer:

<figure><img src="/files/lvswfPYRn4x1eR5yFALk" alt=""><figcaption></figcaption></figure>

**Why this is needed:** actually, TgTaps cannot check whether the user really subscribed to the channel or completed the task. So we assume that the user cannot complete the task faster than for 10 seconds. Therefore, we ask to verify that the task is completed: user will really subscribe or repeat the action.

Of course, there is a cheating is possible and \~5% of users will still not complete the task. This is the risk we have to accept.

## Tasks with the word confirmation

Also, you can select the word confirmation:

<figure><img src="/files/x7Jq5QAQsaqfyKPNGo6l" alt=""><figcaption></figcaption></figure>

In this case, the user will need to enter the keyword to receive points. You can have word confirmation without URL (for example, for daily code bonus).

This is needed to make users to read posts, watch videos, read articles, etc:

<figure><img src="/files/bHMJOmIgOGbmqp3KXc4S" alt=""><figcaption></figcaption></figure>

***

Something unclear in docs or you know how to improve article? [Message us in community!](https://docs.tgtaps.com/tgtaps-docs/readme/community)\
We will answer you and then promise to improve the article within 3 days.


---

# 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://tgtaps.gitbook.io/tgtaps-docs/blocks/tasks.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.
