> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/boost/notification-center.md). # Notification Center Set up automated alerts when your primary provider falls behind competitors in fixture or market coverage, or when trading performance on a key market diverges from competitors. Stay informed and respond quickly without monitoring dashboards manually. *** ## Overview Notifications enable you to: * Create rules that trigger when coverage or performance 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** | The fixture gap between your provider and a competitor reaches X fixtures | | **Market Coverage** | The market gap between your provider and a competitor reaches X markets | | **Market Uptime** | Your provider's uptime on a selected market differs from a competitor by X% | | **Margin Comparison** | Your provider's margin on a selected market differs from a competitor by X% | Each rule compares your primary provider against each selected competitor individually — the alert fires as soon as any single competitor crosses the threshold. ### Alert Direction Every rule watches one direction: * **Lower Than** (default) — fires when your provider's value falls below a competitor by at least the threshold. Use it to catch coverage gaps, uptime drops, or margins that undercut the market. * **Higher Than** — fires when your provider's value exceeds a competitor by at least the threshold. Use it to spot overpricing on margins or anomalies worth investigating. *** ## 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, Market Coverage, Market Uptime, or Margin Comparison | | **Market** | Required for Market Uptime and Margin Comparison rules; hidden for coverage rules. Select Sport, Location, and Competition first — the Market list is populated from those selections. Available markets: 1X2, Under/Over, Asian Handicap (more coming soon) | | **Alert Condition** | The direction (Lower Than or Higher Than) and the gap that triggers the alert — a number of fixtures/markets for coverage rules, a percentage for Market Uptime and Margin Comparison rules | | **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** *** ## Trading Performance Alerts Market Uptime and Margin Comparison alerts use the same data you see in [Trading Performance](/u/boost/trading-performance.md), so an alert always matches what the analysis shows. * **Calculation window** — both types evaluate a rolling 24-hour window, for InPlay and PreMatch alike * **Market Uptime** — calculated on finished fixtures only, so uptime reflects complete events rather than games still in play * **Graph bell icons** — the Market Uptime and Margin Comparison graphs in Trading Performance show a bell icon with an unread-alert badge; click it to view alerts for that graph * **Email deep link** — alert emails include a **View Detailed Analytics** button that opens the Performance Matrix pre-filtered to the rule's providers, market, analysis type, and time window *** ## 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 The **Settings** table shows a **Market** column (blank for coverage rules) and a **Condition** column (Lower Than / Higher Than) for every rule. From the **Alerts Page**: * Filter by insight type, rule name, or date — the insight type filter covers all four alert types * Market Uptime and Margin Comparison alerts also show the **Threshold** you configured and the **Current Gap** that triggered the alert * **Show Analysis** — opens the matching analysis view (Coverage Comparison for coverage alerts, Trading Performance for uptime and margin alerts) with the rule's filters already applied * **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 * [Trading Performance](/u/boost/trading-performance.md) — Uptime and margin analysis * [BOOST Overview](/u/boost/boost.md) — Main BOOST documentation --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lsports.eu/u/boost/notification-center.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.