Deposit No Bet Documentation

Use Case Description

A Deposit No Bet journey supports players who have funded their account but have never placed a bet. Players enter the journey when they deposit, and a segment keeps out anyone who has already played. After a wait you define, the journey checks whether they have bet. Players who have leave the journey. Players who haven't receive a timely prompt tailored to the product they signed up for.

To take full advantage of the Deposit No Bet journey, please review the technical requirements.

Deploying Your Use Case

Understanding The Flow

Players enter the journey on the deposit event. A segment on the journey then keeps out anyone who has already placed a sports bet or casino wager, so only players who have deposited but haven't played are prompted. Without it, every depositor would enter, including players who go on to bet straight away. The screenshot below shows one example of how a Deposit No Bet journey can be built. Your own can differ in channels, timings and number of steps.

The example below then waits 30 minutes and checks whether the player has bet. Players who have are recorded as a success. For the rest, the journey splits by sign-up product and sends a push prompt with sports, casino or default content, waits a further 60 minutes, and checks again. Players who still haven't bet receive a matching SMS prompt, and the journey ends.

A player who deposits several times in quick succession could enter more than once. Set message limits to control campaign re-entry, and use Engagement Categories to cap how often prompts are sent. Every path must finish at an endpoint. See Ending Journeys and Analysing Results.

Adjusting the Use Case

The Deposit No Bet journey can be adapted to your player base, product mix and engagement strategy. Key areas to consider:

Timing and cadence

• Set the wait before the first prompt using your own data, for example your median time from deposit to first bet. Allow for product differences: casino players tend to start playing sooner than sports bettors.

• Add a follow-up reminder for players who still haven't bet, for example a first prompt 30 minutes after the deposit and a second at 2 hours.

Content personalisation

• Use dynamic fields such as first_name and currency_symbol. If you show a balance, use balance_cash from the deposit event.

• Use calls to action that suit a player who has already deposited, such as "Place a bet", "Browse today's fixtures" or "Play your favourite games".

• Use signup_product to choose the focus. The example splits on it, with a default branch for players where it is missing.

• For sports, link to upcoming fixtures where your content can include them. For casino, point to popular games or categories.

Channels

• Short windows suit fast channels such as push and inbox, with email for follow-ups.

Regulatory compliance

• Include the responsible gaming messaging and terms your licence requires in every message. Requirements vary by jurisdiction, so check with your compliance team.

• Include an unsubscribe route in every email. Consent Manager is an optional feature, enabled on request. See Managing User Consent. If you don't use it, make sure channel marketing permission is held elsewhere in your project.

• Make sure self-excluded, blocked and bonus-abuse-flagged players do not enter the journey, using entry criteria or your project's global include conditions.

Use Case Requirements

Before deploying this use case, ensure your data infrastructure supports the technical requirements outlined below. This use case relies on real-time event triggers and profile attributes to deliver timely, relevant messaging to the right players.

The following tables specify which event data and profile attributes are required, recommended, or optional for optimal performance. Proper data foundation is the difference between a high-performing automated journey and one that underdelivers on its potential.

Event

The following events are required for this use case:

The deposit event is required. You also need at least one event that shows the player has started playing:

• bet_placed for sports.

• casino_wager_placed for casino.

• bingo_ticket_purchase or lottery_ticket_purchase, if you offer those products.

The journey uses these play events to decide whether to prompt, so include every product your players can use. Each event must include a user_id and a timestamp in ISO 8601 format.

{
  "event": "deposit",
  "timestamp": "2025-07-19T13:53:27Z",
  "user_id": "user123",
  "value": {
    "deposit_number": 5,
    "payment_method": "Visa",
    "currency_code": "GBP",
    "amount": 200.00,
    "balance_cash": 700.00,
    "balance_bonus": 0,
    "balance_total": 700.00
  }
}

{
  "event": "bet_placed",
  "timestamp": "2025-08-17T14:10:00Z",
  "user_id": "user123",
  "value": {
    "bet_id": "B123456789",
    "bet_type": "multi",
    "odds": "2.50",
    "stake_cash": 50.00,
    "stake_bonus": 0,
    "stake_total": 50.00,
    "potential_return": 125.00,
    "balance_cash": 1100.00,
    "balance_bonus": 200.00,
    "balance_total": 1300.00
  }
}

Data Payload

The following event payload fields are essential for triggering and personalising the Deposit No Bet journey. These data points from the deposit and bet_placed events enable automated player re-engagement.

Profile Attributes

These player profile attributes are used for segmentation, personalisation, and targeting throughout the Deposit No Bet journey.

Computed Attributes

Computed attributes from Xtremepush Intelligence are optional. Use them to build the journey's segment, for example has_placed_sports_bet and has_placed_casino_bet both FALSE, so that players who have already bet are kept out. Players who enter have no betting history, so use signup_product and the deposit details to personalise. See Creating Computed Attributes.

Optimising Your Deposit No Bet Journey for Maximum Conversion

Timing and relevance decide whether a prompt helps or just interrupts. Keep improving the journey with your own performance data.

Measure

• Track the share of depositors who bet within 2 hours and within 24 hours of depositing, and the time from deposit to first bet.

• Also watch message engagement and unsubscribe rate.

• Keep a control group so you can see what the journey adds beyond players who would have bet anyway.

Test one variable at a time

• Compare first-wait lengths, such as 15, 30 and 60 minutes.

• Compare channels, and personalised content versus generic content.

• Compare one prompt versus two.

• Run these with decision branches.

Related use cases

Players who make their first deposit through the Welcome Journey can enter Deposit No Bet if they haven't bet. Players who go quiet later are covered by Churn Prevention.