How to Build Custom Pine Script Alerts for FVG Detection

Written by TradingIM Editorial Team, reviewed by TradingIM Review Board · Updated August 02, 2026 · Editorial policy · For educational purposes only; not personalized investment advice. Past performance does not guarantee future results.

Table of Contents

1. Introduction
2. What Is Custom Pine Script Alerts for FVG Detection
3. Why Custom Pine Script Alerts for FVG Detection Matters for Traders and Investors
4. Core Concepts
5. Step-by-Step Guide
6. Practical Tips for Better Results
7. Common Mistakes to Avoid
8. Frequently Asked Questions
9. Conclusion

Introduction

On a crisp Tuesday morning, the EUR/USD pair opened with a 12‑pip gap between the 09:00 and 09:05 GMT bars. A day‑trader who had set up a Fair Value Gap (FVG) alert on a 5‑minute chart received a notification the moment price re‑entered the gap, allowing a quick long entry with a tight stop. The same trader missed the move on AAPL because the alert script was still firing on stale gaps, creating confusion and unnecessary order traffic.
Traders who rely on manual gap spotting often waste seconds scrolling through price action, and the delay can turn a high‑probability setup into a missed opportunity. Building a custom Pine Script alert that automatically flags fresh FVGs, filters out repeats, and visualizes the gap on‑chart removes that latency.
In this article you’ll learn how build a strong FVG detector, embed multi‑timeframe logic, and configure alertcondition statements that work reliably on both forex and equity markets.

What Is Custom Pine Script Alerts for FVG Detection?

A custom Pine Script alert is a user‑written condition that triggers TradingView’s native notification system when a specific price pattern occurs. For Fair Value Gaps, the pattern is a three‑bar structure where the high of bar 1 is lower than the low of bar 3, leaving an unfilled price corridor. The script marks that corridor with a box object and fires an alertcondition when price later touches the zone.
Example: On the 5‑minute EUR/USD chart, bars 12‑14 show a high of 1.0892, a low of 1.0885, and a low of 1.0900 respectively. The high of bar 12 (1.0892) is below the low of bar 14 (1.0900), creating a bullish FVG between 1.0892 and 1.0900. The script draws a translucent box over that range and sends an alert when the next candle’s low falls back into the box.

Why Custom Pine Script Alerts for FVG Detection Matters for Traders and Investors

Fair Value Gaps are popular among day traders, swing traders, and even algorithmic funds because they often act as liquidity pools where price returns to “fill” the gap. Ignoring them can leave a trader exposed to abrupt reversals or missed entries.
– Scalpers on the CME or forex market use FVGs to anticipate short‑term reversals, especially when the gap aligns with a market‑structure break.
– Swing traders on the S&P 500 or Nasdaq may wait for a daily‑resolution gap to fill before adding to a position, treating the gap as a natural support or resistance.
– Quant teams at hedge funds sometimes embed gap‑fill logic into execution algorithms to improve fill rates.
If you rely on manual spotting, you risk delayed reaction, higher slippage, and inconsistent risk placement. A custom alert standardizes detection, reduces cognitive load, and lets you focus on position sizing and stop placement.

Identifying Fair Value Gaps Using High‑Low Range Logic

The core of any FVG script is a three‑bar high‑low comparison. In Pine Script v5, you can capture the high of bar n‑2 and the low of bar n, then test whether the high is lower than the low.
Scenario: A swing trader on AAPL’s daily chart looks for bullish gaps after a downtrend. Bars 45‑47 show highs of 152.30, 151.80, and a low of 154.10. Because 152.30 = zoneHigh
if gapFilled
box.delete(gapBox)
gapBox := na
zoneHigh := na
zoneLow := na
`

Step 4 — Configure alertcondition() for Real‑Time Notifications

Set up an alert that triggers only when price re‑enters the open zone, not on every bar while the zone exists.
pine
priceInZone = close >= zoneLow and close cooldownBars
alert("FVG Re‑Entry", alert.freqonceperbarclose)

This simple filter reduces alert noise, especially on fast‑moving markets like GBP/JPY where price can bounce in and out of a gap repeatedly.

Practical Tips for Better Results

• Use a modest box width (e.g., right=bar_index+8) to keep the visual tidy on lower timeframes.
• Combine FVG alerts with a momentum filter such as the Relative Strength Index (RSI) > 55 for bullish gaps; this lowers false‑positive entries.
• Set the alert’s message to include the zone’s high and low; TradingView’s webhook payload can then feed an execution engine that places a stop just below the lower edge.
• Monitor liquidity; gaps on thinly traded pairs (e.g., exotic forex) may widen due to low depth, increasing slippage risk when you act on the alert.
• Back‑test the script using TradingView’s built‑in strategy tester. Record the number of alerts, win‑rate, and average drawdown before live deployment.
• Adjust the higher‑timeframe parameter based on the instrument’s typical volatility. For equities, a daily higher‑timeframe works; for forex, a 30‑minute higher‑timeframe may be more appropriate.
• Keep an eye on the CFTC’s daily position limits for futures contracts; excessive trading on FVG alerts can unintentionally breach those limits.

Common Mistakes to Avoid

• Relying on a single timeframe – gaps that form on a higher resolution will be missed, reducing signal quality.
• Leaving the box on after the gap fills – visual clutter leads to misreading and accidental re‑entries.
• Setting alerts to “Once per minute” – on volatile markets this can generate duplicate notifications for the same price touch.
• Ignoring spread costs – on forex, a 2‑pip spread can consume the entire gap on a 5‑pip FVG, making the trade unprofitable.
• Hard‑coding stop levels – always calculate stops relative to the gap’s edge to adapt to varying gap sizes.

How do I create a Pine Script alert for Fair Value Gaps?

Write a script that identifies a three‑bar high‑low mismatch, draws a box over the gap, and uses alertcondition() to fire when price re‑enters the box. Deploy the script on a chart, then add an alert from TradingView’s UI selecting the custom condition.

What is the best timeframe to detect FVGs in day trading?

Most day traders find 5‑minute or 15‑minute charts optimal because they capture intra‑session gaps while providing enough bars for reliable high‑low comparison. Pair the primary timeframe with a higher‑timeframe request.security() call to catch larger gaps that may influence short‑term price action.

Why do some FVG alerts fire repeatedly on the same bar?

If the alert condition does not include a “once per bar” filter or a cooldown, every tick that satisfies the price‑in‑zone test will generate a new alert. Adding ta.barssince() logic or setting the alert frequency to “Once per bar close” resolves the issue.

When should I reset an FVG alert after a price retest?

Reset the zone once price closes beyond the gap’s opposite edge (i.e., the gap is filled). In the script, delete the box and clear stored high/low values when close = zoneHigh for a bearish gap.

Can I combine FVG alerts with other indicator conditions?

Yes. Append additional boolean checks—such as rsi > 55 for bullish gaps or macd.histogram > 0—to the alertcondition() expression. This narrows the signal pool to setups that meet both gap and momentum criteria.

Is it safe to use FVG alerts for automated order execution?

Automation can improve speed, but it also amplifies execution risk. Ensure the alert payload includes explicit stop‑loss and position‑size parameters, and test the workflow in a simulated environment before live trading. Regulatory bodies like the CFTC monitor automated strategies for market‑impact violations, so maintain compliance with order‑size limits.

Conclusion

The most valuable lesson is that a well‑engineered Pine Script alert transforms a visual pattern into a disciplined, repeatable entry signal. Start by coding the three‑bar gap logic, layer in multi‑timeframe data, and finish with a clean alertcondition that respects cooldowns. Test on a range of instruments—EUR/USD, AAPL, QQQ—to confirm reliability, then integrate the alert into your trade‑execution workflow with proper stop placement.
Remember, no script guarantees profit; market conditions can change, spreads can widen, and gaps can disappear. Treat each alert as a hypothesis, size your position conservatively, and always respect your risk limits. Happy charting.

—. Read more in our related guide: How to Perform Daily Market Analysis Like a Professional Trader.

This article is for educational purposes only and does not constitute investment advice. Trading and investing carry risk of loss; never invest more than you can afford to lose.. Read more in our related guide: Equity Market Analysis: How to Evaluate Stocks Before Buying.

Last reviewed: August 2026