12 / 15 Advanced 10 min read

Confluence: turning components into a read.

Absorption is not a trade. A value area low is not a trade. This lesson is about how the pieces you have learned actually assemble — and where the free framework runs out.

ORDER FLOW ACADEMY 12 / 15

Start here

No single order flow pattern is a trade. Confluence is how the pieces become one.

Everything up to this point has been a component. Absorption is a component. A value area low is a component. CVD divergence is a component. Traded individually they are close to coin flips, and most people who lose money with order flow lose it by trading components.

The formula

Level + Context + Order Flow + Confirmation = Setup

Remove any one of the four and you do not have a setup. You have an opinion.


01 — The four components

What each one contributes

1 — LevelA location that matters, marked in advance: VAL, VAH, POC, an LVN, the overnight extreme, prior day high or low.
2 — ContextIs the market in balance or trending? What is the day type so far? What is the volatility regime? Is there news due?
3 — Order flowWhat is happening at the level right now: absorption, exhaustion, a failed auction, trapped participants.
4 — ConfirmationPrice actually doing something. Movement away from the level, aggression drying up on the losing side, structure shifting.

The order matters. Level and context come before you look at order flow, because they determine whether the order flow is worth looking at. Reading the tape without a level is how people end up trading noise for six hours and calling it order flow.


02 — A worked example

Building a read, one layer at a time

This is an educational example to show the reasoning structure. It is not a guaranteed setup, and the same sequence will fail plenty of times.

  1. Level — marked before the open Previous day's value area low sits at 4508. Overnight VAL is close to it at 4508.50. Two independent references clustering in the same two-point zone.
  2. Context — established by mid-morning The market has been in balance for two sessions. No high-impact economic releases scheduled for the next two hours. Volatility is normal. This is a market where responsive activity at range edges has been working.
  3. Price arrives ES sells off into 4508 in the late morning.
  4. Order flow — absorption The footprint shows roughly 1,500 contracts sold aggressively at 4508.00 across three bars, and the low does not extend. Someone is filling all of it.
  5. Order flow — CVD divergence Price made a marginally lower low than the earlier test, but cumulative delta made a higher low. Less net aggressive selling produced the second push down.
  6. Order flow — failed auction A brief probe two ticks below 4508 trades thin and price returns above within one bar. Whoever sold down there is now offside.
  7. Confirmation — the part people skip Aggressive selling stops arriving. Price lifts off the level with buyers taking the offer, and reclaims 4509.50 — back inside the prior balance.

Now you have something. Four independent categories of evidence agree, and the last one is price actually doing what the thesis requires.

Trading component 4 alone

"Absorption at the low, I'm long." No level context, no idea whether the market is trending, no confirmation. This is the version that loses money slowly.

Trading the confluence

A pre-marked level, in a market state where that level should matter, with live evidence someone is defending it, and price confirming before you commit.


03 — Being honest about it

What confluence does not do

Read carefully

  • It does not make the trade a certainty. Every element above can line up perfectly and the trade can still lose. Absorbers withdraw. News breaks unscheduled. That is normal and expected.
  • More confluence is not linearly better. Past a point you are just finding reasons to justify a decision you already made. Three strong, independent pieces of evidence beat nine correlated ones.
  • Confluence can be manufactured. If you look at enough indicators on enough timeframes, something will always agree with you. The discipline is defining what counts before price arrives.

Common mistake

Waiting for perfect confluence and never trading — or the opposite, calling any two things that vaguely agree "confluence" and trading everything.

Here is the useful discipline: write down what you require before the session starts. Level, market state, the specific order flow evidence, and the specific confirmation. If it shows up, you have a trade. If it does not, you do not. Deciding in the moment is how the bar moves.


04 — The gap this opens

Two things order flow genuinely cannot give you

You have now been handed a complete analytical framework. Two problems remain, and neither is solvable with more order flow data.

Consistency

Knowing the framework and applying it identically at 10:14 on a Tuesday when you are down on the day is a different skill. Execution, sizing, patience and review are their own discipline.

Environment

The absorption in the example above is a good read at 11:00 with nothing scheduled. It is a bad read ninety seconds before CPI. Order flow cannot see the calendar.

Key takeaways

  • Individual order flow patterns are components, not setups. Level + Context + Order Flow + Confirmation is the minimum.
  • Level and context come first — they decide whether the order flow is worth reading at all.
  • Confirmation is the step traders skip, and it is the one that separates a read from a trade.
  • Confluence improves probability. It never creates certainty, and every element can align on a losing trade.
  • Define your requirements before price arrives, or you will find confluence for whatever you already wanted to do.

◆ MertFutures Mentorship

You can learn the concepts for free. Applying them consistently is the hard part.

This lesson gives you the framework. What it cannot give you is someone watching your actual trades and telling you honestly where the reasoning broke — the structured methodology, live market application, trade reviews, execution feedback, risk management and accountability that turn a framework into a repeatable process.

Go beyond the fundamentals →

◆ Where this is going

A read is not yet a trade.

Next: turning this into an actual entry, with a defined invalidation and a plan for managing it.

Continue to Trade Execution →

Tracked locally in your browser — no account needed.