How to Set Ichimoku Alerts: TK Cross and Cloud Alignment
Configure Ichimoku line-cross alerts and check displaced cloud alignment, confirmation timing and saved settings before relying on notifications.
Setup Steps
Record all Ichimoku settings
Add the built-in Ichimoku Cloud and record conversion, base, span-B and displacement inputs. The familiar 9/26/52 lengths are a starting convention. The cloud and lagging span are displaced drawings, so chart position and calculation time must be distinguished.
Start with the undisplaced TK comparison
Open Create Alert and inspect the available Ichimoku plots or named conditions. For a conversion/base-line cross, compare the Conversion Line against the Base Line in the required direction. Use a documented custom condition if your chosen implementation does not expose that comparison; do not assume every variant has identical menu labels.
Define which cloud you mean
For price-versus-cloud rules, state whether the cloud is the one displayed at the current price bar or the newly computed cloud projected forward. Those values can differ. For Chikou comparisons, state which historical price bar is being compared. Review the implementation before treating a displaced visual intersection as a signal available earlier.
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.
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.
| Condition | Signal | Notes |
|---|---|---|
| Conversion crosses above Base | Change in the two midpoint lines | The cloud context is a separate filter and does not confer a verified win rate. |
| Conversion crosses below Base | Opposite midpoint ordering change | Confirm the selected plots and timeframe rather than using a visual line intersection alone. |
| Price crosses the cloud displayed at the current bar | Price moved beyond an aligned cloud boundary | Requires correct displacement alignment; a generic comparison with a new leading span can describe another event. |
| New leading spans change ordering | Projected cloud changes sign | A projected cloud is calculated from known history, not future price data or a prediction of volatility. |
Parameters to record and evaluate
Examples describe the configuration, not validated trading settings.
| Parameter | Starting value or requirement | Description |
|---|---|---|
| Conversion / Base lengths | 9 / 26, starting convention | Lookback midpoints use highs and lows; these are not moving averages of closing price. |
| Span-B length | 52, starting convention | Controls the range midpoint used by one cloud boundary, not a guaranteed support strength. |
| Displacement | Record the active setting | Check the implementation’s plotting offset and historical indexing when verifying cloud conditions. |
| Confirmation | State explicitly | Completed chart bars and completed higher-timeframe bars are separate requirements. |
FAQ
Alert Setup FAQ
Are cloud and Chikou alerts available under fixed menu names?
Do changes to Ichimoku settings update an existing alert?
Does a green cloud guarantee a bullish trade?
Can Bar Replay test the notification?
Can I forward an alert to Telegram?
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