Most retention tooling sold to brokers is a marketing product bolted onto the trading server. It
reads an exported client list, sends a campaign, and never learns what those clients did next. That
gap is why bonus programmes get abused and contest results get disputed.
The four components below run inside the MetaTrader 5 environment and read the same account and
deal data the dealing desk reads. Eligibility, scoring, prize crediting and bonus accounting come
from the server's own record of what happened. That is what makes an outcome defensible when a
client questions it.
ComponentPrice Alerts
Server-side price monitoring, independent of the client terminal. A client sets conditions — a
level crossing, a percentage move — and the server evaluates them against the live feed
continuously. When one triggers, the notification goes out by terminal push, Telegram or email.
The broker runs the service from the admin console, with live status of the engine itself.
What matters is where the evaluation happens. Alerts configured inside a terminal stop existing
the moment it is closed — precisely when a client is away from the screen and most likely to miss
a move. On the server the watch becomes a standing service: overnight, over the weekend, and on
the days the client never logs in.
What it solves
- Brings clients back at the moment they are ready to act, not hours later
- Removes the "I missed the move" complaint and the quiet churn behind it
- Runs unattended around the clock with no operational effort from the broker
ComponentPrediction Campaigns
A campaign engine for price-prediction contests. The broker opens a question on any instrument or
scheduled event — where gold closes on Friday, what level an index reaches after a rate decision.
Clients submit before the cut-off, a live leaderboard shows the field, and results settle
automatically against the reference price. Prizes are credited by the engine, not by hand. The
admin portal covers setup, prize rules, entry conditions and localisation.
Entering does not require placing a trade, so a campaign reaches an audience with no account yet
as well as the existing client base. Entry conditions, eligible jurisdictions and prize rules are
set per campaign and published with it.
What it solves
- A low-cost lead-generation format that is simple to explain and easy to share
- Reactivation of dormant clients around scheduled, high-attention market events
- Automatic settlement, so a campaign does not consume back-office time
ComponentTournaments
A trading-competition engine. Contests are scheduled in advance, run on live or demo accounts,
take free or paid entry, and rank participants in real time on a configurable metric — percentage
return, absolute profit, or traded volume. The prize pool is distributed automatically at the
close according to the published structure, and anti-abuse rules run for the duration.
The metric decides whether a tournament is worth running. Absolute profit rewards the largest
account; percentage return rewards the smallest, and invites entrants to open a minimum-size
account and swing it. Entry conditions and account constraints sit alongside it, and the engine
screens for the classic exploit — one participant holding opposite positions across two entries
so one is guaranteed to finish high. Scores come from server trading history, so a result can be
reconstructed if challenged.
What it solves
- A well-understood funnel: demo contests convert an audience into first deposits
- Concentrated activity on a schedule the broker chooses rather than hopes for
- A community identity attached to the broker's brand, not to the instrument
- An additional revenue line where entry-fee contests are permitted
ComponentBonus & Credit Manager
Automated administration of deposit-bonus programmes. Percentage or fixed bonuses are issued as
credit against a deposit, welcome bonuses on account opening, credit converts to withdrawable
balance once the traded volume defined in the campaign has been reached, and any earlier
withdrawal removes credit in proportion automatically. Limits, eligibility and expiry are set per
campaign, and every operation is reported.
Issuing bonus funds as credit rather than as balance is what makes a programme controllable.
Credit supports margin, so the client sees the benefit, but it is not their money until the
campaign conditions are met — which closes the deposit-claim-withdraw loop that makes unmanaged
schemes expensive. Cost is capped per campaign, and every issuance, conversion and removal is
written to an audit trail.
What it solves
- Deposit incentives with a cost capped per campaign and measurable afterwards
- Structural prevention of the classic abuse pattern, not manual detection of it
- No manual credit operations, and none of the errors they produce at volume
- A complete, reproducible audit trail behind every bonus decision
How it ships. The alert, campaign, tournament and bonus engines run against the broker's
MT5 server, with one admin console for configuration, live status and reporting. Client-facing
messages leave through the shared notification gateway. Bonus operations are credit on the
trading account, so what the client sees and what the back office reconciles never diverge.
What has to be right
Engagement software touches client money and public results. These are the details that turn into
support queues.
Eligibility comes from the server. Who qualifies for a bonus, who is ranked and what they
scored are derived from account and deal records, never from a marketing database exported
yesterday. Any other source eventually disagrees with the trading server, and the client is looking
at the trading server.
Crediting must be idempotent. Prizes and bonuses are money. A retry after a timeout, or a
settlement job that runs twice, must not credit twice. Each operation carries an identity and the
engine records that it has been applied.
Rules are frozen before entry opens. Metric, prize structure, entry conditions and bonus
terms are versioned and published with the campaign. Changing them mid-flight is the fastest route
to a dispute a broker cannot win, so a running campaign is immutable.
Compliance framing is configuration, not an afterthought. Eligible jurisdictions, disclosure
text, entry restrictions and bonus terms differ by licence. They are campaign parameters, so a
broker operating under more than one regime runs the same component under different rules.