---
title: "Deposit No Bet Documentation"
slug: "deposit-no-bet-use-case-documentation"
description: "Optimize your Deposit No Bet journey to convert funds into active play, reducing drop-off and enhancing player engagement with timely, personalized prompts."
updated: 2026-10-06T09:45:05Z
published: 2026-10-06T09:45:05Z
canonical: "docs.xtremepush.com/deposit-no-bet-use-case-documentation"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deposit No Bet Documentation

| ![A bar graph illustrating growth trends over time with increasing values.](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/levels(1).png?sv=2026-02-06&spr=https&st=2026-10-31T21%3A12%3A45Z&se=2026-10-31T22%3A12%3A45Z&sr=c&sp=r&sig=9pWxCD%2BzXBjZ6DAVCdLIWLmN3%2BqCBPVOYtegnDPVK74%3D) Level: Basic | ![A target icon with an arrow, symbolizing focus and goal achievement.](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/gaol1(1).png?sv=2026-02-06&spr=https&st=2026-10-31T21%3A12%3A45Z&se=2026-10-31T22%3A12%3A45Z&sr=c&sp=r&sig=9pWxCD%2BzXBjZ6DAVCdLIWLmN3%2BqCBPVOYtegnDPVK74%3D) Goal: Retention | ![A blue checkmark icon indicating completion or approval in a digital interface.](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/tick(1).png?sv=2026-02-06&spr=https&st=2026-10-31T21%3A12%3A45Z&se=2026-10-31T22%3A12%3A45Z&sr=c&sp=r&sig=9pWxCD%2BzXBjZ6DAVCdLIWLmN3%2BqCBPVOYtegnDPVK74%3D) Expectation: Increased Engagement |
| --- | --- | --- |

## **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**](/knowledgebase/docs/deposit-no-bet-use-case-documentation#use-case-requirements)**.**

![Promotion for a €10 free bet and reminder for Sam to use it.](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/dnb.png?sv=2026-02-06&spr=https&st=2026-10-31T21%3A12%3A45Z&se=2026-10-31T22%3A12%3A45Z&sr=c&sp=r&sig=9pWxCD%2BzXBjZ6DAVCdLIWLmN3%2BqCBPVOYtegnDPVK74%3D)

## **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.

![](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/Deposit No Bet Journey.png?sv=2026-02-06&spr=https&st=2026-10-31T21%3A12%3A45Z&se=2026-10-31T22%3A12%3A45Z&sr=c&sp=r&sig=9pWxCD%2BzXBjZ6DAVCdLIWLmN3%2BqCBPVOYtegnDPVK74%3D)

Example journey. Channels, wait times and steps will vary by project.

| Building block | In the example | Ways to adapt it |
| --- | --- | --- |
| Trigger | `deposit` event | Limit to first deposits (`deposit_number` 1), or apply to every deposit with a re-entry rule |
| Filter | Segment: no sports bet or casino wager placed | Include every play event that applies to your products |
| Wait | 30 minutes | Shorter for fast-action casino play (for example 15 minutes), longer for sports (for example 60–120 minutes), where deposits often precede a fixture |
| Bet check | Has the player placed a bet since depositing? | Count every play event that applies to your products (see Event below) |
| Content split | Split by sign-up product: sports, casino, default | Add branches for other products. Keep a default branch for players with no sign-up product |
| First prompt | Push, at 30 minutes, matched to the split | Choose the channel. Add a fallback, such as email or inbox, for players who haven't opted in to push |
| Second wait and check | A further 60 minutes (90 in total), then checked again | Change the gap, or use a single prompt |
| Second prompt | SMS, at 90 minutes, matched to the split, only if the player still hasn't bet | Use a different channel, and make sure the player has consented to it |
| Goals and end | A success goal at each check, and an end point after the final prompt | Every path needs an end point |

A player who deposits several times in quick succession could enter more than once. Set [message limits](https://docs.xtremepush.com/docs/campaign-events#message-limits1) to control campaign re-entry, and use [Engagement Categories](https://docs.xtremepush.com/docs/en/engagement-categories) to cap how often prompts are sent. Every path must finish at an endpoint. See [Ending Journeys and Analysing Results](https://docs.xtremepush.com/knowledgebase/docs/en/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](https://docs.xtremepush.com/docs/unsubscribe-link-behaviour) route in every email. [Consent Manager](https://docs.xtremepush.com/docs/en/consent-manager) is an optional feature, enabled on request. See [Managing User Consent](https://docs.xtremepush.com/knowledgebase/docs/en/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](https://docs.xtremepush.com/docs/engagement-rules#global-include-condition1).

**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.

****Deposit Payload Example****

```json
{
  "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
  }
}
```

****Bet Placed Payload Example****

```json
{
  "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.

| Field | Requirement | Used for |
| --- | --- | --- |
| `user_id` | Required | The unique internal ID for the player. |
| `timestamp` | Required | ISO 8601 date-time |
| `deposit_number` | Recommended | Identifies first versus repeat deposits, and lets you limit the journey to first deposits |
| `amount` | Recommended | Deposit amount, for personalisation and segmentation |
| `balance_cash` | Recommended | Cash balance after the deposit, for personalisation |
| `balance_total` | Optional | Cash plus bonus balance |
| `payment_method` | Optional | Payment method used |

## Profile Attributes

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

| Attribute | Requirement | Used for |
| --- | --- | --- |
| `first_name` | Required | Greeting (set a fallback value) |
| `account_status` | Required | Only active accounts receive messages |
| `is_self_excluded`, `is_blocked`, `is_abuser` | Required | Keeping excluded or flagged players out of the journey. Updated by `player_update`event |
| `currency_code`, `currency_symbol` | Required if amounts are shown | Correct currency in content |
| `signup_product` | Recommended | Sports versus casino focus |
| `signup_offer` | Recommended | Offer-specific content |
| `acquisition_source_code` | Optional | Content by acquisition channel |

## 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](https://docs.xtremepush.com/knowledgebase/docs/en/creating-computed-attributes).

| Computation | Description |
| --- | --- |
| `has_placed_sports_bet` | TRUE if the player has ever placed a sports bet |
| `has_placed_casino_bet` | TRUE if the player has ever placed a casino bet |
| `deposits_made` | Total number of deposits made (lifetime, or over the last 7, 14 or 30 days) |

## **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](https://docs.xtremepush.com/docs/campaign-split-test#control-group1) 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](https://docs.xtremepush.com/knowledgebase/docs/en/using-decision-branches-in-the-journey-builder).

### Related use cases

Players who make their first deposit through the [Welcome Journey](https://docs.xtremepush.com/knowledgebase/docs/en/welcome-journey-use-case) can enter Deposit No Bet if they haven't bet. Players who go quiet later are covered by [Churn Prevention](https://docs.xtremepush.com/knowledgebase/docs/en/churn-prevention-use-case).

| ## **Further Implementation Details** For more information on event tracking, API limits, and SDK integration, please browse our full developer resources. [**View Our Docs**](https://docs.xtremepush.com/?ref=brand-cta) |
| --- |