CRM and journeys

Journeys that wait for real events, not cron jobs.

The campaign engine reads the same ledger, bonus grants and game rounds as the rest of the platform. Journeys react to what players actually do, attribute revenue to the exact enrollment, and never send to a player who has not consented.

Launch your brand Book a demo

EmailSMSiOS pushAndroid pushIn-appGrant bonus

console.gamebridge.io/admin/campaigns/journey

GB Console

Players

Dashboard
Players
Payout requests

Growth

CRM campaigns
Bonus Engine
VIP management
Segmentation
Packages
Banners

Control

Risk cases
Reports
Analytics
Activity log

Casino

Games
Originals
Slot Forge
Poker

Working brand

Nova ▾

CRM / Campaigns / Journey builder

⌘K

Comeback after bonus · Journey

Preflight ✓ Activate

Funnel · 7d

Entered4,120

Delivered3,988

Opened2,410

Clicked1,102

Converted388

A/B winner

B · email+5.4 pts

Significance gate met (n ≥ 30)

Attributed revenue

$18,940

168h window · exact enrollment

Verified in the product

Every channel
email, SMS, iOS and Android push, in-app and grant bonus: Event + schedule
entry triggers, from signup to poker milestones: Full toolkit
journey steps including wait-for-event, condition and A/B split: 100+
eligibility rule fields: Configurable
attribution window per conversion goal

What the engine does

From a single blast to a full lifecycle program.

Single-stage campaigns for announcements; multi-stage journeys for onboarding, reactivation, VIP nurture and post-purchase flows. Same builder, same audience engine, same reporting.

Entry and audience

Triggers: sign up, login, purchase, VIP upgrade, bonus claimed, manual, scheduled, mission step and mission completed, poker first hand, hand milestone, tournament entry, busted out
Schedules: send now, later, or repeat hourly to monthly with a player-birthday sweep and IANA time zones
Around 106 eligibility fields with AND/OR nesting and a live audience preview
Entry limits: max total, per player, and cooldown between enrollments
Segments from the nightly segmentation engine, with manual overrides that expire

Journey steps

Send email, SMS, push (iOS and Android), in-app message, or grant a bonus
Wait for a duration, wait until a date, or wait for one of seven real events
Condition branches on ledger, wallet, KYC, VIP and activity fields
A/B split per step with adaptive mode and significance-gated winners (30+ entries, 5-point lead)
Update segment, enroll in mission, call a webhook on an allow-listed host, end

Delivery and consent

Marketing-consent gate per channel and per vertical (casino, sports) on every send
Global and brand-scoped suppressions for bounces, complaints, SMS STOP, invalid addresses and manual blocks, with audited lift
Duplicate-safe sends through owner tokens; per-state advisory locks; single-runner job locking
Server-side activation preflight that blocks campaigns with missing templates or channels
Test sends flagged so they never count in reporting

Measurement

Conversion goals: purchase or deposit, login, bonus claimed, wager, click
Attribution to the exact enrollment inside a configurable window (168 hours by default) with attributed revenue
Funnel per campaign: sent, delivered, opened, clicked, converted
Around 20 personalization variables with fallbacks
Portable JSON import and export between brands and environments

Wait-for-event

The step that makes a CRM feel alive.

Most tools wait for time. GameBridge journeys can wait for a purchase, a login, a bonus claim, a mission step, a VIP upgrade, a poker milestone or a game launch, then branch on what happened, or did not happen, in the window you set.

Reactivation fires when a player goes quiet after claiming a bonus, not on a nightly batch
Onboarding branches on first purchase inside 72 hours instead of guessing from a segment
VIP upgrades trigger a host introduction and a tier bonus reliably, exactly once
Every wait step has a reaper: stuck enrollments are cleaned up, never silently lost

How a campaign ships

Draft, preflight, activate, learn.

Step 1

Design the journey

Drag steps onto the canvas, set the trigger, define the audience with the eligibility builder and see the live count.
Step 2

Preflight

Server-side checks confirm templates exist, channels are configured for the brand and consent gates are in place. Web Push is blocked until it ships.
Step 3

Activate with a test

Send to test accounts flagged as test, then activate. Repeats respect the brand's local time zone.
Step 4

Read the funnel

Delivery funnel, A/B winner with significance, conversions and attributed revenue per campaign, exportable as JSON.

Who it is for

One canvas, three teams.

Build lifecycle programs without tickets to engineering.

Visual journey builder with a full set of step types
Segments, missions and bonuses from the same screen
A/B winners you can defend to finance
Import a proven journey into a new brand in minutes

Evaluator questions

What CRM teams ask before switching.

Can we keep our existing email provider?

Email is sent through AWS SES with SNS event feedback for delivery, bounces, complaints, opens and clicks; SMS through Twilio. Templates, sender identities and suppression lists are managed per brand inside the platform.

How does attribution work?

Each campaign can define a conversion goal (purchase or deposit, login, bonus claimed, wager, click). When the goal event happens inside the attribution window, it is attached to the exact enrollment that caused it, and revenue is credited to that campaign and variant.

Do journeys respect quiet hours?

Repeat schedules run in the brand's local time zone. There is no separate quiet-hours setting today; teams model it with schedule windows and wait-until steps.

Can journeys grant bonuses?

Yes. The Grant Bonus step uses the same grant path as the bonus engine, so per-player, per-day, global, budget and cooldown limits always apply.

Is Web Push available?

Not yet. Web Push shows as coming soon and preflight blocks activation of any campaign that uses it. iOS and Android push are live through Firebase.