# Trading confluences, how to stack signals that actually add value

A practical guide to trading confluences: liquidity, fair value gaps, inverse FVGs, equal highs and lows, and break of structure — and how to filter them.

Source: https://queenbet138-a10.shop/trading-confluences-how/ · based on the channel [TJR](https://www.youtube.com/channel/UCGHBUXjDCeiIXNdKR0HUZnA) · Video: [Learn Every Trading Confluence In 18 Minutes](https://www.youtube.com/watch?v=TYbpk7WogHI) · 2026-10-18

![Trading confluences, how to stack signals that actually add value](https://queenbet138-a10.shop/trading-confluences-how/trading-confluences-how.webp)

## Key takeaways

- Confluence in trading means two or more independent signals pointing to the same decision — entry, target or invalidation.
- The five confluences most scalpers and intraday traders track are liquidity sweeps, fair value gaps (FVG), inverse FVGs, equal highs/lows and break of structure (BOS).
- More confluences is not automatically better: each added signal must be independent and testable, or it just adds confirmation bias.
- A confluence only becomes a rule when you can define the entry, the stop and the invalidation level before the trade.
- Risk management and journaling decide the outcome more than the number of confluences on a chart.

Trading confluences are two or more independent signals that point to the same decision — the same entry, the same target or the same invalidation level. A single signal tells you something might happen; a confluence tells you that several separate pieces of market structure agree, which is why traders use them to filter low-quality setups. TJR's walkthrough of the concept in "Learn Every Trading Confluence In 18 Minutes" is a compact map of the five most used ones, and the full framework behind it is laid out in the [TJR trading blueprint](https://go.tjrtrades.com/blueprint-nviugv1).

## What a trading confluence actually is

A confluence is a filter, not a signal generator. The idea is simple: if a liquidity sweep, a fair value gap and a break of structure all line up at the same price, the probability that the level matters rises — but only if those three things are genuinely independent observations rather than three names for the same candle. The most common mistake is counting overlapping concepts as separate confirmations and then sizing up on what is really one piece of evidence.

A useful test before you call something a confluence:

1. Can you describe the signal without referring to the other signals on the chart?
2. Does it have a defined price level attached to it?
3. Would the trade still make sense if that one signal were absent?

If the answer to the first question is no, you are not stacking confluences — you are describing one setup with several labels.

## The five core confluences traders stack

The confluences that come up most often in intraday and scalping models are liquidity, fair value gaps, inverse fair value gaps, equal highs and lows, and break of structure. Each one describes a different mechanic of price delivery, which is exactly why they can be combined: liquidity is about where orders rest, gaps are about imbalance, and structure is about direction.

- **Liquidity.** Clusters of stop orders above equal highs or below equal lows, plus session highs and lows. Price often trades into these pools before reversing, so a sweep is treated as a trigger rather than a target.
- **Fair value gap (FVG).** A three-candle imbalance where the wicks of candle one and candle three do not overlap. The unfilled space often acts as a magnet when price returns to it.
- **Inverse fair value gap.** A gap that failed to hold as support or resistance and now behaves the other way around — former support becomes resistance, and the gap becomes the entry zone on the retest.
- **Equal highs and equal lows.** Two or more highs or lows at nearly the same price. They mark obvious liquidity and are frequently run before a real move.
- **Break of structure (BOS).** A close beyond a prior swing high or low that confirms the direction of the current leg. BOS answers the question "which side am I trading?" while the other confluences answer "where?"

## How to combine confluences without over-filtering

Stacking every confluence you know usually produces no trades at all, so the practical approach is to pick one directional confluence and one locational confluence. Direction comes from structure — a break of structure on your trading timeframe. Location comes from liquidity, an FVG or an inverse FVG. That is a two-part model you can actually test, and it keeps the decision simple enough to execute in real time.

A workable sequence looks like this:

1. Mark the prior session high and low and any equal highs or lows — these are your liquidity pools.
2. Wait for a break of structure to establish which side of the market is in control.
3. Identify the FVG or inverse FVG created by the leg that broke structure.
4. Wait for price to return into that zone, ideally after sweeping a liquidity pool.
5. Define invalidation below the swing that created the structure break, and size the position from that distance.

Notice what is missing: no third and fourth confirmation. Adding a moving average, an oscillator and a higher-timeframe trend filter on top of a two-part model does not make it stronger — it makes it slower and harder to review. If you want to add a third confluence, add it only after the two-part version has been journaled over at least 50 trades.

## Why more confluences do not fix a weak strategy

The number of confluences on a chart has no relationship to the quality of the underlying plan. A trader with one clear rule and disciplined risk control will outperform a trader with six overlapping signals and no exit criteria, because the second trader cannot tell which signal actually produced the result. This is the point experienced viewers keep making: the value is in knowing which confluences fit your strategy, not in collecting all of them.

Three practical guardrails:

- **One model, one market, one session.** Test a single setup on a single instrument before combining anything.
- **Fixed risk per trade.** If the stop distance changes because a confluence moved, the position size should change, not the percentage of the account at risk.
- **Journal the confluence count.** Record how many signals were present on each trade. After a few dozen entries you will see whether the extra filters improved your average result or just reduced your trade count.

## Common questions traders ask about confluences

Most doubts around confluences are about timeframes, frequency and honesty of results. Beginners often ask which timeframe the signals should be read on; the answer is that structure and liquidity are marked on the timeframe you execute on, while higher-timeframe levels are treated as context rather than triggers. Mixing timeframes without a rule is the fastest way to justify any trade after the fact.

The second recurring theme is patience. Confluence-based models produce fewer entries than signal-chasing, and traders coming from indicator-heavy setups often feel the strategy is broken during quiet stretches. That is the filter working, not failing. The third theme is skepticism about results shown online — a healthy instinct, since screenshots of large percentage gains say nothing about sample size, drawdown or risk per trade. Treat any claimed performance, including numbers shared in community chats, as unverified and focus on your own logged data.

A related discipline question is how confluences interact with risk-reward. They do not replace it: a confluence improves the odds of the entry being at a meaningful level, but the trade still needs a defined stop and a realistic target. Traders who ask for more material on discipline and R:R are usually asking the right question, because those two variables determine the outcome more than the entry model does.

## Useful links

- [TJR trading blueprint](https://go.tjrtrades.com/blueprint-nviugv1) — the full system for building a repeatable process.
- [Indicators used daily](https://go.tjrtrades.com/indicators-6qf6zb4) — the toolset referenced in the video.
- [Funded account raffle](https://form.tjrtrades.com/funded-contest) — entry form for the giveaway.
- [Alpha Futures](https://app.alpha-futures.com/signup/TJR/) — funded account signup with the TJR discount.
- [Lucid Trading](https://lucidtrading.com/ref/TJR/) — discount on funded trading accounts.

## Bottom line

Confluences are a filtering tool: structure tells you which direction to trade, liquidity and fair value gaps tell you where, and everything else is optional. Pick two signals, define the invalidation level before entry, and journal the results until you know whether the model holds up on your instrument and session. TJR's 18-minute breakdown is a good checklist of the vocabulary, but the edge comes from testing one combination properly rather than collecting all five. If you want the structured version of that process, start with the [TJR blueprint](https://go.tjrtrades.com/blueprint-nviugv1) and treat every confluence as a hypothesis to verify, not a guarantee.

## Questions & answers

**How many confluences should I use per trade?**

Two is usually enough: one directional signal such as a break of structure and one locational signal such as a fair value gap or a liquidity sweep. Adding more filters reduces trade frequency and makes it harder to tell which signal is actually contributing to your results.

**What is the difference between a fair value gap and an inverse fair value gap?**

A fair value gap is a three-candle imbalance where the first and third candles' wicks do not overlap, and price often returns to fill it. An inverse fair value gap is a gap that failed to act as support or resistance and now behaves in the opposite role, which makes it useful as a retest entry zone.

**Do confluences work on any timeframe?**

They work on any timeframe as long as you are consistent. Mark structure and liquidity on the timeframe you execute on, and treat higher-timeframe levels as context rather than as entry triggers. Switching timeframes mid-trade is what turns a model into after-the-fact justification.

**Why does a confluence-based strategy produce so few trades?**

Because the model is designed to filter, not to fire constantly. Fewer setups is the expected outcome when you require structure and location to align, and the quiet stretches are where discipline matters more than the entry technique.