Skip to content

Building a campaign ​

The settings that decide behaviour, in the order they matter.

Making it findable ​

Four settings quietly decide whether a campaign can be granted at all. A campaign can look completely correct and still never fire because one of them is wrong.

SettingWhat to watch
StatusOnly an active campaign is granted.
Start and end dateThe end date is the most common silent failure — status stays "active" long after the date passes, and the campaign keeps looking healthy in the list.
CurrencyMust match the currency the player actually plays in.
Published to the siteA campaign that has not synced to the content system is skipped entirely. See When a bonus does not arrive.

Who qualifies ​

Uses per player limits how many times one person can receive it. Set it to 1 for anything meaning "first deposit only".

Targeting restricts a campaign to named players or to people who signed up with a particular referral code. Targeting also raises priority: when several campaigns match the same deposit, a targeted one wins over an open one.

When it triggers ​

For a deposit campaign:

Deposit range — the minimum and maximum deposit that qualify. Leave the maximum empty for no upper limit. A deposit exactly equal to the maximum still qualifies.

Payment method — restricts the campaign to fiat or crypto deposits. Leave it open to accept both.

Crypto-only campaigns cannot be tested from the admin panel

A deposit booked by an operator always counts as fiat. A campaign limited to crypto will never match one, however correct the rest of it is. Test crypto campaigns with a real crypto deposit on the player site.

How the player gets it ​

Two ways, and the choice decides whether the campaign ever fires on its own.

Automatically — the player qualifies and receives it. This is what a deposit campaign normally wants: the deposit lands, the campaign matches, the bonus appears.

The player joins it — the campaign is offered, and nothing happens until the player accepts it themselves.

A joinable campaign is skipped by every automatic grant

The engine looks only at campaigns the player does not have to join. Set a deposit campaign to joinable and it will never fire on a deposit, however correct the rest of it is - and nothing reports this, because from the engine's point of view there was simply no campaign to match.

Use joinable only for offers a player picks up deliberately.

How much ​

Either a fixed amount or a percentage of the deposit.

A percentage campaign can also carry a maximum bonus amount. It does two jobs at once: it caps any single award, and it caps the player's lifetime total from that campaign. A 100% offer capped at 8,000 grants 8,000 on a 10,000 deposit, and if the campaign allows repeat use, 8,000 is also the most that player will ever receive from it.

Leaving the cap empty removes both ceilings

The field is optional. Left empty, the campaign pays the full percentage of whatever was deposited — a 100% offer on a 50,000 deposit grants 50,000 — and the player's lifetime total from the campaign is uncapped as well, because it is the same field doing both jobs.

Nothing warns you at the point of saving. Leave it empty only when you mean to.

This caps what the player is given. What they may keep is a separate ceiling, set further down the form - see Wagering and conversion.

What the player must do ​

Two separate requirements, covered fully in Wagering and conversion:

To receive it — an optional requirement to wager the deposit before the bonus becomes usable. Set to zero, the bonus is active immediately. Above zero, it waits.

To keep it — how much must be wagered before bonus winnings become real money, and what that multiplier applies to.

Presentation ​

Name, description, terms and image are what the player sees. The image is uploaded to the content system; keep it under 10 MB.

Internal documentation. Every page states what has been verified and what has not.