Sponsored tasks with a ceiling you authorise.
You define the task, the reward and the caps. The platform verifies each completion before a reward is credited.
The mechanics
Six properties, enforced by the schema rather than by trust.
A ceiling you authorise
A budget change adds a version; the previous one stays as the record of what was authorised.
Caps where they belong
Per-user, per-day and global completion caps, with a cooldown on each task.
Country and language targeting
Each task names the countries and languages it is offered in.
Verified before paid
Campaign tasks use server checks or manual review — never a self-declared claim.
Every movement recorded
Commit, release and adjustment are separate, each tied to the reward it paid.
One funding source, never both
A campaign is either platform-funded or sponsor-funded, and the database enforces it.
What a budget is, and is not
An authorised ceiling is permission to spend up to an amount. It is not proof that a sponsor has paid, and it is not an invoice. Settlement is a separate, contractual step.
Setup
How a campaign is set up
Four steps, from the sponsor record to activation.
Advertiser record
The sponsor is recorded once, with its own status.
Campaign and ceiling
A campaign starts as a draft; a budget version authorises the ceiling.
Tasks attached
Each task carries its reward, caps, targeting and verification mode.
Activate
Activation is the only operation that validates funding and budget.