Funded, never traded: the shape of the activation window
The interval between a cleared deposit and a first order is the most predictive series a retail broker owns, and the one most likely to be reported as a single monthly percentage.
A client who deposits and does not trade has already told you something specific. Most brokers compress that signal into a single monthly activation percentage, which discards both the timing and the reason, the only two things that would let you act on it.
Activation is a decay curve
Time from cleared deposit to first order is not normally distributed and has no meaningful average. It is heavily front-loaded with a long, thin tail: a large share of clients who will ever trade do so within hours, and the probability of a first order falls steeply after the first few days.
The practical consequence is that a weekly activation report is looking at a decision window that closed before it was generated. By the time a client appears on a fortnightly “inactive funded” list, they are in the 3% tail.
Reporting activation monthly is measuring a 72-hour phenomenon with a 30-day instrument.
The reasons are separable, and they are not the same problem
“Funded but never traded” is treated as one cohort. It is at least four, and the correct response differs completely between them.
| Cohort | Signature in the data | Correct response |
|---|---|---|
| Blocked | Open KYC item, or deposit credited to wallet not trading account | Operational fix, not outreach |
| Confused | Logged in two or more times, no order ticket opened | Guided first trade, in their language |
| Waiting | Logged in, watchlist built, no order | Market or instrument prompt, timed to their session |
| Never intended | No login after deposit, bonus-driven acquisition | Stop spending on the channel that produced them |
The first cohort is not a marketing problem
A meaningful share of apparently inert funded clients are blocked by something mechanical: a document that expired between application and deposit, or a deposit that settled at the payment provider and never reached the trading account because an API call failed. These clients are trying to trade. Emailing them an encouragement is worse than doing nothing.
h(t) = P(first order in [t, t+Δ] | no order before t)Where cohorts beat per-client rules
Individually, each client is a very small sample: one deposit, a handful of logins. The useful structure appears at cohort level, clients from the same acquisition channel, country, deposit size band and platform tend to share an activation shape. That is what makes the timing decision tractable.
- 01Deposit clearsTrigger, not a schedule
- 02Check mechanical blockers firstKYC, credit path, platform account
- 03Place the client in a cohortChannel, country, size band, platform
- 04Use the cohort hazard to time contactNot a fixed day-3 rule
- 05Contact in their language and sessionDrafted, then approved
| Client A | Client B | |
|---|---|---|
| Deposit | €2,000 cleared 09:14 | €2,000 cleared 09:20 |
| Logins since | 4 | 0 |
| Open compliance item | Proof of address expired | None |
| Cohort activation median | 5 hours | 5 hours |
| Correct action | Chase the document | Guided first trade at their session open |
Illustrative figures, chosen to show the mechanism. Your own numbers will differ.
What this requires you to hold
- Deposit events joined to the trading account they credited, not just to the client.
- Login and session telemetry, at least at the level of “did they open a ticket”.
- Open compliance items, live, at the moment the decision is taken rather than at month end.
- Acquisition channel retained permanently, because it remains predictive long after the client stops being new.
- Client language and timezone, which decide whether a well-judged message arrives at 3am.
Each of those lives in a different system at most brokers. The reason activation work is usually shallow is not that the analysis is hard, it is that nobody can assemble the five inputs quickly enough for the answer to still be actionable when it arrives.