Wire it into what you already run
A campaign should start in the tool your retention desk opens every morning. Each module sends from inside it and returns delivery, spend and opt-in state to the same record.
- 3
- Modules
- 9
- Connectors
- 40+
- Platform events
CRM plugins
Send from the system your team already lives in
Your retention team already spends its day in one screen. These connectors add sending to that screen and write the receipt, the spend and the consent flag onto the player profile.
- 9
- Connectors
- under 2 s
- Write-back
- none
- Middleware
Platform connectors
Drop into the gaming platform you already run
Player events already exist inside your platform. The connectors listen to them and turn deposits, bonus expiries and session milestones into messages without you writing an integration layer.
- 40+
- Event types
- under 900 ms
- Latency
- 30 days
- Backfill
Webhooks and events
Nothing goes missing while your side is down
Delivery states, inbound replies and consent changes arrive as signed callbacks. They keep arriving while your consumer catches up, and they stay replayable for a month if it does not.
- 24 hours
- Retry window
- HMAC-SHA256
- Signature
- 30 days
- Replay
Connectors we maintain
Each one is versioned against the API, so a schema change on either side does not become your on-call problem. Anything in-house speaks to the same generic outbound shape.
- Pylonhouse
- Aperia CRM
- Spoolworks
- Crestline
- Ledgerbay
- Orbiter
- Prismstack
- Tallyroom
Running something that is not listed? Tell us what it is - the generic connector covers most of them, and we build the ones that come up twice.
Connect it this sprint
Every module runs against sandbox keys first, with simulated networks and forced failure codes, so you can prove the integration before a single real message is billed.