# Notification Center

Set up automated alerts when your primary provider falls behind competitors in fixture or market coverage. Stay informed and respond quickly to changes in performance.

***

## Overview

Notifications enable you to:

* Create rules that trigger when coverage gaps exceed your threshold
* Receive **email notifications** when conditions are met
* Receive **webhook deliveries** directly to your systems or tools
* View **in-app alerts** from any BOOST page
* Jump directly to analysis from any alert

***

## Alert Types

| Type                 | Triggers When                                       |
| -------------------- | --------------------------------------------------- |
| **Fixture Coverage** | Your provider lags behind competitors by X fixtures |
| **Market Coverage**  | Your provider lags behind competitors by X markets  |

***

## Creating a Rule

1. Navigate to **Settings** → **Add New Rule**
2. Configure the following:

| Field                   | Description                                                                                                                                                                                                        |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Rule Name**           | A label to identify this rule                                                                                                                                                                                      |
| **Analysis Type**       | Fixture Coverage or Market Coverage                                                                                                                                                                                |
| **Alert Condition**     | Number of fixtures/markets gap that triggers the alert                                                                                                                                                             |
| **Package Type**        | InPlay or PreMatch                                                                                                                                                                                                 |
| **Sport**               | Required — select one sport                                                                                                                                                                                        |
| **Location**            | Optional — narrow the scope                                                                                                                                                                                        |
| **Competition**         | Optional — narrow the scope further                                                                                                                                                                                |
| **Primary Provider**    | Required — your baseline provider                                                                                                                                                                                  |
| **Competitors**         | Required — select at least one                                                                                                                                                                                     |
| **Active Rule**         | Toggle the rule on or off without deleting it                                                                                                                                                                      |
| **Email Notifications** | Check to receive an email when the rule triggers                                                                                                                                                                   |
| **Webhook**             | Check to send an HTTP POST to your configured endpoint when the rule triggers. Requires a webhook to be configured in **Delivery Methods** first. The name of your configured webhook is shown below the checkbox. |

3. Click **Save Changes**

***

## Notification Delivery

### Email

* Sent when rule conditions are met
* Multiple alerts are grouped by package type
* Includes links to BOOST and analysis

### In-App Bell

* Badge shows count of unread alerts
* Click to view related alerts
* **View All Alerts** — opens full Alerts page
* **Clear All** — removes alerts and resets the rule

### Webhook

* When a rule triggers, BOOST sends an HTTP POST request to your configured endpoint with a JSON payload
* One endpoint per account — all webhook-enabled rules deliver to the same URL
* Delivery status per rule is visible as a checkmark in the **Webhook** column of the **Settings** table

***

## Setting Up Webhook Delivery

Webhook delivery requires two steps: configuring your endpoint, then enabling it per rule.

### Step 1 — Configure your endpoint

1. Go to **Notification Center** → **Delivery Methods**
2. Click **Add Webhook**
3. Fill in the form:

| Field              | Description                                                                                                               |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| **Name**           | Required. A label for this webhook (e.g., "Slack Alert", "Risk Tool")                                                     |
| **URL**            | Required. Your HTTPS endpoint. The URL is validated on save.                                                              |
| **Custom Headers** | Optional. `Content-Type: application/json` is pre-filled. Add additional key-value pairs as needed (e.g., an auth token). |
| **Payload**        | Required. The JSON body sent on each delivery. Use template fields to include dynamic values.                             |

4. Build your payload using the **Payload Template Fields** panel on the right. Click any field to insert it into the payload body.

| Template Field              | Value Sent                          |
| --------------------------- | ----------------------------------- |
| `$RuleName`                 | Name of the rule that triggered     |
| `$PackageType`              | Package type (InPlay or PreMatch)   |
| `$PrimaryProviderName`      | Your configured primary provider    |
| `$CompetitorProvidersNames` | Comma-separated competitor names    |
| `$SportName`                | Sport associated with the rule      |
| `$LocationName`             | Location associated with the rule   |
| `$CompetitionName`          | Competition (if configured)         |
| `$GapValue`                 | Numeric gap that triggered the rule |
| `$PointInTime`              | Timestamp of the trigger event      |

**Example payload:**

```json
{
  "alert": "Coverage gap detected",
  "rule": "$RuleName",
  "sport": "$SportName",
  "location": "$LocationName",
  "package": "$PackageType",
  "primary_provider": "$PrimaryProviderName",
  "gap": "$GapValue",
  "timestamp": "$PointInTime"
}
```

5. Click **Save**

Once saved, the webhook appears in the **Delivery Methods** table with its name and URL. To update it later, return to **Delivery Methods** and edit the entry. Changes apply to all rules using this webhook.

### Step 2 — Enable webhook on a rule

1. Go to **Notification Center** → **Settings**
2. Open an existing rule using the **⋮** menu → **Edit Rule**, or click **Add New Rule**
3. In the **Notifications** section, check **Webhook**. The name of your configured webhook is shown below the checkbox.
4. Click **Save Changes**

The rule will now deliver an HTTP POST to your configured endpoint each time it triggers.

### Webhook delivery status

In the **Settings** table, the **Webhook** column shows delivery status per rule:

| Indicator | Meaning                              |
| --------- | ------------------------------------ |
| ✓         | Webhook is enabled for this rule     |
| *(empty)* | Webhook is not enabled for this rule |

If your endpoint is not receiving deliveries, verify it is reachable and returns HTTP 2xx. Check that any required authentication headers are correctly set in **Delivery Methods**.

***

## Testing Your Webhook

To verify your setup before using it in production:

1. Go to [webhook.site](https://webhook.site) and copy the unique URL assigned to you
2. In **Delivery Methods**, create a webhook using that URL as the endpoint
3. Enable the webhook on an existing rule in **Settings**
4. Wait for the rule to trigger (lower the threshold temporarily to speed this up)
5. Return to webhook.site — the incoming request will appear in the sidebar with your payload, all template fields resolved to real values

Once confirmed, replace the webhook.site URL with your production endpoint.

***

## Managing Alerts

From the **Alerts Page**:

* Filter by insight type, rule name, or date
* **Show Analysis** — opens Coverage Comparison table
* **Edit Rule** — modify alert configuration
* **Delete Alert** — remove individual alerts
* Bulk actions: mark as read/unread, delete

***

## Related

* [Provider Benchmark](/u/boost/provider-benchmark.md) — Coverage comparison
* [BOOST Overview](/u/boost/boost.md) — Main BOOST documentation


---

# 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.lsports.eu/u/boost/notification-center.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.