What is Confluence?
Confluence occurs when level, pattern, indicator, and session context agree on same trade idea.
Indian market context (NSE)
Reference levels: Nifty 50 at 24,300, Reliance Industries at ₹1,300, Bank Nifty futures at 55,000 (lot size 30). Examples below show how Confluence shows up on Indian index, equity, and futures books — update to live quotes in your journal.
Nifty 50 perspective
Confluence on Nifty (24,300): on the 15-minute chart, combine with session VWAP and 9:15–10:00 liquidity — index confluence signals misfire on expiry Tuesdays without volume confirmation.
Reliance Industries perspective
Confluence on Reliance at ₹1,300: daily vs hourly settings diverge around results and ex-dividend dates; note corporate events in journal when confluence readings spike.
Bank Nifty futures perspective
Confluence on Bank Nifty futures (55,000): first-hour signals differ from post-14:30 behaviour; avoid standalone entries when banking names lead the move.
How to validate
- Forward-test Confluence on paper or sim for two weeks after rule changes.
- Validate only on trades where Confluence settings matched the written playbook.
- Split results by trending vs range weeks on Nifty before trusting the signal.
- Require higher-timeframe bias agreement if that is part of your rule.
How to track in TradeLyser
- Add Confluence reading to trade entry notes (value + timeframe).
- Create tags: “Confluence aligned” / “Confluence ignored”.
- Monthly: filter trades by alignment tag and compare win rate and avg R.
- Screenshot chart context for mentor review on disputed trades.
Best practices
- Combine Confluence with higher-timeframe bias — not as a lone trigger.
- Avoid curve-fitting settings on less than three months of tagged data.
- Refresh playbook screenshots when changing Confluence parameters.
- Skip trading when Confluence conflicts with written risk limits.
Common pitfalls
- Treating Confluence as a guaranteed reversal signal.
- Optimising parameters on one bullish month only.
- Trading against higher-timeframe bias because Confluence “said so”.
- Failing to log when you overrode Confluence discretionally.
How to use this in TradeLyser
Checklist score 1–5 for confluence; review expectancy by score bucket monthly.
Related terms
Price action trading uses raw price structure — highs, lows, patterns, and context — over lagging indicators.
Support is a price area where demand previously stepped in, slowing or reversing declines. It is a zone — not a single tick — and can fail.
A setup is the specific pattern, level, and confirmation rule that must be present before entry.
Volume Weighted Average Price averages traded price weighted by volume from session open. Many intraday desks use it as fair-value reference.
FAQ
Minimum confluence score?
Define in plan — e.g. three of five factors.
Confluence curve fitting?
Too many filters on small sample — validate forward.
Start journaling with
TradeLyser
Connect your broker, tag strategies, and review performance with AI-assisted insights.