MetaTrader 4 feeds
Where a MetaTrader 4 server gets its prices.
An MT4 symbol can receive prices through several server-side routes. Knowing which route owns it is the first step in diagnosing or replacing a feed.
- Feed modules connect an external source to the trade server.
- Gateways and feed modules have different operational roles.
- Mappings must be explicit when source and platform names differ.
Find the owning route
Before changing a symbol, establish whether its quotes come from a feed, gateway, bridge, API integration, or another symbol.
Rights still matter
A compatible connector does not include provider credentials, exchange permissions, or redistribution rights.
Map once
Keep provider names, MT4 names, precision, and pricing adjustments in one controlled mapping.
On this page
The source name visible to traders is not enough to identify the path a price took. On an MT4 server, quotes can arrive from a conventional data-feed module, a gateway or bridge, a server-side integration, or an administrative tool. A symbol can also be configured to follow another symbol’s quote stream.
Feed modules
A feed module adapts a provider’s protocol to the server. Each configured instance normally has its own connection details, credentials, symbol selection, and retry behavior. Several enabled feeds can run at the same time, allowing the server to choose among sources that cover the same symbol.
The module is only the adapter. The brokerage still needs the provider account, permission to use the data, the correct instrument entitlement, and an operational contact for the source.
Gateways and bridges
A gateway usually carries a broader trading relationship than a price-only feed. Depending on the setup, it may provide quotes as part of order routing or connect one trading environment to another.
Do not treat a gateway and a data feed as interchangeable just because both can produce Bid and Ask. Establish:
- which component is authoritative for the symbol;
- how source priority is resolved;
- where symbol renaming and price adjustments happen; and
- whether changing the route also changes execution behavior.
Server APIs, plugins, and controlled publishing
Authorized server-side software can publish ticks without using a traditional vendor feed module. This is a common integration point for a managed pricing service or an existing bridge.
The operational questions are the same: authentication, symbol mapping, timestamp handling, reconnect behavior, monitoring, and a safe way to stop publishing during maintenance.
Manual dealer quotes are useful for controlled operations, but they are not a resilience plan and should be clearly distinguishable in the audit trail.
Symbol aliases need special care
When the provider’s name and the platform’s name differ, the mapping may live in the feed, a gateway, an upstream bridge, or the MT4 symbol configuration. Avoid maintaining the same transformation in several places.
A reviewable mapping should record:
Swipe or scroll horizontally to see all columns
| Item | Example |
|---|---|
| Provider symbol | XAU/USD |
| MT4 symbol | XAUUSD |
| Digits and point size | Platform specification |
| Bid/Ask adjustment | Upstream policy or gateway rule |
| Trading and quote sessions | MT4 symbol schedule |
Choose the route deliberately
For each symbol group, write down the preferred source, backup source, integration owner, mapping owner, and expected behavior when quotes stop. Then verify the result with a normal tick, a reconnect, and a source outage.
Feed settings cover the connection itself. Backup feeds cover priority and switching. If several sources must be compared or combined before MT4 receives a price, use an upstream pricing engine rather than duplicating that logic in platform mappings.
A feed shaped around your setup
Identify the MT4 entry point.
Tell us how prices reach your server today and which symbols need to move. We’ll set out a practical integration path in writing.