Alert System
Build custom alerts with conditions, templates, backtesting, and battle testing.
Overview
The Thrive alert system is a composable, multi-condition engine that lets you define precisely when you want to be notified. Unlike simple price alerts on exchanges, Thrive alerts can combine conditions across price, funding rates, open interest, volume, divergences, whale activity, and z-scores into a single rule. This means you can express complex setups like "notify me when BTC funding rate exceeds 0.04% AND open interest is rising AND price is above the 24-hour high" as a single alert.
Alerts run server-side on Thrive's infrastructure, so they work even when you are not on the platform. Notifications are delivered via email, in-app push (PWA), or both. Every triggered alert is logged in your alert history for review and performance analysis.
Alert availability by plan
Condition Types
Each alert consists of one or more conditions joined by AND logic. All conditions must be true simultaneously for the alert to trigger. The following condition types are available.
Price Conditions
Price conditions trigger based on absolute price levels or percentage changes over a specified timeframe.
Triggers when price crosses above or below a specific USD value.
Triggers when the percentage change over a timeframe (1H, 4H, 24H) exceeds a threshold.
Triggers when price enters or exits a defined range. Useful for breakout monitoring.
Triggers when price makes a new high or low over the specified lookback period.
Funding Rate Conditions
Funding rate conditions monitor the perpetual futures funding rate and trigger when it reaches levels that indicate extreme positioning.
Triggers when the aggregated funding rate crosses a specific threshold (e.g., above 0.05% or below -0.03%).
Triggers when the funding rate z-score exceeds a standard deviation threshold.
Triggers when funding rate changes by more than a specified amount within a timeframe.
Open Interest Conditions
Triggers when open interest changes by more than a specified percentage over a timeframe.
Triggers when total open interest crosses an absolute USD threshold.
Triggers when the OI z-score reaches a statistical extreme.
Volume Conditions
Triggers when volume exceeds a multiple of its average (e.g., 3x the 7-day average).
Triggers when 24H volume crosses an absolute threshold.
Divergence Conditions
Triggers when a new divergence is detected on the asset, optionally filtered by type.
Triggers when an existing divergence reaches a specified severity level (moderate, severe, critical).
Triggers when an active divergence resolves, allowing you to review the outcome.
Whale Movement Conditions
Triggers when a transaction above a specified USD amount is detected for the asset.
Triggers when net exchange flows exceed a threshold, indicating potential selling or accumulation.
Triggers when wallets identified as smart money by Thrive’s classification engine execute transactions in the asset.
Whale and smart money conditions
Creating an Alert
Alerts are created from the Alerts page in the sidebar. The builder interface walks you through each step of the configuration process.
Select an asset
Choose the asset you want to monitor. You can type a ticker in the search field or select from your watchlist. Some condition types (like market-wide whale alerts) can be configured without an asset selection.
Add conditions
Click Add Condition to add your first condition. Select the condition type from the dropdown, configure the parameters (threshold, timeframe, comparison operator), and click confirm. Repeat for additional conditions. All conditions are joined with AND logic.
Configure notification channels
Choose how you want to be notified: in-app push notification, email, or both. Email notifications include a direct link to the alert detail page with the full context of the trigger.
Set alert behavior
Choose whether the alert triggers once and then deactivates, or repeats every time the conditions are met (with a configurable cooldown period between triggers to prevent spam). You can also set an expiration date after which the alert auto-deactivates.
Save and activate
Review the alert summary, give it a descriptive name, and click Activate. The alert begins monitoring immediately. You will see it in your active alerts list with a live status indicator showing its current evaluation state.
Alert Templates
Thrive provides pre-built alert templates for common trading setups. Templates are fully configured alerts that you can activate immediately or customize before saving. They are designed to help new users get started and to save experienced users time on frequently used configurations.
Triggers when funding rate z-score exceeds +/- 2.0. Indicates crowded positioning that historically precedes reversals.
Triggers when open interest increases by more than 15% in 4 hours. Indicates aggressive new positioning.
Triggers when a severe price-funding divergence is detected. Pre-filtered for the highest-probability pattern.
Triggers when smart money wallets execute buys exceeding $500K in the asset. Pro+ only.
Triggers when price moves more than 3% in one hour with volume above 2x average. Captures momentum ignition events.
Triggers when estimated liquidation volume exceeds a threshold, indicating a potential cascade event.
Start with templates
Notification Channels
Alerts can be delivered through two channels. Each channel can be enabled or disabled per alert, and you can set global defaults in Settings.
| In-App Push | Native push notifications via the PWA. Fastest delivery method. Requires the PWA to be installed and notification permissions granted. Works on desktop and mobile. |
| Sends a formatted email with the alert name, trigger conditions, current market context, and a direct link to the alert on Thrive. Costs 1 credit per email sent. |
Backtesting Alerts
Before activating an alert, you can backtest it against historical data to see how often it would have triggered and what happened to price afterward. Backtesting lets you validate your alert logic before committing to live notifications.
Running a Backtest
After configuring an alert in the builder, click the Backtest button instead of Activate. Select a historical lookback period (7 days, 30 days, 90 days, or 1 year) and click Run. The system evaluates your alert conditions against historical data and returns a list of every hypothetical trigger.
Backtest Results
The backtest results panel shows every hypothetical trigger event on a timeline. For each trigger, you can see the market context at the time, what happened to price in the 1 hour, 4 hours, 24 hours, and 7 days following the trigger. Aggregate statistics include total trigger count, average forward return by timeframe, and win rate (percentage of triggers where price moved favorably).
Backtesting is Pro+ only
Battle Testing
Battle testing is an advanced feature that stress-tests your alert configuration under different market regimes. While backtesting shows you what happened historically, battle testing simulates how the alert would perform under specific conditions: high volatility, trending markets, range-bound markets, and crash scenarios.
Market Regime Simulations
| Bull Trend | Simulates the alert against periods where the asset was in a sustained uptrend. Tests whether the alert triggers appropriately during trending conditions. |
| Bear Trend | Simulates against sustained downtrend periods. Validates alert behavior during bear markets. |
| Range-Bound | Simulates against periods of consolidation with low directional bias. Tests whether the alert generates excessive false triggers in choppy conditions. |
| High Volatility | Simulates against the most volatile historical periods. Checks whether the alert is robust enough to avoid noise-driven triggers. |
| Crash / Capitulation | Simulates against sharp drawdown events. Validates that the alert behaves correctly during extreme market stress. |
Battle testing is useful for ensuring your alert does not trigger excessively during market conditions where you would not want to trade. An alert that triggers 50 times during a range-bound market is likely too sensitive and needs tighter conditions.
Managing Active Alerts
The Alerts page shows all your active, paused, and recently triggered alerts in a single view. From here you can pause, edit, duplicate, delete, or review the trigger history of any alert.
Currently monitoring. The alert evaluates conditions on every data update cycle.
Temporarily disabled. Conditions are not evaluated. Resume at any time without reconfiguring.
The alert has fired. If set to one-time, it is now inactive. If set to repeat, it enters cooldown before re-evaluating.
The alert reached its expiration date and was automatically deactivated.
Alert History
Every alert trigger is recorded in your alert history with a timestamp, the exact market conditions at trigger time, and links to the relevant asset page. Over time, the alert history becomes a valuable dataset for evaluating which alert configurations are producing actionable signals and which need refinement.
Alert Best Practices
Single-condition alerts (e.g., price above X) trigger frequently and add noise. Combine price with a derivatives or volume condition for precision.
Always run a backtest to verify the alert triggers at a reasonable frequency and produces favorable forward returns.
For repeating alerts, set a cooldown period (e.g., 4 hours) to prevent the same condition from flooding your notifications.
Use names like "BTC Funding Extreme Short Setup" rather than "Alert 1". Your future self will thank you when managing 20+ alerts.
Deactivate or delete alerts that have not triggered in 30 days. Stale alerts consume monitoring resources and clutter your dashboard.
Templates encode setups that have historically performed well. Customize from there rather than building from scratch.
Next Steps
Watchlist
Pair your alerts with a curated watchlist for comprehensive monitoring.
Divergence Detection
Use divergence conditions in your alerts for mean-reversion setups.
Data Feed
Alert on the same funding, liquidation, and volume prints the data feed shows.
Asset Analysis
Understand the data behind the conditions you are monitoring.
