A task wall in an iframe on your site. A user does a task and gets your currency — coins, points, whatever you run on. We find the advertisers, check every completion and pay you for the confirmed ones.
Connecting is free. You do not buy traffic and you do not pay for the wall — you take a share of every completion.
After that there is nothing for you to do. The tasks come from advertisers, we review the reports, and what reaches you is a postback for something already accepted.
Domains, topic, traffic geo. Each domain is moderated on its own and the wall opens only on the approved ones — a subdomain added later does not widen access quietly.
Your unit's name, how much of it is in a dollar, the user's share. Under the rate field, a live calculation over the catalogue: what a user earns for each task, and what does not express in your currency at all.
| Task | To the user |
|---|---|
| Telegram channel subscription | 62 coins |
| Install an app, reach level 3 | 936 coins |
| Reels views | not shown |
One script on the page, and the wall sets its own height and theme. The postback URL and the placement secret are set in the same place, in the wall's settings.
<script src="https://wall.tasqo.pro/loader.js" data-placement="GB7K2M" data-user="USER_ID" data-ts="UNIX_TIME" data-sig="HMAC_SHA256(USER_ID:UNIX_TIME)" async></script>data-user is your own user id. The postback brings it back to you with the reward. data-ts is the unix time in seconds the page was rendered at; a link dies an hour later. data-sig is the HMAC of "USER_ID:UNIX_TIME" with the placement secret, computed on your server: nobody opens the wall as somebody else.
You check nothing.
The screenshot, the conversation with the worker, the round of revision, the argument and the second look are ours. What reaches you is a postback for a completion that has already been accepted.
| Whose job | Your own tasks | With Tasqo |
|---|---|---|
| Finding an advertiser | You, in DMs and on forums | Us: a catalogue, and panels over the API |
| Looking at screenshots | You, by hand, in the evening | AI; the disputed ones go to our moderator |
| Arguing with the worker | You, in the same chat | Us: a thread, a revision round, deadlines |
| Paying for fakes | You, and you notice a week later | Nobody: what is not accepted is not paid for |
| Unsubscribed the next day | The credit cannot be taken back | A reversal, and a second postback |
| Crediting the user | You | You — on the postback, with your own logic |
Sent on every approval and every reversal. Undelivered ones are retried on a schedule; the delivery log and a test-postback button are in the cabinet.
GET https://yoursite.com/tasqo/postback?user_id=u_9042117&amount=62&payout=0.007800&status=approved&transaction_id=t-a41c9e&country=RU&reversible_until=2026-09-29T12:00:00Z&sig=3f9a1c7e2b64d0f5
Answer 2xx with `1`, `OK` or an empty body, or we will retry.
The advertiser pays for a completion, we keep our part, the rest is yours. The share is in your cabinet before the first task, not after the first month.
Credited when a report is accepted. Not for a click on a task, not for opening the wall, not for an impression.
New revenue sits in pending while the re-check window is open — a week on subscriptions, typically. When it closes, the amount moves to available.
A user unsubscribes, or a completion turns out to be fake — the conversion is withdrawn and a second postback reaches you with status reversed. That is said before you integrate, not in small print afterwards.
Theme, accent colour, logo, language, grid or list, the currency icon — all per placement. A user sees only what their country and device can actually do: no "not available in your region" cards in the feed.
Register, send the site to moderation, paste the loader. Questions go to Telegram support.