when your TradingView indicator levels don't line up with the edgeful report page, it's almost always one of 3 things — the wrong session/timezone, the wrong variant for your asset, or the wrong timeframe. get these 3 in sync and the levels match.

the rule underneath all of it: the indicator and the report have to be anchored to the same session, in the same timezone. the session is what every level is built around — change it, and you're measuring a different thing.

every edgeful indicator exposes a timezone input and session start / end inputs. set them to match the session you've selected on the report. here are the exact values for the built-in sessions:

a mismatched timezone is the single most common reason levels look off — if your edgeful session is London (Europe/London) but your indicator is still on America/New_York, the boxes will sit hours away from where they should. the market sessions indicator is the easy way to check: it draws each session as a box so you can see at a glance whether your timezone is right.

short answer: they're the same window, written in two different timezones — so neither is "wrong." for the current built-in London session, set Europe/London, 8:00 AM - 4:00 PM.

here's why it's confusing. edgeful's built-in London session is now anchored to London local time: 8:00 AM - 4:00 PM Europe/London. that exact same window, expressed in New York time, is about 3:00 AM - 11:00 AM ET — which is how the London session used to be defined back when it was anchored to Eastern. so if you've seen both sets of numbers floating around, they're describing the same hours from two different clocks, not two different sessions.

anchoring to Europe/London is the better default because it tracks the real London open through daylight-saving shifts on both sides of the Atlantic — the session stays put relative to the London market instead of drifting an hour twice a year. set your indicator to Europe/London, 8:00 - 4:00 to match the current report. if you specifically want the legacy ET-anchored version (3:00 - 11:00 New York time), build it as a custom session — see want the old Eastern-based behavior? below.

the Asian session is the one to slow down on, because it runs overnight relative to New York — Tokyo's hours fall in the ET evening and early morning, so the session crosses midnight ET.

two things follow from that. first, futures roll to a new trading day at 6:00 PM ET, so a given day's Asian session may have started the evening before in ET — edgeful labels it by the trading day it belongs to, not the calendar date it opened on. second, any session that crosses midnight needs the overnight toggle turned on, on both the report and the indicator.

to match it on TradingView: set the indicator's timezone to Asia/Tokyo, enter the same start / end as your report's Asian session, and turn the overnight setting on. if the dates look shifted by a day, that's the 6pm rollover doing its job — not a mismatch.

this is the one that catches most futures traders. some reports ship in two flavors, and picking the wrong one is the #1 reason an indicator's data doesn't match the report page:

mixing the two — a standard indicator against a by-session report, or vice versa — is exactly when the numbers stop agreeing.

put the indicator on the timeframe the report runs on. most edgeful reports run on the 1-hour or daily timeframe. opening candle continuation and IB are tied to the first hour (9:30 - 10:30 AM ET on NY).

one definition worth nailing down: the opening candle is the first candle of the session — on NY that's the candle that opens at 9:30 AM ET, not 9:15. measured from there, the ORB window is the first 15 minutes (9:30 - 9:45) and IB is the first hour (9:30 - 10:30). if your indicator is anchored to 9:15, that's usually the mismatch.

one gotcha worth flagging: don't use a 60-minute candle to capture the NY open. 60-minute candles start and end on the hour, so the first one runs 10:00 - 11:00, not 9:30 - 10:30 — it misses the open entirely. use a 30-minute candle to capture the first 30 minutes cleanly. you can keep your own trading timeframe on the chart and let the indicator plot the higher-timeframe levels on top.

if you trade outside the default 9:30 AM ET start — London open, the Asian session, or custom prop-firm hours — set the session start and end once on the indicator, then save it as a chart template so it loads that way every time.

make sure the custom session on your report and the custom session on your indicator use the same timezone and the same start / end. moving the end time even 15 minutes shifts the reference close — so they have to be identical on both sides.

the built-in London and Asian sessions used to be anchored to Eastern time. if you want to keep trading them that way, recreate them as custom sessions on the report and match them on the indicator:

then set your TradingView indicator to the same UTC-4 timezone and the same window.

run through all 3 checks in order:

if all 3 match and it's still off, it's usually access-related — the indicator may need a refresh after a TradingView update. see the TradingView indicators access article below.