Alerts
Axiom BB Pro provides 39 distinct alert conditions. Every alert fires only after the chart bar has closed and confirmed — none of them trigger mid-bar. This means you will never get an alert based on a provisional val...
Written By Axiom Admin
Last updated About 1 month ago
Alerts
Axiom BB Pro provides 39 distinct alert conditions. Every alert fires only after the chart bar has closed and confirmed — none of them trigger mid-bar. This means you will never get an alert based on a provisional value that might change by the time the bar settles.
That said, an alert firing does not make a trade decision for you. These alerts notify you that a structural condition has changed. What you do with that information is still your job.
How alert timing works
All 39 alert conditions are gated by barstate.isconfirmed. In plain terms:
The alert evaluates its condition only after the current chart bar has fully closed.
If the condition is true on the confirmed bar, the alert fires.
If the condition was true mid-bar but false at the close, the alert does not fire.
If the condition was false mid-bar but true at the close, the alert fires.
This gating means you can trust that the condition was real when the alert triggered — it was not a provisional spike that reversed before the bar settled.
One important nuance: The alerts evaluate on the chart timeframe's bar close, not on the slot's higher-timeframe bar close. If you have a 60-minute slot running on a 1-minute chart, the condition is true on each confirmed 1-minute bar where it still holds. The slot's BB values may update only once per hour (if On Bar Close is on), but the alert check still happens on every confirmed chart bar, so repeated alerts are possible depending on your TradingView alert frequency.
Per-slot alerts
Each of the 10 slots has three alert conditions. That is 30 alerts across all slots.
Above Basis
Below Basis
Basis Change
A note on slot numbering: The alert name uses the slot's number (BB 01, BB 02, etc.), not the timeframe. If you reconfigure Slot 1 from 5-minute to 15-minute, the alert is still called "BB 01." Match the slot number to your configuration when setting up alerts.
Blended band alerts
Three alerts track the blended band's relationship with price.
Blended Above Basis
Blended Below Basis
Blended Basis Change
Alignment alerts
Two alerts track whether all enabled slots agree on which side of their basis price sits. These are the closest thing the indicator has to a "consensus" reading — and they require the most careful interpretation.
All Above Basis
All Below Basis
Alignment alert dependency: These alerts check every enabled slot that has a valid (non-na) basis. If a slot is enabled but its cross-ticker source has no data, that slot may produce na for its basis and could be excluded from the alignment check. Make sure your enabled slots are producing valid data before relying on alignment alerts.
Blended cross alerts
Four alerts track specific price crossings of the blended band levels. These are the most likely to be misused as trade entry signals, so the framing here is especially important.
Crossed Above Upper Band
Crossed Below Lower Band
Crossed Above Basis
Crossed Below Basis
Hidden data plots
The indicator provides two hidden plots that do not draw on the chart but are available as data sources in TradingView's alert creation dialog:
Active Above Basis Count — the number of enabled slots currently showing price above their basis
Active Below Basis Count — the number of enabled slots currently showing price below their basis
These can be used in external alert configurations. For example, you could set up a TradingView alert that fires when "Active Above Basis Count" crosses above 2 (meaning at least 3 slots agree on bullish-side positioning, without requiring full alignment).
Alert misuse patterns
These are the most common ways alerts from this indicator get misinterpreted. Recognizing them before they happen is cheaper than learning from a bad trade.
Treating alignment alerts as buy/sell signals
"All slots above basis" is a structural observation, not an entry signal. It tells you the configured timeframes agree on positioning. It does not tell you that a trade is safe, profitable, or well-timed.
The way this goes wrong in practice: you set up the alignment alert. It fires. All timeframes agree, and it feels like confirmation. You enter a position because "the structure supports it." And then the lowest-timeframe slot crosses its basis the other way, alignment breaks, and you are left holding a position whose structural support just disappeared — because the alignment that felt durable was actually the peak of agreement right before one timeframe turned.
This does not mean alignment alerts are useless. They are good at flagging moments of structural agreement that deserve your attention. But "deserves attention" and "enter a trade" are different actions. Use alignment as a filter within a broader process, not as the process itself. When the alert fires, check how the alignment formed, how deep it is, and what other factors support or contradict it before you act.
Treating blended-cross alerts as breakout signals
The blended band is a weighted average. Crossing it is not the same as crossing a BB at a specific, meaningful timeframe. If price crosses above the blended upper band but is still inside the 60-minute upper band, the "breakout" is an artifact of averaging — the blend's upper band was lower than the 60-minute upper because averaging pulled it down.
The danger is that the alert sounds definitive. "Crossed Above Upper Band" feels like a breakout notification. But the upper band in question is a synthetic level, and the cross means price exceeded a weighted average of several upper bands — some of which may have been exceeded hours ago, while others have not been touched. Check which individual slots price has actually crossed before treating the alert as structurally meaningful.
Relying on basis-change alerts without checking direction
The "Basis Change" alert fires on any flip — from above to below or from below to above. It does not encode direction. If you set up a basis-change alert and act without checking the chart, you do not know whether the cross was bullish or bearish. This sounds obvious, but under time pressure it is easy to assume the direction based on recent context rather than checking.
Pair basis-change alerts with the corresponding above/below alerts, or check the chart when the alert fires. The basis-change alert tells you something happened. The above/below alerts tell you what.
Expecting alerts to fire on the HTF bar close
Alerts evaluate on the chart timeframe's confirmed bar, not on the slot's higher-timeframe bar close. If you are on a 1-minute chart with a 60-minute slot, the "above basis" condition is true on every confirmed 1-minute bar where it still holds — not just at the top of the hour. This means repeated alerts are possible for the same structural condition, depending on the TradingView alert frequency you choose.
If you want to be notified once when a condition changes rather than on every bar where it holds, use the "Basis Change" alert (which fires on the transition) rather than the "Above Basis" or "Below Basis" alerts (which fire on the state). You can also configure TradingView's alert frequency settings ("Once Per Bar Close" vs. "Once Per Bar") to control repetition, but those settings apply to the chart bar frequency, not to the HTF candle.