Pivot Points High Low: Detection Delay and Chart Labels
Pivot Points High Low identifies local price extremes using bars on both sides of a candidate turning point. The right-side requirement creates a detection delay: the pivot price belongs to an earlier bar, but the pivot was not known on that bar. This distinction matters when interpreting a chart, building an alert, or testing a strategy.
Four lengths control the search
Pineify's implementation uses TradingView's built-in pivot-high and pivot-low functions. It exposes separate left and right lengths for highs and lows, each defaulting to 10. The left and right lengths do not have to be equal.
| Setting | Meaning | Main consequence |
|---|---|---|
| High left length | Bars before a candidate high | Changes the historical comparison window |
| High right length | Bars after a candidate high | Determines the required detection delay |
| Low left length | Bars before a candidate low | Can differ from the high-side window |
| Low right length | Bars after a candidate low | Determines low-pivot detection delay |
TradingView's indicator description explains the surrounding-high and surrounding-low comparison. Increasing the window makes the local-extreme condition more selective; it does not prove that the resulting level will be more profitable to trade.
Read the price and timestamp separately
Suppose an illustrative candidate high occurs on bar 100 and the right length is three. It can only be evaluated as a pivot when bar 103 arrives, and a close-confirmed workflow must wait for that bar to finish. If a strategy enters at the old high on bar 100 because a later chart marks it there, the test uses information unavailable at that time.
Pineify's current generated labels are placed on the detection bar at the earlier pivot price. They are not shifted back to the candidate bar. Blue high labels and orange low labels are defaults with configurable colors. Another script may deliberately draw its label on the earlier pivot bar, so inspect the implementation before comparing screenshots.
The generated label condition does not itself require the detection bar to be closed. During that live bar, a changing high or low can affect the result. TradingView's repainting documentation distinguishes changing live values from plots drawn into the past. Waiting for a bar close and avoiding a historical plotting offset address different issues.
Choose lengths by the delay you can accept
A right length of 10 means 10 chart bars, not 10 minutes on every chart. On a 15-minute chart that is 150 minutes of bar duration; on a daily chart it is 10 daily bars, which need not equal 10 calendar days. Missing sessions and gaps also affect elapsed clock time.
Start by specifying the delay your proposed rule can tolerate. Then compare a small set of lengths while retaining a separate evaluation period. Do not select settings only because the finished chart has attractive turning points. No universal scalping, swing, or position-trading parameter range is established here.
A pivot is a historical reference, not an order
A recent pivot low can define a candidate support reference, and a recent pivot high can define candidate resistance. A retest can hold, break, or gap through the price. The marker does not reveal who traded there, establish institutional intent, or prove that other traders will defend it.
A breakout rule and a rejection rule need different definitions. For a breakout, specify whether a close must cross the last known high and whether the level expires. For a rejection, specify the permitted distance from the level and what price behavior counts as rejection. Neither rule is complete without exit and position-size logic.
This indicator differs from period-based pivot formulas. Those calculate levels from a selected period's OHLC data; swing pivots search for local extremes. Previous-period data are deliberate inputs to that other method, not defective or inherently stale data.
Add and verify the Pineify component
In the Visual Editor, search for Pivot Points High Low and check the applicable plan access. Configure the four lengths and label settings, generate the script, and inspect the exported source in TradingView. Open its Pine Editor using the Pine icon on the right toolbar and add the script to your chart.
Check one high and one low manually. Identify the candidate bar, count the right-side bars, and verify the detection-time label. If you use the output in an alert or strategy, confirm that the rule uses the value only after it becomes available. A fresh pivot output is an event; retaining the latest level for future retests requires explicit state in the strategy.
Backtest the information available at each bar
Test entries from the detection time onward and record the exact rule for keeping or replacing a level. Include commission, slippage, and an executable fill model. Compare trade count, average net trade, drawdown, and sensitivity to nearby lengths. No SPY win-rate improvement or AAPL/NVDA trading anecdote is documented here.
Why is a pivot label later than the turning point?
The calculation requires bars to the right. Pineify's current label placement uses the detection bar while displaying the earlier pivot price.
Do left and right lengths need to match?
No. Pineify exposes four separate lengths for high and low pivots. Changing the right length changes detection delay.
Is the latest pivot safe to use before the live bar closes?
Its status can change during the detection bar. If your rule requires confirmed information, explicitly enforce closed-bar timing and test the alert accordingly.