Skip to main content

non-US markets and international TradingView setup

how to use edgeful algos and reports with non-US markets like DAX, forex, and crypto — including which tickers work, timezone and session considerations, and TradingView setup nuances.

Written by Brad

which markets edgeful supports

edgeful reports and algos work with:

  • US futures — ES, NQ, YM, RTY, CL, GC, MES, MNQ, MBT, and more

  • stocks and ETFs — SPY, QQQ, AAPL, and any ticker on major US exchanges

  • forex — EUR/USD, GBP/USD, and other major pairs (reports and manual trading; automation is futures only)

  • crypto — BTC, ETH, and other pairs (reports and manual trading; automation is futures only)

  • international futures — DAX and other non-US contracts (with some caveats)

edgeful has 150+ reports across futures, stocks, forex, and crypto. algo automation is futures only: it routes to Tradovate, NinjaTrader, or ProjectX futures accounts. and there are important setup differences depending on what you're trading.

the timezone factor

edgeful reports and algos default to the NY session. on the reports you can switch to London, Asia, Daily (6pm–5pm ET), or your own custom session, but on the default NY session:

  • the "session open" is 9:30 AM ET

  • the "previous session close" is based on the NY close

  • gap calculations, IB ranges, and ORB timing all anchor to Eastern Time

if you're trading from a different timezone, this doesn't change anything about how the data works — but it changes when things happen for you.

example: if you're in Europe and trading DAX with edgeful's ORB algo, the ORB window starts at 9:30 AM ET (3:30 PM CET). that's the NY session ORB — not the Frankfurt open. make sure this aligns with how you actually want to trade.

you can customize session times in the algo indicator settings on TradingView. if you want the ORB to reference a different opening window (say, the Frankfurt open at 9:00 AM CET), adjust the time inputs on the indicator accordingly.

algo-specific considerations

ORB (opening range breakout)

works on any ticker. the opening range window is fully customizable — 1-minute, 5-minute, 15-minute, or any other interval. default is based on the NY session (9:30 AM ET), but you can change the start time in the indicator settings.

for non-US markets: adjust the ORB start time to match the session open you're targeting. if you're trading DAX and want to capture the European session open, set it to your preferred local open time.

IB (initial balance)

by default, the IB is the first hour of the NY session — 9:30 to 10:30 AM ET. the IB algo can also run on London, and the IB reports let you change both the session and the IB duration.

for non-US markets: the IB concept still applies if your market has a defined session open. the IB reports let you pick the session, but if your instrument isn't in the report library, you're using the indicator on your chart (which you can customize) — not pre-calculated report data.

engulfing

pattern-based — works on any ticker, any timeframe. no session dependency. this is the most straightforward algo to use on non-US markets.

TradingView setup for non-US tickers

contract symbols

TradingView uses exchange-specific symbols. a few things to watch:

  • DAX futures — use the correct exchange prefix. the symbol format varies depending on your data provider (e.g., FDAX1! for continuous on EUREX)

  • forex — use standard pairs (EURUSD, GBPUSD). make sure your TradingView data subscription covers forex if it's not included in your plan

  • crypto — use exchange-specific symbols (BINANCE:BTCUSDT, COINBASE:BTCUSD, etc.)

for backtesting, use continuous contracts (the "1!" suffix) to get uninterrupted historical data. for live alerts, you may need the specific front-month contract — check your broker's requirements.

data subscriptions

TradingView charges separately for real-time data on different exchanges. if you're trading DAX, you'll need EUREX data. if you're trading forex, check whether your TradingView plan includes it or requires an add-on.

this is separate from edgeful — it's a TradingView billing item. if you already have real-time data through your broker (NinjaTrader, Tradovate), you still need TradingView data separately for the alerts to work correctly.

chart timezone

set your TradingView chart timezone to match the session you're trading. this doesn't change the data — but it makes the chart easier to read and ensures your indicator time settings make sense visually.

go to TradingView chart settings → timezone → select your preferred timezone (or use "exchange" to match the instrument's native timezone).

broker compatibility for non-US markets

the supported brokers for edgeful automation are:

  • Tradovate — primarily US futures. some international products available depending on your account type

  • NinjaTrader (brokerage) — US futures and some international contracts

  • ProjectX (Topstep) — US futures only

if your broker doesn't support edgeful automation for the specific non-US instrument you want to trade, you can still use the algo indicators on TradingView manually. set up alerts for entries, TP, and SL — then execute the trades yourself at your broker. you won't get automated execution, but you'll get the algo signals.

Rithmic-based prop firms (Apex Trader Funding, etc.) do not support TradingView webhook automation. this applies to both US and non-US instruments.

what's not supported (yet)

  • pre-calculated report data for non-US instruments — edgeful's report library on the website is focused on US futures, stocks, and ETFs. you won't find a DAX gap fill report page with historical stats. the algos and indicators work on any TradingView chart, but the website report data doesn't cover every international instrument.

  • sessions on instruments outside the library — reports offer NY, London, Asia, Daily, and custom sessions, but only for instruments in the report library. for anything else, you'll read the levels off your chart.

these are product-level limitations, not bugs. as edgeful expands coverage, more international data will be added to the report library.

Did this answer your question?