Data Feed and Connection Setup: The Pre-Market Checklist Every NinjaTrader Bot Needs
You've built a bot portfolio. You've run the backtests, picked your position sizes, and worked out your automated risk management. None of it matters if NinjaTrader can't hold a stable connection to your funded account when the bell rings.
Connection setup gets treated as a five-minute formality — plug in the data feed, click connect, move on. It's the part of going live that actually causes the most silent failures: a bot that stops sending orders mid-session, a feed that reconnects with a gap in the data, or an ATI bridge that never linked to your broker in the first place. Here's the checklist to run before a bot ever touches a live or funded account.
Data feed vs. broker connection — know which is which
NinjaTrader separates market data from order execution, and conflating the two is where most setup mistakes start. Your data feed (Kinetick, Rithmic, or a CQG feed depending on your funded account firm) delivers the price ticks your bots trade on. Your brokerage/funded-account connection is the separate link that actually routes orders. You can have a perfect data feed and a dead order connection — the charts update, the bot fires a signal, and nothing happens on the account.
Check both independently under Control Center > Connections. Each one shows its own status light. Green on the data feed and red on the brokerage connection is a configuration most new funded traders don't catch until a bot misses a fill.
The pre-market connection checklist
- Confirm both connections are green — data feed and brokerage/ATI, separately, not just "NinjaTrader is open."
- Check the account is mapped correctly — under Connections, verify the funded account number shown matches the one you intend to trade. A bot pointed at a demo or the wrong sub-account trades real signals into nothing.
- Watch for a reconnect during the session, not just at startup. A feed that drops and silently reconnects can hand a bot a gap in tick data — it may see a false breakout or miss the one that actually happened.
- Verify time sync. NinjaTrader's session times and your firm's daily loss cutoff both depend on your system clock being accurate. A few minutes of drift can make a bot think the session is still open when the firm has already locked the account.
- Test with Sim before funded capital — if you haven't already worked through the connection modes themselves, see Sim101 vs. Live before pointing a bot at a real account.
Why this matters more once bots are running unattended
A discretionary trader watching the screen notices a frozen chart or a stale quote in seconds. A bot doesn't — it keeps evaluating whatever data it's handed, connected or not, until something forces an error. That's the same blind spot automated risk management is built to catch on the position side, but it can't catch a connection that silently degrades before a trade is ever placed. The fix isn't more automation — it's a two-minute manual check before the open, every day, that costs nothing and prevents the failures that are hardest to diagnose after the fact.
Where this fits with your bot lineup
If you're running strategies from the no-coding bot lineup across multiple funded accounts, each account needs its own verified connection — the checklist above runs once per account, not once per NinjaTrader instance. It's a small habit that sits underneath everything else your bots are supposed to automate, and it's the one piece of "setup" that never stops mattering, no matter how long you've been running a given strategy.
