.svg){kind=icon}
A trading account is worth nothing on the day it opens. Someone clicks a partner's link, fills in a form, and at that moment the only thing you know is that a form was filled in. The money, the KYC? check, the first real trade — all of it happens later, and most of it never happens at all.
So the deal you want is not "pay for signups". It is "pay when this person becomes a customer we can actually make money from". That is what a qualified deposit? is, and this article builds the rule that pays on one. The same shape works for a prop firm? evaluation, a crypto exchange or a CFD broker — only the number changes.
What "qualified" actually means
Every broker, exchange and prop firm has its own definition, but they are all made of the same three parts. Write yours down before you touch Everflow, because the rule is a direct translation of it.
Money moved
A deposit landed, and it was big enough to be worth a payout. Not a demo account, not a pending transfer.
In a market you can pay on
The jurisdiction on the account is one your licence and your partner agreement actually cover.
A real, verified person
Identity checks passed. Until they do, the money can go back out as fast as it came in.
The important word is and. Conditions in a Customer Value rule are joined with AND, always — there is no OR. That is a constraint when you want alternatives, and exactly what you want here: money on its own is not a qualified deposit, and neither is a verified account that never funded.
The numbers you need
Three things have to reach Everflow on the conversion, and one you get for free.
| You call it | In Everflow it is | Worth knowing |
|---|---|---|
| First deposit (FTD) | A Number data point on the conversion | Send the amount in one currency and convert before you send. The rule compares numbers, not currencies. |
| Jurisdiction | A Text data point, matched exactly | Not the same as Everflow's IP geo. Send the one compliance would recognise. |
| KYC status | A Text data point, matched exactly | Send the settled state, not the pending one. A rule that fires on "submitted" pays for accounts that later fail. |
| Trades placed | Either a Number data point, or a Metric if each trade is a conversion | If Everflow already counts it, do not send it. Fewer moving parts. |
| Lifetime deposits | A running total on a Continuous cycle | Continuous never resets, so the total is genuinely lifetime. |
| Tier / band | One rule per band, with a floor and a ceiling | There is no "between" operator. Four tiers is four rules. |
| CPA per qualified deposit | Outcome type Bonus, payout model Applicable Payout | Added on top of the normal payout, at most once per cycle. |
| A share of the deposit | Outcome type Bonus or Substitution, payout model Custom Data Point | A percentage of a number you sent. Bonus adds; Substitution replaces. |
| Deposit reversal / chargeback | A negative value you send against the same customer | Nothing subtracts on its own. If you do not send it, the total never comes down. |
| Trader or account | A user ID | One key, every event, for the account's whole life. The most common integration miss. |
The one you do not have to send
Before you build anything, look at what Everflow already keeps. A metric? is a number the platform counts by itself — how many conversions this customer has generated, how much payout they have earned. If each trade fires a conversion, "has this person traded five times" is already answered, and you do not need a data point for it.
Text is for matching, Number is for comparing
Country and KYC? status are each a custom data point? of type Text. Text values are matched exactly — is it DE — and never compared, which is why a deposit amount cannot be Text. The type locks when you save, so this is one of the few decisions you cannot walk back.
Step 1: Whose total is it?
Before conditions, scope. Shared? pools every conversion into one total. Segmented? keeps a separate total per advertiser, offer, partner, or a combination of two.
For a deposit bonus you almost always want Segmented, and usually by partner. Shared means two partners who both touched the same trader watch the same total climb, and the one who happens to be attributed when it crosses the line takes the bonus.
Step 2: The three conditions
This is the rule itself, and it is three lines.
Read it back in English: all values of First Deposit Amount greater than 250, and Country exactly DE, and KYC Status exactly verified. Every one has to be true before anything pays. The number being compared is the first-time deposit? your own platform sent — Everflow stores it and adds it up, and never works it out for itself.
Step 3: Four tiers, four rules
Most broker deals are banded: the bigger the first deposit, the bigger the payout. Everflow has no between operator and a rule has one outcome, so each band is its own rule.
| Rule | Conditions, all joined with AND | Pays |
|---|---|---|
| Tier 1 | deposit > 250 deposit < 1000 country = DE kyc = verified | $75 |
| Tier 2 | deposit > 999 deposit < 5000 country = DE kyc = verified | $200 |
| Tier 3 | deposit > 4999 deposit < 25000 country = DE kyc = verified | $600 |
| Tier 4 | deposit > 24999 country = DE kyc = verified | $1,500 |
Every rule in that table carries the same two qualifiers — a supported country and a verified account — and then a floor, and a ceiling. The top band has no ceiling, which is why it is one condition shorter.
Every tier fires
A $30,000 deposit is greater than 250, greater than 999, greater than 4,999 and greater than 24,999. Four rules match, and four bonuses pay.
Exactly one tier fires
The same deposit clears the floor on tier 4 and fails the ceiling on the other three, so only one rule can match it.
Give each rule a name that says which band it is. You will be reading this list at 9pm six months from now when a partner asks why a $4,900 deposit paid $200 and not $600.
Step 4: What each tier pays
Set Outcome Type. There are two, and the difference is not how much they pay — it is whether they add to the partner's normal payout or replace it.
Bonus
Added on top of whatever the partner already earns on that conversion.
- At most once per cycle, per customer
- Flat, or a percentage of a data point
- Right for a one-off qualification payment
Substitution
Replaces the applicable payout and revenue instead of adding to it.
- No once-per-cycle limit
- Flat, or a percentage of a data point
- Right for an ongoing share of what the trader generates
Either outcome can be a flat amount or a percentage, and this is worth being precise about, because the form says something narrower than it means. Set the payout model to Applicable Payout and a bonus is CPA only — a flat figure you type. Set it to Custom Data Point and the same bonus becomes a percentage of a number you sent: 10% of First Deposit Amount. Revenue works identically, through Custom Revenue and Revenue Model.
The finished rule
Everflow restates the whole thing in plain English on the rule's own page.
This is the screen to send someone who asks what the deal is. It is not a description of the rule — it is the rule.
Check it worked
Two checks, in order, and the first one matters more than people expect.
Did the values arrive at all?
Before any rule can fire, the numbers have to reach Everflow. The Advertiser Postback report shows the inbound calls with the parameters still on the end of the URL.
If a parameter is missing here, it was never sent. No rule will ever see it, nothing will error, and the customer will simply never qualify.
What arrived on one conversion?
Open a single conversion and the Parameters table lists exactly what came with it, key by key.
This is the fastest way to settle an argument about whether a value was sent or dropped, and it is where to start when one trader qualified and an apparently identical one did not. It is also where a deposit reversal? shows up — or does not, if nobody wired it.
What you get
You stop paying for forms
A signup that never funds, never verifies or never trades costs the programme nothing.
The band is enforced, not trusted
Nobody reconciles tiers in a spreadsheet at month end. The rule decides at conversion time.
Partners can see what qualifies
A partner who learns which sources produce funded, verified traders sends more of them.
One definition, everywhere
"Qualified" stops meaning something slightly different in every partner conversation.
Common questions
QCan one rule cover all four tiers?
No. A rule has one outcome, and the operators are Equal To, Greater Than and Less Than — there is no "between" and no way to vary the amount by band inside a single rule. Four bands is four rules. The upside is that each one is readable on its own.
QWhat stops a big deposit from triggering every tier?
The ceiling. If your tiers only have floors, a $30,000 deposit satisfies all four and pays all four bonuses. Give every band except the top one a Less Than condition as well, and exactly one rule can match any given deposit.
QDo I have to send the number of trades?
Only if a trade is not already a conversion. If each trade fires a conversion event, Everflow counts them for you and the condition is a Metric — Total of Base Conversion Events. Sending a count you could have read is a second source of truth to keep in sync.
QCan a bonus be a percentage, or does that have to be a substitution?
A bonus can be a percentage. The limit people remember — "only the CPA payout model is supported for bonuses" — applies when the payout model is set to Applicable Payout. Switch the model to Custom Data Point and the same bonus pays a percentage of a value you sent. What separates a bonus from a substitution is that a bonus is added on top and capped at once per cycle, while a substitution replaces the payout and is not.
QWhat happens if a deposit is reversed?
Nothing, unless you tell Everflow. It adds up what arrives, so a reversal only reduces a customer's total if your platform sends a negative value against the same user ID. If reversals are common, send them — and read the article on NGR, which is about exactly the case where the total can go below zero.
QOur KYC can move from verified back to under review. Does the rule re-evaluate?
A rule looks at conversions as they arrive. A bonus that has already paid is not clawed back because a later value changed, and a customer whose status improves later will qualify on their next conversion. If a reversal has to move money, that is a payout adjustment, not a rule change.
QWill a new rule pay on deposits that already happened?
No. A rule starts looking at conversions the moment it is saved, so it cannot reach back over last quarter's deposits. If you want to see what a rule would have done before committing to it, create it Inactive — it collects without paying — and switch it on once the numbers look right.
QTwo partners touched the same trader. Who gets the bonus?
Whichever partner the qualifying conversion is attributed to, which is why the scope setting matters. Segmented by partner keeps a separate total per partner, so each one is measured on the traders they actually brought rather than on a pool they both contributed to.
QCan I use this for a prop firm challenge instead of a deposit?
Yes, and it is the same shape. The challenge fee is the Number data point, the pass/fail state is a Text data point, and "qualified" becomes "paid for a challenge and passed it". Nothing about the rule is specific to deposits — it is specific to a number, a state, and a threshold.
→ Introduction To Customer Value — what a rule decides, and the five shapes people build.
→ How To Send User IDs & Data Points For Customer Value — getting the deposit and KYC values flowing in the first place.
→ Build Your First Customer Value Rule — the simplest possible rule, if this is your first one.
→ Paying On Net Gaming Revenue (NGR) With Customer Value — a revenue share that has to survive a losing month.
