MetaTrader 4 feeds
MetaTrader 4 data feed settings that matter.
An MT4 feed dialog mixes provider details, symbol selection, and connection recovery. Review those as separate operational decisions.
- Connection settings identify one provider session.
- Symbol masks decide which instruments the feed may supply.
- Reconnect timing is not the same as backup switching.
Scope the symbols
A broad or invalid mask can expose more provider symbols than intended, so verify the effective list after saving.
Separate the clocks
Connection retry, inactivity detection, and source failover answer different questions.
Verify after change
Check connection status, a sample of symbols, source priority, and the journal rather than relying on a successful save.
On this page
An MT4 data-feed configuration answers three different questions: where to connect, which symbols to accept, and how to recover the connection. Keeping those decisions separate makes the configuration easier to review.
Connection identity
Record the module, provider endpoint, account, and environment together. A production feed and a test feed can look similar while carrying different symbol sets, permissions, or prices.
Credentials should be stored and rotated through the brokerage’s normal access process. Screenshots and exported configurations should not expose them.
Symbol selection
The feed’s symbol or keyword rules limit which provider instruments it can present to the server. Wildcards and exclusions are convenient, but they also make unintended expansion easy when a provider adds symbols.
After every rule change:
- inspect the effective symbols rather than only the mask;
- check one included symbol and one excluded symbol;
- confirm the platform name, digits, and point size; and
- verify that the backup feed covers the same intended set.
Renaming is better handled in one controlled mapping layer. If a provider calls an instrument EUR/USD and MT4 calls it EURUSD, decide whether the feed, gateway, bridge, or upstream pricing service owns that transformation.
Connection recovery
Three clocks are often confused:
Swipe or scroll horizontally to see all columns
| Mechanism | Purpose |
|---|---|
| Inactivity detection | Decides when the current connection is no longer healthy |
| Reconnect and retry timing | Controls attempts to restore that feed |
| Feeder switch timeout | Controls when MT4 may use a lower-priority source after quotes stop |
Changing a reconnect value does not necessarily make source failover faster. It can instead make one broken connection retry more or less aggressively. Review it together with the server-wide switch policy and the provider’s normal quote cadence.
Priority is outside the individual connection
The position of a feed in the server’s feed list determines its relative priority for overlapping symbols. Moving an entry can affect many symbols at once and can restart feed activity, so treat reordering as a production change.
See MT4 backup feeds for the complete failover review.
A safe change checklist
- Export or record the current configuration without secrets.
- Confirm the module and server build supported by the provider.
- Make the smallest possible change in a test environment first.
- Check connection status and recent journal messages.
- Compare several live symbols with the intended source.
- Exercise a reconnect and, when priority changes, a controlled failover.
- Confirm that quote sessions and symbol filters have not hidden the result.
Feed settings establish transport and scope. Pricing rules—aggregation, markups, spread construction, and cross-source protection—are easier to govern in a client-specific pricing engine .
A feed shaped around your setup
Review the feed configuration before the change window.
Send the intended symbols, connection model, and backup behavior. We’ll reply with the questions that should be settled before rollout.