> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/hubconnect-operator-zone/promotions/streamer-exclusions.md). # Streamer Exclusions **Streamer Exclusions** let you agree with a supplier, directly in HubConnect, that a streamer's promotional gameplay is excluded from billing, so you're not charged for Gross Gaming Revenue (GGR) that came from your own marketing spend rather than real player activity. Until now, agreeing this with a supplier meant a private conversation with no shared record and no confirmation once it was live, and no protection if an ID or a date slipped. **Streamer Exclusions** feature puts the whole exchange in HubConnect: you submit the request, the supplier approves or rejects it, and once approved, the agreed GGR is excluded from billing automatically from the date you asked for. You can access Streamer Exclusions from the **Promotions** section in the HubConnect Operator Zone sidebar. {% hint style="info" %} **Streamer Exclusions is an exclusion tool, not a streamer campaign product.** It covers 100% of the GGR for agreed streamer activity and partial exclusions aren't supported. Not every supplier supports it either, so check the [Product Catalogue ](/hubconnect-operator-zone/product-catalogue.md)for a product before you request an exclusion on it. {% endhint %}

The Streamers Exclusion page gives you two views of the same data: * **Player List View** for every streamer player you've requested an exclusion for, with the products, games, and GGR/bet totals tied to them. * **Product List View** showing every product you have streamer exclusions on, with the streamer players attached to each one. Both views let you drill into a row for more detail, request new exclusions, and end existing ones. *** ## Player List View

The default view lists every streamer player currently covered by a request: | Column | Description | | ---------------------- | ---------------------------------------------------------- | | **Streamer Player ID** | The player ID you submitted for the streamer | | **Brand** | The Brand the exclusion applies to | | **Excluded Products** | The products currently covered | | **Excluded Games** | The games currently covered | | **Total GGR** | Gross Gaming Revenue generated across the covered activity | | **Total Bet** | Total amount wagered across the covered activity | ### Requesting a streamer exclusion

Click **Request Exclusion** to open a new tab and fill in: 1. **Brand** for the applicable Brand 2. **Products** to cover 3. **Games** for specific titles (leave blank for all games on selected products) 4. **Currencies** the exclusion covers, chosen from your Brand's supported currencies 5. **Stream** **URL**(s) for the streamer's channel 6. **Users** **by** **ID** for the streamer's player IDs 7. **Start** **date** and **End** **date** for exclusion period 8. **Note** as free text for future identification Your request goes to the supplier, and the streamer player appears in the table with a status of **Pending** until they respond. #### Effective dates Once the supplier approves, the exclusion applies from the date **you** requested, not the date they approved it. {% hint style="info" %} **Example:** You request an exclusion starting 1 September. The supplier approves it on 5 September. The exclusion still applies from 1 September, so GGR generated by the covered players between 1 and 5 September is excluded from billing too. {% endhint %} #### **Currency scope** Every exclusion is scoped to specific currencies as well as specific products, games, and player IDs. Choose which of your Brand's supported currencies the deal covers when you submit the request. Only play in those currencies is excluded from billing — play in any other currency, even from the same player IDs, stays billable. The supplier sees the currencies you've selected before they approve, and what they approve is what applies to billing. {% hint style="info" %} **Example.** You scope an exclusion to EUR only. Partway through the campaign, the streamer's account starts playing in USD under the same player ID. The USD play isn't covered by the exclusion, so the supplier continues to bill it as normal. {% endhint %} ### Viewing and managing a streamer Click any **Streamer Player ID** to open its detail table, showing every product and game combination it's excluded on:

Column	Description
Product Name	The product this row covers
Games	The games attached
Stream URL	The streamer's channel
Start Date / End Date	The dates the exclusion covers
GGR / Bet	Totals for this product and game combination
Status	Pending, Approved, Active, or Ended. See Streamer exclusion statuses

Use **Add the Streamer to More Products** to request the same streamer on additional products.

#### **Streamer Extensions** An exclusion has a start date and usually an end date. While it's running, you can change the end date. What happens next depends on the direction of the change. * **Adding** an end date to an open-ended exclusion, or **shortening** an existing one, applies immediately. **No** supplier **approval** is **needed**, and the exclusion stays **Active**. * **Extending** to a later end date is a request, not an immediate change. It needs the supplier's agreement, because it increases what gets excluded from their billing. The exclusion moves to the **Extension** status until the supplier decides. Extension is a status on your existing exclusion, shown in the same Status column as everything else, it isn't a new exclusion. **How it works:** 1. On an Active exclusion, pick a later end date. The record moves to **Extension**. 2. While in Extension, the date field is visible but disabled, only one request at a time. 3. If the supplier accepts, the record returns to **Active** with the new end date. History shows both the previous and the new date. 4. If the supplier rejects, the record returns to **Active** with the previous end date unchanged, nothing is lost. 5. You can cancel your own pending extension request at any time before the supplier decides, using the cancel action on the request. The exclusion stays **Active** with its original end date. If you've requested exclusions for this streamer before, the same form shows an action log of the supplier's past approval and rejection decisions.

Term	What it means
Extension	The status of an exclusion while a later end date is awaiting the supplier's decision
Cancelled by the operator	The state of an extension request you withdrew, or that was voided because you ended the exclusion while the request was pending
Shorten	An immediate end-date change that needs no supplier approval — covers both shortening an existing end date and adding one to an open-ended exclusion

If you've requested exclusions for this streamer before, the same form shows an action log of the supplier's past approval and rejection decisions. #### Ending a streamer exclusion {% hint style="warning" %} **Ending a streamer exclusion takes effect immediately and can't be undone.** If the exclusion has a pending extension request, ending it voids that request too — it's marked **Cancelled by the operator**, and the supplier can no longer act on it. An ended exclusion can't be revived by a late approval. {% endhint %} Select one or more rows in the table and click **End Streamer** to stop an exclusion. You'll be asked to confirm before it takes effect.

*** ## Product List View

Switch to Product List View to see the same data organised by product instead: | Column | Description | | ---------------- | ------------------------------------------------------- | | **Product Name** | The product | | **Streamers** | The streamer players currently excluded on this product | Click a product to open its detail table to see Players connected to Products:

| Column | Description | | ----------------------------- | --------------------------------------------------------------------------------------------------------------- | | **Streamer Player ID** | The streamer player excluded on this product | | **Brand** | The Brand the exclusion applies to | | **Excluded Games** | The games covered | | **Stream URL** | The streamer's channel | | **Start Date** / **End Date** | The dates the exclusion covers | | **Status** | Pending, Approved, Active, Rejected, or Ended. See [Streamer exclusion statuses](#streamer-exclusion-statuses). | Use **Add More Streamers for the Product** button to request additional streamer players on this product. You can also end a streamer exclusion from here for just this product. As with the Player List View, **this takes effect immediately once confirmed and can't be undone.**

*** ## Streamer exclusion statuses

Status	What it means
Pending	Submitted, waiting on the supplier's decision.
Approved	The supplier has accepted; the exclusion becomes Active once its start date arrives.
Active	Currently in effect. GGR from the covered activity is being excluded from billing.
Rejected	The supplier declined the request.
Ended	Finished. Either the end date has passed or it was ended manually.
Extension	A later end date has been requested and is awaiting the supplier's decision, the exclusion keeps running under its current end date until they respond.

*** ## Frequently Asked Questions **Which products support Streamer Exclusions?** Not every supplier supports it. Check the [Product Catalogue](/hubconnect-operator-zone/product-catalogue.md) before you request an exclusion on a product. **Can I exclude part of a streamer's activity, like half their GGR?** No. Streamer Exclusions covers 100% of the GGR for agreed streamer activity, partial exclusions aren't supported. **Does shortening an end date need the supplier's approval?** No. Shortening an end date takes effect straight away. **What happens if I ask for a later end date?** It's logged as an Extension request and needs the supplier's approval. The exclusion stays Active on its current end date until they decide. You can cancel the request yourself at any point before then. **Can I cancel an extension request I've submitted?** Yes. Use the cancel action on the request at any time before the supplier decides. The exclusion stays Active with its original end date. **What happens to a pending extension request if I end the exclusion?** It's voided along with the exclusion and marked Cancelled by the operator. The supplier can no longer approve it. **Can I undo ending a streamer exclusion?** No. Ending a streamer exclusion is immediate and can't be reversed. If you need the same players covered again, submit a new request. **Does the supplier see my streamer's player IDs?** No. Suppliers identify users by their own Supplier User IDs, not the player IDs you submit, Hub88 maps between the two. **Can I have exclusions with more than one supplier at once?** Yes. Requests, approvals, and statuses are tracked per product and per supplier, so you can manage a streamer across multiple suppliers and Brands from the same Streamers page. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hub88.io/hubconnect-operator-zone/promotions/streamer-exclusions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.