Signals
Talk to an engineerStart freeSnowplow
Solutions/Industry

Keep more players, and earn more from each session.

For game studios and sportsbook or casino operators, Signals tells your game server, cashier and player protection tooling what each player is doing right now, so they respond while the player is still in the session.

Start freeTalk to us
How Signals helps

What studios and operators can do with it.

RetentionHigher D1 and D7 retentionA player failing the same level a third time is about to quit, and difficulty waits for the next balance patch. Signals tells your game server this session's attempts, so it eases the level in time.How difficulty tuning works →RetentionHigher event participationThe event invite goes out on a schedule, often after the player has logged off. Signals flags a match ending with the event untouched, so your game shows the invite in the lobby before they go.How live event invites work →MonetizationHigher ARPDAUStore offers are set before the session starts, so a player out of coins mid-level sees the standard bundle. Signals tells your game server what they ran out of and where, so the offer fits.How in-game store offers work →MonetizationHigher deposit conversionA deposit bonus decided before the session pays for deposits that would happen anyway. Signals tells your cashier who opened it twice and closed it, so your rules offer it to the player it would move.How cashier bonus timing works →ProtectionEarlier player protection flagsRisk reviews run on a schedule, so a change in pattern surfaces a session late. Signals flags a stake rising fast or a session running long as it happens, and your team acts under your rules.How player protection flags work →ProtectionLower promo abuse lossesBonus abuse is caught in the next review, after the money has moved. Signals flags a bonus claimed without play or a device on its fourth account before the payout, and your risk rules decide.How promo abuse checks work →
For your engineers

One SDK, one read call.

We host it, or it runs in your own AWS or GCP account. Signals collects events with its own SDKs, updates what it knows within a second of each event, and answers a read in 6ms at the median and 10ms at p95, in-region.

Read the docs →
const player = await signals.getServiceAttributes({
  name: "live_ops",
  attribute_key: "user_id",
  identifier: playerId,
});
// { sessions_today: 3, stake_change_this_session: "rising", bonus_claimed_without_play: true, time_in_session_minutes: 48 }
Your game server or platformasks what this player is doing when it builds the offer or the level
Live ops and risk toolingget this session's behavior with each request
Braze, or any tool that takes a webhookgets a message the moment a rule fires
Snowflake, BigQuery or Databricksruns the same definitions over past sessions
Questions

Before you hand this to an engineer.

Do we replace our CRM, bonus tooling or risk platform?

No. Signals computes what each player is doing right now and serves it to the systems you run. Your CRM still sends the message, your bonus rules still decide who gets the offer and your risk platform still makes the call. Signals gives them the live player state they lack during the session.

Does changing an offer or difficulty rule still need a client release?

Not if the rule runs on your server and reads player state from Signals. Add the SDK and collection starts; you define what you want to know about a player once, in the console or in code, and your server reads the new value on the next request with nothing shipped through the app store. A rule compiled into the client still needs a release, which is why most teams move it to the server first.

Where does player data live?

Signals runs hosted by us or in your own AWS or GCP account, in the region you choose. You decide what a profile is keyed on, whether that is a player, a session, a wallet or a device, and you decide which events are collected in the first place.

Will Signals restrict a player or tell us who is at risk?

No. Signals flags a change in pattern during the session, such as stakes rising faster than usual or a session running long past the player's norm, and sends it to your team or your safer gambling tooling. What counts as a marker and what happens next are your rules. Signals does not diagnose harm and does not decide to restrict anyone.

What if next-day data is fine for us?

Then a warehouse tool is cheaper, and you should use one. Signals earns its place when the decision has to happen while the player is in the session, such as the offer at the end of a match, the bonus at the cashier or the flag before the payout.

Try it on your own site.

Add the SDK, define one thing you want to know about a visitor, and watch it update while you click around. The free tier runs on the real engine: no card, no sales call.

Start freeTalk to an engineer