Which alert option should I choose for Pineify exports?

The Visual Editor generates alert() calls with a selected frequency and message. Add the exported script to your chart, open Create Alert, and choose the script with Any alert() function call. Exporting code does not activate a running TradingView alert.

What is the difference between alertcondition() and alert()?

In indicators, alertcondition() adds named entries to the alert menu. Its message is constant text but can contain supported TradingView placeholders. alert() supports runtime messages in indicators and strategies; its frequency is set in the code. Both require you to create a running alert in TradingView.

Does Once Per Bar Close prevent all repainting?

No. Waiting for the chart bar to close avoids acting on temporary values within that bar. It does not correct future-data leaks, unconfirmed higher-timeframe requests, or misleading historical plots. Check the signal calculations as well as the alert frequency.

Will editing my script update an existing alert?

No. A script alert runs a saved copy of the script, inputs, symbol, and timeframe. Delete and recreate it after changing that setup. Historical signal markers do not send retrospective notifications.

Can custom alerts send webhooks?

Yes, when webhook alerts are available on your TradingView account and two-factor authentication is enabled. Use a message matching the receiver schema and check the alert log for delivery status. A webhook notification does not confirm broker execution, and delivery can fail.

TradingView Custom Alerts Guide: Updated for 2026

TradingView Custom Alerts: How to Create Multi-Condition Alerts in 2026

TradingView supports native multi-condition alerts with up to five conditions on the same symbol, on Plus plans and above. All conditions must be true together. For OR groups or rules that remember an earlier event, use Pine Script. Pineify can generate supported AND/OR conditions and alert messages visually; you still create the running alert in TradingView.

Explore the Visual Alert Builder Compare Alert Types

TradingView Native Alerts vs Custom Pine Script Alerts

Choose the workflow that matches your rule, message, and account permissions.

Capability	Native Alerts	Manual Pine Script	Pineify Visual Editor
Condition logic	Up to five simultaneous conditions; same symbol; Plus or above	AND/OR groups and stateful rules within Pine limits	Nested AND/OR groups using supported inputs and indicator outputs
Message values	Supported TradingView placeholders	Placeholders in alertcondition(); runtime strings in alert()	Message placeholders converted into alert() runtime strings
Activation	Add conditions in the TradingView alert dialog	Add script to chart, then create a running alert	Export, add to chart, then select Any alert() function call
Limits still apply	Account technical-alert quota and eligible condition types	Account quota, Pine resource limits, and notification delivery	Pineify feature access plus the same TradingView runtime limits

alertcondition() vs alert(): Select the matching alert

The two functions expose different choices in Create Alert. Neither function activates a server-side alert by itself.

alertcondition() adds a named menu entry for an indicator. Declare it at global scope. Its constant message can include supported placeholders such as ticker, close, or a plotted value. A call in a strategy does not provide an alertcondition-based alert option.

alert() builds messages at runtime and sets frequency in code. Choose Any alert() function call when creating its alert. Pineify Visual Editor currently exports this form, with a selected trigger, frequency, and message. Strategy scripts normally calculate at bar close, which also constrains when their alert() calls can run.

See the official Pine alert documentation for function behavior and supported placeholders.

AND, OR, and conditions across different bars

A crossover is an event on one bar. RSI above 50 is a state that can remain true for several bars. Decide whether your rule requires them together or remembers the event for later.

Visual condition planning table
Group or rule	Condition rows	What qualifies
AND	EMA 20 crosses above EMA 50; RSI 14 above 50	Both are true on the same evaluated bar.
OR	EMA crossover; RSI crosses above 50	Either event is true. Both are not required.
Nested groups	(EMA crossover OR RSI crossover) AND close above EMA 200	Either event plus the trend filter.
Sequence	EMA crossover first; RSI confirmation on one of the next three bars	Remember the event, expire the window, and reset after a signal. A plain AND group cannot do this.

The sequence row is a specification for custom Pine logic, not a verified one-click Visual Editor preset. Define whether the crossover bar counts and whether a new crossover resets the window before implementing it.

Native multi-condition alert boundaries

Open Create Alert and use Add condition for each rule. A native multi-condition alert consumes one technical alert. Different timeframes are supported, with frequency based on the smallest interval. Strategies and scripts containing alert() are not supported in that native combination workflow. Pine scripts before version 4 with alertcondition() are also excluded. This page's combined code example contains alert(), so create it as a standalone script alert.

Source: TradingView multi-condition alerts. Checked October 16, 2026. Verify current entitlements on the TradingView plans page.

How to Add Custom Alerts on TradingView Step by Step

Build Your Custom Condition Script

Define your multi-indicator trigger rules. You can write raw Pine Script or use Pineify Visual Pine Script Editor to assemble conditions like EMA crossover + RSI filter visually.

Apply the Script to Your TradingView Chart

Open Pine Editor, paste the complete exported source, and click Add to chart. Review the plots, inputs, symbol, timeframe, and condition values before creating an alert.

Create the TradingView Custom Alert

Open Create Alert. For a Visual Editor export, select the script and Any alert() function call; the exported code controls frequency. For a named alertcondition() event, select that event and choose Once Per Bar Close in the dialog. Check expiration and notification settings.

Multi-Condition Custom Alert Code Pattern

This complete educational indicator checks an EMA crossover and RSI filter on the same confirmed chart bar. It demonstrates both alert APIs; it is not an exact Visual Editor export or a trading recommendation. Choose one alert path to avoid duplicate notifications from separately created alerts.

//@version=6
indicator("Confluence Custom Alert [Pineify]", overlay = true)

// Calculations
ema_fast = ta.ema(close, 20)
ema_slow = ta.ema(close, 50)
rsi_val = ta.rsi(close, 14)

plot(ema_fast, color = color.blue, title = "Fast EMA")
plot(ema_slow, color = color.orange, title = "Slow EMA")

// Confluence Condition: Golden Cross + RSI momentum confirmation
cross_up = ta.crossover(ema_fast, ema_slow)
long_condition = cross_up and rsi_val > 50 and barstate.isconfirmed

// Static Alert for TradingView Menu
alertcondition(long_condition, title = "Long Confluence Signal", message = "Bullish EMA crossover with RSI confirmation!")

// Dynamic Alert for Webhooks and Notifications
if long_condition
    alert('{"event":"ema_rsi_signal","ticker":"' + syminfo.ticker + '","price":' + str.tostring(close) + '}', alert.freq_once_per_bar_close)

Verify timing, snapshots, and delivery

Once Per Bar can fire before a candle closes. Once Per Bar Close waits for the closing calculation. The example gates both APIs with barstate.isconfirmed. Bar-close timing alone cannot repair repainting caused by other parts of a script, such as unconfirmed higher-timeframe data.

alert.freq_all permits every executed alert() call on a realtime bar, so repeated true conditions can produce repeated events. TradingView halts script alerts that trigger more than 15 times within three minutes. Check active status and runtime errors if notifications stop; see the official alert troubleshooting FAQ.

TradingView stores a snapshot of a script alert's code, inputs, symbol, and timeframe. Delete and recreate that alert after changing the setup. Alerts run on realtime bars; historical markers are useful for checking logic but do not demonstrate live notification delivery.

Suggested validation, not a reported live test: compare the EMA and RSI values at a qualifying close, check the alert log, then inspect the notification or receiver log. Confirm an AND rule stays silent when only one condition is true. Changing a frequency does not change an AND rule into a sequence rule.

For webhooks, enable two-factor authentication and send a body matching the receiver's expected schema. Valid JSON is sent as application/json. Delivery may fail; check Webhook status in the alert log. A notification is not proof of an executed trade. See TradingView webhook configuration.

Why Build Custom Alerts with Pineify Visual Editor

Multi-Indicator Logic

Combine supported indicator outputs and price data in nested condition groups. This does not grant access to the internals of protected third-party indicators.

Custom Alert Messages

Insert supported values into messages. If you write JSON, check its syntax and field names against your receiver; compatibility is not automatic.

Review the Export

Inspect the generated Pine Script, compile it in TradingView, and observe a live alert before relying on it. Pine resource and account limits still apply.

Create Custom TradingView Alerts Without Code

Configure supported conditions, choose an alert frequency, and review the generated script before creating the alert in TradingView.

Explore Pineify Visual Pine Editor

Frequently Asked Questions

Common questions about TradingView custom alerts, alert functions, and automated execution.

Yes. Native multi-condition alerts support up to five conditions on the same symbol with the Plus plan or above. All conditions must be true together. Use Pine Script when you need OR groups or rules that remember an earlier event.