A Telegram channel can call its instrument GOLD while the terminal lists XAUUSD with a suffix. That naming problem is easy to notice. The more expensive mistake is assuming that a lot, a pip or a stop distance means the same thing at every destination.
Treat an XAUUSD signal as a set of prices and an intended instrument, then read the destination's contract specification. Confirm the symbol, contract size, minimum volume, volume step and trading session before deciding how much to send. Gold's familiarity does not make the broker's specification optional.
In this guide
Match the contract before the spelling
A mapping connects a source label to a destination symbol; it does not establish economic equivalence by itself. Spot-style gold CFDs and exchange-traded gold futures have different contract and expiry conventions. Substituting one for the other requires more than replacing the ticker in a text box.
Read the broker's instrument specification in the platform and record its units. The mapping guide separates name translation from instrument selection, while the MT5 guide covers the terminal checks needed to reach that destination.
Calculate with stated assumptions
Consider an illustrative USD-denominated gold CFD with a contract size of 100 ounces per lot and a permitted volume of 0.10 lots. A price move of $1 per ounce changes the position value by $10 before costs. A $5 distance between entry and stop therefore represents $50 of price risk under these assumptions, before slippage or fees.
That example is arithmetic, not a statement about your broker. A different contract size, account currency or volume changes the result, and a stop order does not guarantee its trigger price as the final fill. Use the accepted size and actual execution price when reconciling the trade.
| Field | Why it matters |
|---|---|
| Contract size | Converts lots into underlying exposure |
| Tick size | Defines allowed price increments |
| Volume step | Determines which quantities can be submitted |
| Stop restrictions | May prevent a requested protective level |
| Bid and Ask | Explain spread and side-dependent execution |
Retire the unexplained pip
Gold channels often quote “pips” without defining the increment behind the word. Two reports can describe the same price move with different pip totals. Keep entry, exit and stop in explicit price units until the source convention is established.
A terminal's displayed decimal digits do not alone establish the monetary value of a tick or the provider's pip convention. Look up the specification and calculate the quantity. Screenshots with large pip numbers are not a substitute for that calculation.
A zone is still a decision
A post such as “BUY GOLD 2400–2403, SL 2395” leaves an execution policy to resolve. Entering near the top of that illustrative zone creates a different stop distance from entering near the bottom. The entry-range article explains why silently choosing the midpoint is not an innocent formatting step.
Also distinguish the chart price from the executable side of the quote. Spread widening can affect entry and protective order behaviour, particularly near interruptions or thin trading periods. Test with recorded Bid and Ask values rather than diagnosing every difference as parser delay.
Use a small specification sheet
Before enabling the route, save the destination symbol, contract specification, volume convention and an example expected order. Run that example on demo and inspect the actual protective levels. Repeat after changing brokers or accounts, because a familiar platform interface can hide a different contract underneath.
Keep the source's advertised performance separate from this technical validation. The risk article explains how several individually modest gold entries can accumulate into a much larger account exposure.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay