What counts as a tracked call
A tracked call is a public statement that identifies an asset and a direction or stance clearly enough to be represented in the dashboard. Broad commentary without a usable asset or stance may not become a tracked call.
How calls are tracked
Methodology
The rules behind tracked calls, prices, source attribution, and known limits.
Last updated June 27, 2026
What information is stored
Stored fields can include asset, asset type, direction, source name, speaker, publication time, original URL, quote, thesis or summary, starting price when available, latest stored price when available, and return-in-favor when it can be measured.
Entry or starting prices
When available, the starting price is intended to represent the price around the time the public call was published or captured. If price lookup is unavailable, the call can remain visible without an entry price.
Stored prices and return-in-favor
Stored prices may be refreshed after the call and can be delayed, stale, unavailable, or corrected later. Return-in-favor is calculated only from stored public-call data and available market-price data; the dashboard does not promise live pricing or complete symbol coverage.
Long, short, and neutral calls
For long calls, positive price movement is in favor. For short calls, negative price movement is in favor. Neutral calls are treated as watchful or non-directional; when a raw move is shown, it should not be read as a directional win.
Missing data and unavailable symbols
Some assets, symbols, or timestamps may not have usable price coverage. Data can be delayed, incomplete, or incorrect, and missing price data should not be treated as a zero return.
Source attribution and links
SignalTrades keeps source names and original-source links when available so users can review context directly. Summaries are meant to point back to the source, not replace it.
Limits and corrections
Automated extraction and price lookups can make mistakes. If a ticker, source, direction, duplicate, price, return, or calculation looks wrong, report it from the relevant call so the data can be reviewed.