Since 27 May 2026, you can put a TradingView alert directly on a Fibonacci drawing. The alert watches one level, or the zone between two levels, of a Fib Retracement or Trend-Based Fib Extension, and it moves with the drawing whenever you reposition the tool or change its settings.
That removes the old workaround of copying each level onto a horizontal line. It also means the price an alert watches can change without you opening the alert. Any price you typed into the alert's message, such as a stop level for an automated instruction, does not move with it. This article explains the level and channel conditions, works through an example with real arithmetic, and lists what to check before a Fib alert sends anything to PineConnector.
What changed
TradingView announced alerts on Fibonacci drawings on 27 May 2026 (the post was updated on 29 May 2026). Before that, an alert on a Fib level meant drawing a horizontal line or ray over the level and redoing it whenever you adjusted the Fib tool. Now the alerts sit on the drawing and move with it when you reposition the tool or change its settings[1].
Two tools are covered: Fib Retracement and Trend-Based Fib Extension. TradingView's Help Center gives the setup. For a retracement, select the two extreme points, then right-click the drawing and choose "Add alert on Fib retracement". For an extension, identify three points (the start of the move, its end and the end of the correction) and choose "Add alert on trend-based fib extension". A left-click and "Add alert" also opens the dialog[3].
An alert on a drawing counts as a technical alert, which has its own limit per TradingView plan, separate from price alerts[5].
Level conditions and channel conditions
The announcement lists two groups of conditions[1]. For an individual level: Crossing, Crossing Up, Crossing Down, Greater Than and Less Than. For the zone between two levels: Entering Channel, Exiting Channel, Inside Channel and Outside Channel. The levels on offer are 0.5, 0.618 or "any visible level from your drawing settings".
The Fib pages list these conditions and give examples for only two of them. TradingView's Help Center defines the operators once for all technical alerts, and paraphrased, it describes what triggers each one[3]:
- Crossing / Crossing Up / Crossing Down: one level. Triggers when the value reaches the level from either direction, or from the one you pick.
- Greater Than / Less Than: one level. Triggers when the value "surpasses or falls below" the level.
- Entering / Exiting Channel: the zone between two levels. Triggers when the value reaches the zone's boundaries from a certain direction.
- Inside / Outside Channel: the zone between two levels. Triggers when the value "moves into or out of" the zone.
All four definitions are worded around price reaching, passing, or moving into or out of something. None of them says whether a condition that remains met, such as price staying above a level, triggers again on later bars. How often each condition fires under each frequency is not documented, so count the triggers on a demo alert before relying on one.
The frequency setting sets how often an alert may trigger. In TradingView's definitions, Once only triggers a single time. Once per bar checks every bar and triggers whenever conditions are met, no more than once per bar, and Once per bar close does the same but waits for the bar to close. The fourth option, listed as "Once per minute or every time", checks conditions every minute and triggers whenever they are met[4]. Any frequency other than Once only can therefore send the same message more than once. Once per minute is not limited to one trigger per bar, so on a chart timeframe above one minute it can trigger more often than Once per bar.
The announcement and the Help Center describe the level choice differently. The announcement describes choosing the level you want to track[1]. The Help Center's retracement page describes a Crossing alert as triggering when price crosses any of the active levels[2]. Neither page explains the difference, so check in your own alert dialog which level or levels the alert watches before relying on it.
A worked example: what re-anchoring does to the numbers
The prices below are illustrative. They use EURUSD with five decimals, a swing low of 1.08000 and a swing high of 1.10000, so the range is 0.02000. The levels are measured down from the swing high, which is how a retracement of an up-move is usually read: level 0 at the high, level 1 at the low.
- 0.5 level: 1.10000 − 0.5 × 0.02000 = 1.09000
- 0.618 level: 1.10000 − 0.618 × 0.02000 = 1.08764
- Channel from 0.5 to 0.618: 1.08764 to 1.09000
Now the market makes a higher high and you drag the drawing's high point to 1.10500. The range becomes 0.02500 and every level is recalculated:
- 0.5 level: 1.10500 − 0.5 × 0.02500 = 1.09250
- 0.618 level: 1.10500 − 0.618 × 0.02500 = 1.08955
- Channel from 0.5 to 0.618: 1.08955 to 1.09250
An alert on the 0.618 level now watches 1.08955 instead of 1.08764, about 19 pips higher, and you did not touch the alert. That is the feature working as designed. The part that does not move is text: if the alert's message contained a stop price you calculated from the old drawing, it still says the old number.
Check the direction on your own chart. TradingView's Help Center says the 0% and 100% levels come from the two extremes of the trend line you draw, and the drawing has a Reverse option that flips it vertically[2]. Read the level labels and prices on the drawing itself rather than assuming which end is 0.
What moves with the drawing, and what does not
- The level price the alert watches moves. TradingView says Fib alerts move with the tool[1].
- Channel boundaries between two levels move with the levels.
- Prices typed into a message do not move. A message is text you entered.
- Levels with "Fib levels based on log scale" switched on are calculated differently, according to the Help Center[2].
- For comparison, an indicator alert after you change the indicator's inputs does not follow. It keeps triggering on the old settings[3].
The last row is a useful reminder that TradingView alerts do not all behave the same way. Fib alerts follow the drawing, as TradingView documents[1]. An indicator alert keeps the settings it was created with[3], and TradingView's Pine Script FAQ says an alert on a script saves a snapshot of the script and its inputs[9]. That snapshot is the problem described in why an alert keeps using old Pine Script settings.
You can also label a level. The Help Center says custom text added to a level, for example "Strong resistance", is displayed in the alert message[2]. That is helpful for notifications to your phone. For a message that PineConnector reads, extra text is a problem, because PineConnector's syntax guide asks you to keep explanations out of TradingView's Message field[6]. How level text combines with a message of your own is not described, so check the first logged message if you ever rely on one.
Fib alerts and PineConnector: what is and is not established
TradingView's sources for Fib alerts describe the conditions, the setup, how the alert follows the drawing, and that level text appears in the alert's message. They do not describe webhook delivery for Fib alerts, or whether the whole message can be replaced with text of your own. Not described is not the same as unavailable, but it means there is no documented or tested route from a Fib alert to PineConnector, and this article did not test one. For that reason it gives no message to paste.
If you consider connecting one, these points follow from how the alert and PineConnector's syntax are described:
- Typed prices go stale. Any absolute price written into a message, such as a stop, keeps its value when the drawing moves. Only the watched level follows the drawing.
-
Distance-based stops are measured from the entry, not the drawing. PineConnector's
sl_pips=sets a stop a number of pips from entry, where one PineConnector pip is 10 quoting points[6]. It does not track a Fib level either. - Repeats. Any frequency other than Once only can trigger more than once, and each trigger would send the message again. How often a given condition repeats is not documented, so count the triggers on a demo alert first.
- A triggered alert is not a trade. PineConnector's documentation says a received alert does not prove a broker fill[7]. At the broker, an accepted order, a filled deal and an open position are separate checks.
Any route you try belongs on a demo account first, through PineConnector's demo test workflow, comparing the TradingView Alerts log, PineConnector's Bridge and the broker account.
Limitations and common mistakes
- Re-anchoring after the alert is set. The watched price changes. Open the alert afterwards and confirm the level it now watches.
- Hidden levels. The announcement offers the levels visible in your drawing settings[1]. A level switched off there is not one you should expect to pick.
- Assuming how often a condition fires. TradingView does not say how often Greater Than, Less Than, Inside Channel or Outside Channel trigger while price stays on one side, and Once per minute is not limited to one trigger per bar. Count the triggers on a demo alert. TradingView stops a regular alert once it reaches 15 triggers in a three-minute window[8].
- Switching the chart between linear and log scale. With "Fib levels based on log scale" enabled, the levels are calculated differently.
- Trend-based extensions. The tool uses three points: the start of the move, its end and the end of the correction[3]. Moving any of them can change the watched level, so recheck the level prices after every adjustment.
What to check next
- After drawing or adjusting the Fib tool, open the alert and confirm the level or channel and its current price.
- Choose the condition and frequency, then count how many times a demo alert triggers before anything acts on the message.
- If a message contains absolute prices, remember they do not move with the drawing.
- Treat any connection to PineConnector as untested: try it only on a demo account through PineConnector's demo test workflow, and inspect the first logged message.
The same questions apply to other drawing alerts. Rectangle alerts have zone and side-of-zone conditions, and long and short position alerts watch entry, stop and target together.
Reviewed 23 September 2026. Facts were checked against the linked sources on that date. The worked example is arithmetic on illustrative prices; no alert in this article was run against a trading account.
Related reading
- TradingView updates for alert-based automation: a practical index
- TradingView rectangle alerts: zone conditions and side-of-zone conditions
- Alerts on TradingView long and short position drawings
- Choosing position size, stop loss and take profit for a PineConnector alert
- TradingView webhook received, but no MT5 trade: a stage-by-stage diagnosis
Sources
- TradingView Blog – Introducing alerts on Fibonacci drawings, published 27 May 2026, updated 29 May 2026, accessed 23 September 2026.
- TradingView Help Center – Fibonacci retracement drawing tool, accessed 23 September 2026.
- TradingView Help Center – Getting started with technical alerts, accessed 23 September 2026.
- TradingView Help Center – Differences between alert frequencies, accessed 23 September 2026.
- TradingView Help Center – Alerts separation by type, accessed 23 September 2026.
- PineConnector Docs – PineConnector Syntax, accessed 23 September 2026.
- PineConnector Docs – Connect your strategy, accessed 23 September 2026.
- TradingView Help Center – Alert was triggered too often and stopped, accessed 23 September 2026.
- TradingView – Pine Script documentation, FAQ: Alerts, accessed 23 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
