Alert Setup Guide

How to Set Parabolic SAR Alerts: Direction and Flip Checks

Set Parabolic SAR crossing alerts with the operands in the correct order, distinguish Start from Increment, and test configuration on new data.

Setup Steps

1

Record Start, Increment and Maximum

Add Parabolic SAR and inspect its three acceleration inputs. The documented defaults are Start 0.02, Increment 0.02 and Maximum 0.20. Start is an acceleration factor, not a zero-tick offset. Record the indicator timeframe as well.

2

Read the crossing operands in order

Open Create Alert and inspect the selected series. Price crossing above SAR is the bullish ordering change; price crossing below SAR is the bearish one. If SAR is the first operand, the directions reverse: SAR crossing below price describes the bullish ordering change. Verify the series labels before saving.

3

Decide whether a plot cross represents your flip rule

Inspect a few bars where the SAR dots change sides and compare the intended condition. A custom implementation may expose a directional state-change condition directly. Composite rules such as a flip plus volume or repeated flips require that logic explicitly; they do not inherit a proven success rate.

4

Save the alert context

Choose the frequency, expiry and notification method in your account. For a rule defined on completed candles, select Once Per Bar Close where available. Record the symbol, timeframe and inputs. Recreate the alert after changing the script or its inputs; the running alert retains its saved configuration.

5

Verify delivery on new market data

Treat chart inspection and delivery as separate checks. Bar Replay can help inspect historical plots, but server alerts continue using live data. Check a new event against the alert log, then check the chosen notification channel. This is a test procedure, not a claim that delivery or investment performance has been tested here.

Alert Conditions Reference

Conditions to define and verify for the selected indicator.

Feature comparison table: Signal vs Notes
ConditionSignalNotes
Price crosses above SARBullish price/SAR orderingEquivalent direction is SAR crossing below price; do not reverse these operands.
Price crosses below SARBearish price/SAR orderingEquivalent direction is SAR crossing above price.
Repeated changes in SAR sideThe selected rule is switching frequentlyThis can occur in a range. It does not predict the next breakout.
SAR flip plus another conditionA separately defined combined ruleSpecify both conditions and their timing; a filter may remove profitable and losing events.

Parameters to record and evaluate

Examples describe the configuration, not validated trading settings.

Feature comparison table: Starting value or requirement vs Description
ParameterStarting value or requirementDescription
Start0.02Initial acceleration factor, not a price offset.
Increment0.02Increase applied as new extreme points occur. Increasing it does not slow acceleration.
Maximum0.20Caps the acceleration factor; it is not a maximum loss limit.
Chart / indicator timeframeRecord bothUse matching calculation context when checking the dot positions and alert log.

FAQ

Alert Setup FAQ

Which direction should the crossing alert use?
It depends on the first operand. Price above SAR is bullish ordering; SAR above price is bearish ordering. Write the full comparison rather than relying on the word “up” alone.
Does increasing Increment reduce sensitivity?
No. It increases how quickly the acceleration factor rises when the algorithm records new extremes, subject to the maximum. Test the resulting behavior instead of assuming fewer false signals.
Are SAR settings a stop-loss guarantee?
No. A calculated line is not an executed order, and gaps or slippage can move an actual fill beyond a selected level.
Can I test alert delivery by replaying a past flip?
No. Inspect past dots for calculation behavior, then check live alert logs and notifications separately.
How should I handle frequent flips?
First verify the intended timeframe and rule. Then compare any proposed filter with fixed parameters and later data; do not equate a lower event count with profitability.

Need a custom alert rule?

Describe the condition in Pineify’s coding agent, then review the generated Pine Script and test its timing and delivery in TradingView.

Explore Pine Script coding