← THE CHARTSPOD LEDGEROPEN TERMINAL →
TRADINGVIEW GUIDE · ALERTS

TradingView Crypto Price Alerts: Crossing vs Once-per-Bar Close

'Crossing' can fire on an intrabar wick that later reverses. 'Once per bar close' waits for confirmation and fires later. Choose the trigger that matches your plan.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

In TradingView price alerts, the condition (such as Crossing, Crossing Up or Greater Than) defines what must happen, and the trigger frequency defines when it is evaluated. 'Once per bar' can fire as soon as price touches the level inside an unfinished bar; 'Once per bar close' fires only if the condition holds when the bar closes. For crypto, intrabar triggers react fastest but include wicks that reverse; bar-close triggers confirm but arrive later. Match the trigger to whether your plan needs a touch or an accepted close.

Condition and frequency are separate choices

FrequencyFires whenTypical use
Only onceFirst time condition is met, then stopsOne-off level watch
Once per barFirst time in each bar, even intrabarFast notification of touches
Once per bar closeCondition true at bar closeConfirmed breaks
Once per minuteAt most once per minuteOngoing monitoring

Frequency names reflect TradingView's alert dialog at the time of writing; check the options shown in your account.

The wick problem

Same 15-minute bar, two alerts on a $60,000 levelSame 15-minute bar, two alerts on a $60,000 level: 09:02: Wick to $60,050: 'once per bar' fires; 09:09: Price back to $59,800; 09:15 CLOSE: Closes $59,850: 'bar close' does not fire; RESULT: One alert says break; the other says no break.09:02Wick to $60,050: 'once perbar' fires09:09Price back to $59,80009:15 CLOSECloses $59,850: 'bar close'does not fireRESULTOne alert says break; theother says no break
Illustrative prices. The trigger choice decided which story you were told. Original ChartsPod editorial graphic.

On volatile crypto pairs, especially around funding times and news, intrabar touches that fail are common. A bar-close trigger filters many of them at the cost of delay equal to the remaining bar time.

Test an alert before you rely on it

Create the alert on a level slightly above or below the current price on a short interval, such as 1 minute, with the same condition and frequency you intend to use. Watch it trigger, then compare the alert's timestamp with the bar on the chart. For a once-per-bar-close alert, the timestamp should match the bar's close; for an intrabar setting, it should match the moment of the touch.

Repeat on the real interval. A 4-hour bar-close alert on a level touched early in the bar will arrive hours later, which may be fine for a swing plan and useless for a scalp. Knowing the worst-case delay in advance prevents surprise.

Finally, write in the alert message what the alert means and what you will do. "BTC 1h close above 60k: check footprint and funding before entry" is more useful at 3 a.m. than "BTC crossing 60000".

Choosing the trigger

Trigger choice by plan typeTrigger choice by plan type. Take profit at a level: Once per bar yes, Bar close no. Stop-like warning: Once per bar yes, Bar close part. Breakout entry on acceptance: Once per bar no, Bar close yes. Retest of a level: Once per bar part, Bar close yes. News or volatility watch: Once per bar yes, Bar close no.Once per barBar closeTake profit at a level●○Stop-like warning●◐Breakout entry on acceptance○●Retest of a level◐●News or volatility watch●○● yes ◐ partial / depends ○ no ? not verified
Touch-based plans want intrabar; acceptance-based plans want bar close. Original ChartsPod editorial graphic.

Compare with ChartsPod alerts and their bar-close vs intrabar behaviour.

Open the ChartsPod terminal

ChartsPod's equivalent is covered in ChartsPod Alerts: Bar Close vs Intrabar Triggering.

Use intrabar triggers for touches and bar-close triggers for acceptance, and know how long a bar-close alert can wait.

Review TradingView Crypto Price Alerts with bar replay before using it live.

Open ChartsPod replay

Questions readers ask

Why did my TradingView alert fire but price didn't break?

An intrabar trigger fired on a wick that later reversed. Use 'once per bar close' for confirmation.

Is 'Crossing' the same as closing above?

No. Crossing can be met intrabar; closing above needs a bar-close trigger.

Do alerts work during Bar Replay?

Server-side alerts keep firing on real-time data during replay.

Sources and methodology

ChartsPod capabilities were checked against ChartsPod's public pages (home, docs, markets and indicators) on 17 October 2026. Third-party facts come only from the official sources listed. Venue availability inside ChartsPod is shown per tool, so confirm the exact exchange and contract in the terminal before relying on a feature. Worked examples use clearly labelled illustrative numbers, not recorded market data.

  1. TradingView: How do I turn Bar Replay on? — replay behaviour.
  2. TradingView Pine Script: Repainting — live vs historical calculation.
  3. ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.