# Introducing Sportsbook Type of Rewards and Campaigns

**Released**: 3 September 2025

***

[**Rewards**](/operator-backoffice/rewards.md) and [**Campaigns**](/operator-backoffice/campaigns.md) now both **support** two **types**: **Casino** and **Sportsbook**. The two types are added as tabs to Rewards and Campaign views in Operator Backoffice, giving you a clearer, more structured way to manage incentives across products.

<div><figure><img src="/files/GRrZhyloWW4mQYVK23Pt" alt=""><figcaption></figcaption></figure> <figure><img src="/files/UqSe7suFDa5Hk9GNRlXO" alt=""><figcaption></figcaption></figure></div>

This update brings three major improvements to how rewards and campaigns are set up and managed:

* **Product split**: Casino and Sportsbook rewards and campaigns are now separated into dedicated tabs. This prevents cross-product errors and keeps configuration simple.<br>
* [**Custom Sportsbook prepaids**](/operator-backoffice/rewards.md#adding-a-casino-reward)**:** Operators can now create flexible templates with sportsbook-specific parameters, including odds ranges, sport categories, max payout, bet count, and validity windows.<br>
* **Integrated campaign creation:** Prepaids can be linked directly to campaigns in the same flow, removing the need to switch between pages. Rewards can also be created inside a campaign setup using a simple toggle.

Rewards and Campaigns continue to work independently but are closely connected: **campaigns** **group** and distribute **rewards**, while **rewards** can **exist** **standalone** if required. To keep the logic clean, Casino and Sportsbook campaigns and rewards **must be created separately.**&#x20;

**Sportsbook rewards and campaigns** can only be created through Operator Backoffice, not through API.

Operators also benefit from a dedicated Sportsbook Rewards list, where key details such as UUID, categories, odds ranges, bet amounts, payout limits, and status are tracked alongside linked campaigns and users.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hub88.io/product-news/september-2025/introducing-sportsbook-type-of-rewards-and-campaigns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.