# Multi-Timeframe Analysis — How to Log Your Confluence in a Journal

> Multi-timeframe analysis (MTA) improves trade accuracy when applied correctly. Journaling MTA setups lets you measure whether your confluence approach is actually working.

**Tags:** multi-timeframe, confluence, technical-analysis, setup-tracking

**URL:** https://traderjournal.app/technical-indicators/multi-timeframe-analysis-how-to-log-confluence

---


# Multi-Timeframe Analysis — How to Log Your Confluence

Multi-timeframe analysis means checking higher timeframes for trend direction and context before entering on a lower timeframe signal. The theory is that trades aligned with the higher timeframe trend have better odds. Your journal tests whether this is true for you in practice.

## The Logging Framework for MTA Trades

Structure your trade notes around three timeframe levels:

**Higher timeframe (HTF) — context:**
- What is the trend on D1 or H4?
- Where are the major support/resistance levels?
- Is this a good area for your setup direction?

**Mid timeframe (MTF) — confirmation:**
- Is the pattern developing on H1 or H4 aligned with the HTF direction?
- Is there confluence at this level (previous structure, moving average, Fibonacci)?

**Entry timeframe (ETF) — trigger:**
- What specific signal on M15 or H1 triggers your entry?
- Does the trigger align with the higher timeframe context?

In your Trader Journal note, include brief answers to each level:

"HTF (D1): Bullish trend. Price pulled back to the D1 50 EMA + previous resistance turned support at 1.0780. MTF (H4): H4 showing bullish engulfing candle at the level. H4 trend also bullish. ETF (H1): H1 breakout above consolidation at 1.0795. Entry 1.0798, stop 1.0755, target 1.0875."

## Tags for MTA Quality

Create tags that capture how many confluences aligned:

- **mta-full** (all three timeframes aligned — strongest)
- **mta-partial** (two of three aligned)
- **mta-none** (entry taken without higher timeframe check)

Over time, filter by these tags. The expected result: **mta-full** trades have significantly better win rate and profit factor than **mta-none** trades.

If the data does not show this, either your MTA reading is inconsistent or the specific confluence criteria you are using are not actually predictive for your instruments.

## Common Multi-Timeframe Mistakes Visible in Journal Data

**Forcing confluence:** Traders sometimes see a higher timeframe bullish bias and enter a lower timeframe long even when the setup is weak. Tags like **forced-setup** or notes mentioning "marginal confluence" combined with the trade result reveal whether this pattern consistently loses.

**Wrong timeframe for entry:** If your strategy is H4-based but you filter down to M5 for entry, the M5 noise introduces entries at poor risk-reward. The trade note that records the entry timeframe and the resulting R multiple helps identify if your entry timeframe is working against you.

**Delayed entry:** MTA sometimes means waiting for multiple confirmations. By the time you have all three timeframes aligned, you may be entering late. Track the ratio between your actual entry and the original signal point.

## Measuring Whether MTA Actually Helps You

The definitive test is this comparison:

Filter trades by **mta-full** and check win rate + profit factor.
Filter trades by **mta-none** and check the same.

If the difference is 10+ percentage points in win rate, MTA is adding real value to your approach. If the difference is minimal, either you are not executing MTA correctly or your strategy's edge comes from something other than timeframe alignment.

Most traders who commit to this measurement for 60+ trades find that proper MTA adds 10-20% to their win rate. That is not a marginal improvement — on a 40% win rate strategy, moving to 55% win rate with the same risk-reward changes a losing strategy into a profitable one.