← All trading concepts Lesson · composite concepts

Confluence

Beginner to intermediate · every hourly zone on five instruments scored zero to four · 3 September 2026

The assumption underneath every trading checklist ever written: more reasons, better odds. It is testable, it has never really been tested, and when you test it the line does not go up.

In one sentence

Confluence is the practice of requiring several independent reasons to agree before taking a trade, on the assumption that each additional reason improves the odds.

What confluence claims

Do not take a trade for one reason. Wait until several line up — the level, the zone, the session, the round number, the higher timeframe — and take the trade where they meet. Every checklist ever written rests on this, and it feels unarguable. More reasons, better odds.

the zone round number prior day low big candle leaves the gap return rejected
One zone, four reasons to like it: a round number inside it, yesterday's low inside it, the discount half of the range, and a big candle that created it. The measurement asks whether the fourth reason helps.

It is also testable, and testing it needs a base zone that can be found by rule plus factors that are yes-or-no rather than matters of opinion. Fair value gaps are the base: there are thousands of them and their edges are arithmetic. The four factors are the ones a beginner is actually taught to look for.

Score every zone from zero to four, then compare hold rates. If confluence works, the line goes up.

Think of it like this

A restaurant has great reviews, a full dining room, an award in the window and a queue outside. Four reasons, all real.

They are also all the same reason wearing different hats — the place is popular. And popular restaurants are noisy, rushed and slow to seat you. Stacking four correlated signals does not multiply your information; it repeats it, while quietly selecting for the conditions those signals share.

What the data actually says

The raw answer is dramatic and it is partly an artefact, so both versions are printed here.

Instrument0 factors1 factor2 factors3 factorsChange
XAUUSD85.7%80.4%79.7%75.4%-10.3 pts
GBPUSD81.7%82.9%79.9%73.4%-8.3 pts
EURUSD82.7%76.9%82.8%73.9%-8.8 pts
US3076.5%79.7%78.1%80.3%+3.8 pts
NAS10081.6%79.7%77.2%66.7%-14.9 pts

What was counted: Every hourly fair value gap is scored against four factors a beginner is taught to look for: a round number inside the band, a prior-session high, low or close inside it, the band sitting in the discount half of the last 48 hours for a bullish gap (premium half for bearish), and a displacement candle having created it. Each is a yes or no. Held means price entered the band and was pushed a full band-height back the way it came before reaching the far edge — the identical rule used for the balanced price range.

These are the size-matched figures — only zones in the middle half by width, which is the comparison that survives the confound described below. Four-factor zones are omitted because once the sample is narrowed there are too few of them to report honestly.

On gold, size-matched: zones with no extra factors held 85.7%. Zones with three held 75.4%. Adding reasons was worth -10.3 points — in the wrong direction.

4 of the five instruments declined as factors were added. The exception was US30, which rose 3.8 points. Nowhere did the line climb the way a checklist assumes.

The confound, and why the honest number is a third of the raw one

The unmatched figures are far more dramatic: on gold, 86.2% at zero factors falling to 57.3% at 4. That is a -28.9-point collapse, and it would make a much better headline than the real result.

It is mostly about width. A wider band is more likely to contain a round number or yesterday's low simply by covering more prices — gold's four-factor zones had a median width of 75.3 pips against 9.1 for zero-factor ones. And a wider band faces a harder test, because both thresholds scale with it. So factor count and difficulty were entangled.

Restricting to the middle half of zones by width removes most of that. The decline survives at about a third of its raw size. That surviving third is the finding; the other two thirds were an artefact of the measurement, and publishing them as though they were real would have been the most impressive wrong thing on this site.

Why more reasons would make things worse

A decline still needs explaining, and the likely mechanism is not mysterious.

The four factors are not independent. Displacement candles leave big gaps; big gaps span more prices, so they catch round numbers and prior-session levels; and prices that move far enough to do all that are trending. Stacking these does not add four separate pieces of evidence — it selects for one condition, a fast directional market, and that is precisely the condition in which price runs through a zone instead of respecting it.

Look at the factors individually and the same story shows: each one on its own sits close to the others in hold rate. None is a strong filter alone, and combining them mostly compounds what they share.

How to use this

  1. Count reasons, but ask what they have in common. Four correlated reasons are one reason repeated. Four independent ones are genuinely worth more.
  2. Stop treating a long checklist as a licence to size up. There is no measured basis for it here, and the direction of the effect was negative on four instruments.
  3. Watch for the width trap in your own testing. If wider zones look better, check whether your definition of success got easier as the zone got wider. That single error was two thirds of the raw effect on this page.
  4. Prefer one good reason and a clear invalidation. A simple zone with a defined stop measured at least as well as an elaborate one.
  5. Keep the factors that pay elsewhere. Prior-session levels are excellent targets even where they add nothing as filters. A factor can be useful for one job and useless for another.
1 Find one zone you can define Edges by rule, not by eye — everything downstream depends on it 2 List the reasons you like it Round number, prior-session level, discount, displacement 3 Ask what they share Most of these co-occur because the market was moving fast 4 Do not scale risk with the count Three factors held 75.4% against 85.7% for none, size-matched 5 Spend the effort on invalidation instead Where the idea is wrong is worth more than how many reasons it is right
What to do with a stack of reasons, given that the stack did not improve the odds.

A worked example

Worked example

Dev finds a gold zone he loves. It was created by a huge candle, it holds the 3,840 round number, yesterday's low sits inside it, and it is in the discount half of the week's range. Four out of four. He takes triple his usual size.

What the data says about that zone. Nothing good and nothing terrible — but nothing better than a zone with none of those features. Once width is accounted for, the four-factor group was the weakest one measured on gold, and it had too few members to quote with confidence at all.

What went wrong in his thinking. He counted four reasons. He had one: gold moved fast and left a big imbalance. The round number and yesterday's low are inside the zone because the zone is wide, and it is wide because the candle was big.

What he should have done with the observation. Kept the zone, used his normal size, and used yesterday's low as a target on the way out rather than as a reason to get in.

The habit worth taking from this. Before adding a reason to a checklist, ask whether it can be true when the others are false. If it cannot, it is not a new reason.

Test your own checklist the same way

Score your setups zero to four on your own criteria before you know the outcome, then compare the hit rates by score. If your line is flat, every hour spent hunting for the fourth reason was spent on nothing.

Score your setups in the backtester →

Doing it on TradingView

  1. Pick one base setup you already trade and define its edges by a rule you could give someone else.
  2. Write your four criteria down before you start. Choosing them afterwards guarantees a result and teaches you nothing.
  3. Every time the setup appears, tag it on the chart with its score. TradingView's text tool is enough; the score must be recorded before the outcome is known.
  4. Record whether the zone held, using a fixed distance rather than a poke — decide in advance how far price must travel to count.
  5. After fifty, group by score. Also record zone width, so you can check whether your high-scoring zones are simply your widest ones.

Common mistakes

The drill
  1. Replay two months of hourly candles and mark every zone your base setup produces — every one, not the appealing ones.
  2. Score each zero to four on your own criteria, and write down its width, before scrolling forward.
  3. Follow each one and record held or broke by a fixed distance rule.
  4. Now group twice: by score, and by width. If the width grouping explains more than the score grouping does, you have found on your own data exactly what this page found on ours — and that is the most useful afternoon in this whole series.

Run the drill in the free backtester → Free, no sign-in to begin.

Questions people ask

Does confluence actually improve your win rate?

Not in this measurement. Matched for zone width, gold zones with no extra factors held 85.7% of the time and zones with three held 75.4% — a decline of 10.3 points. Four of the five instruments went the same way.

Why would more reasons make results worse?

Because the reasons are not independent. Big candles leave wide gaps, wide gaps catch round numbers and prior-session levels, and all of it happens in fast trending conditions — which is exactly when price runs through a zone rather than respecting it. Stacking correlated signals selects for one market condition instead of adding four pieces of evidence.

What was the size confound?

Wider zones catch more factors by covering more prices, and they also face a harder test since the thresholds scale with the band. Unmatched, gold fell 28.9 points; restricted to the middle half of zones by width it fell 10.3. Two thirds of the dramatic version was an artefact.

Does this mean I should trade every setup I see?

No. It means the number of reasons is not the thing to filter on. One zone you can define precisely, with a stop you can defend, measured at least as well as an elaborate one — and it will appear far more often.

Should I stop using round numbers and prior-day levels?

Not at all — but use them for the job they do. Prior-session levels are strong targets, which the Key Levels Calculator quantifies. Being useful as a target is a different claim from being useful as a filter.

How do I test my own checklist?

Write your criteria down first, score every setup before you know the outcome, record zone width alongside the score, then group by both. If width explains more of the variation than the score does, your checklist is measuring size rather than quality.

The last lesson, and the one that applies to all the others

Everything on this site is a reason to like a setup. This page says the way to use them is one at a time, well defined, with an invalidation you can state — not stacked into a checklist that mostly measures how fast the market was moving.

Open the free backtester →

Beginner exploration

Three questions to help you use this page

Open each answer for a plain-language way to read Confluence, test it carefully and decide what to explore next.

What does “Confluence” mean for a beginner?

This page focuses on “Confluence”.Every trading checklist assumes reasons stack. Scored zero to four across thousands of zones on five instruments and matched for zone width, hold rates fell as factors were added — 85.7% with none against 75.4% with three on gold.For “Confluence”, a beginner should identify what the learning guide measures, assumes or teaches before acting on its conclusion.Treat this page's account of “Confluence” as a learning reference rather than a prediction, signal or promise of future performance.

How should a beginner use this page to explore “Confluence”?

For “Confluence”, translate the idea into a definition you could apply the same way on two different charts.While exploring “Confluence”, work through one example slowly and record which inputs or observations determined the result.Keep your “Confluence” record honest: list the limitation or counterexample before using the concept in a trading plan.Before leaving “Confluence”, practise the definition on unseen history and review consistency before judging performance.

How can AI help explore “Confluence” responsibly?

Turn one idea from “Confluence” into a rule with explicit inputs, dates, costs and pass-or-fail conditions.Ask AI to expose missing assumptions in that “Confluence” test, not to guess the next market move.Use the FXAbsolute AI Backtesting Lab to inspect calculations connected to “Confluence” and the assumptions behind them.Reproduce any important “Confluence” result and reserve unseen data before deciding that an apparent pattern is useful.

Continue your exploration of Confluence with the beginner AI prompt guide, or inspect public calculations in the AI Backtesting Lab.