the 3 things that have to match
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.
set the right session and timezone
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:
session | timezone to set | session window | IB / ORB windows |
NY | America/New_York | 9:30 AM - 4:00 PM | IB 9:30 - 10:30 · ORB 9:30 - 9:45 |
London | Europe/London | 8:00 AM - 4:00 PM | IB 8:00 - 9:00 · ORB 8:00 - 8:15 |
Asian | Asia/Tokyo (its local timezone) | local market hours | first 60 min / first 15 min, local |
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.
use the right variant for your asset
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:
stocks and ETFs — use the standard versions (gap fill, previous day's range, pivot points). those markets close at 4 PM ET, so the calendar day and the session day are effectively the same
futures, forex, crypto — use the by session versions (gap fill by session, previous day's range by session, pivot points by session, fibonacci by session). these use the session close instead of the calendar-day close
mixing the two — a standard indicator against a by-session report, or vice versa — is exactly when the numbers stop agreeing.
match the timeframe
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 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.
customize a non-standard session
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.
want the old Eastern-based behavior?
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:
old London — timezone UTC-4 (New York), 3:00 AM - 11:00 AM. name it "London NY"
old Asian — timezone UTC-4 (New York), 7:00 PM - 4:00 AM, overnight toggle on. name it "Asia NY"
then set your TradingView indicator to the same UTC-4 timezone and the same window.
if the data still doesn't match
run through all 3 checks in order:
the report's session dropdown matches the indicator's session and timezone
the report's timeframe matches what the indicator is plotting
the variant is right — by session for futures/forex/crypto, standard for stocks/ETFs
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.