How do I measure TradingView-to-cTrader latency correctly?

What this means in practice

Timestamp the signal/alert, webhook receipt, connector dispatch, cTrader request, acknowledgement and broker fill. Report median and tail latency rather than one best-case number. This page is specifically about “How do I measure TradingView-to-cTrader latency correctly?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Transport fast, fill slow

Inspect the mechanism named by “Scenario A — Transport fast, fill slow” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Transport fast, fill slow on question 37, use that evidence specifically to answer “How do I measure TradingView-to-cTrader latency correctly?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Bar-close delay mistaken for network

Inspect the mechanism named by “Scenario B — Bar-close delay mistaken for network” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Bar-close delay mistaken for network on question 37, use that evidence specifically to answer “How do I measure TradingView-to-cTrader latency correctly?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Reconnect outlier

Reconnect is a reconciliation event. Re-read actual cTrader positions and pending orders first, then decide whether queued commands remain valid. Expire stale entries and make recovery idempotent. For Scenario C — Reconnect outlier on question 37, use that evidence specifically to answer “How do I measure TradingView-to-cTrader latency correctly?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• target connector/account identity
• exact broker symbol
• normalized order parameters
• cTrader response and final position/order state

Practical rule

For “How do I measure TradingView-to-cTrader latency correctly?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.