CRM, bonuses & affiliates
Growth tooling that cannot route around consent.
Segments, automation journeys, campaigns, a bonus engine and affiliate attribution — with marketing consent and self-exclusion checked by construction, in the send path, rather than by a coordinator remembering to tick a box.
Segmentation
9 rule types, combined with AND, failing safe
The design decision worth interrogating is what happens when the segmentation engine meets a rule type it does not recognise — after a version skew, a bad migration, or a hand-edited segment. Ledgerfield excludes every player from that segment. The alternative default quietly includes everybody, and the first time you notice is when a bonus lands in an account it should never have reached.
Segments
Rules over deposits, losses, activity recency, lifetime value, game preference, verification state and more — evaluated server-side and reusable across campaigns, offers and automations.
Automation journeys
Multi-step enrolments with steps, delays and conditions. A player enrols, moves through steps on schedule, and exits when a condition stops holding — with each enrolment individually inspectable.
Consent in the send path
Marketing consent and self-exclusion are checked where the send happens, not where the campaign is authored. A campaign that targets an excluded player does not send to them — there is no path where it could.
Email templates & tracking
Templates, sends and open/click tracking are modelled, so a campaign's reach is a queryable fact rather than an export from somebody else's tool.
Bonus engine
Wagering is allocated, not broadcast
When a player with an active bonus places a bet, the wagering contribution has to be attributed to a specific bonus. Applying the turnover to every active bonus at once is the shortcut, and it lets a player clear several bonuses with one stake. Ledgerfield allocates the contribution instead.
- Offers are targeted, granted and evaluated separately — an offer a player is eligible for, a bonus they hold, and the conditions that release it are three different objects with three different lifecycles.
- Conditions are evaluated, not hard-coded, so a wagering requirement, a minimum odds floor, a game restriction and an expiry are configuration rather than a release.
- Every grant, contribution and forfeiture is a ledger event with an actor and a reason — which is what makes a bonus dispute answerable months later.
- Loyalty tiers and referrals run through the same reward-granting path, so a VIP award and a bonus release cannot drift into two different code paths with two different sets of rules.
Affiliates
Attribution that survives an audit
Clicks, referrals and commissions are separate records, so an affiliate invoice can be reconstructed from the events that produced it rather than from a rolled-up figure. Commission accrual is a ledger movement like any other.
Where this stack is thinner than an incumbent'sLedgerfield has no bundled email service provider, no SMS gateway and no push infrastructure — sends are modelled and tracked, and the transport is yours to point at. There is also no visual drag-and-drop journey builder; automations are configured through the API and the back office rather than a canvas. If your marketing team's day is spent inside a visual builder, that is a real difference and it is worth raising early rather than discovering at handover.
Bring your worst bonus-abuse case.
The interesting question is never whether a bonus engine can grant a bonus. It is what happens on the sixth edge case — bring one and we will walk it through the code.