Fast answer
TradingView crypto signals need chart, alert, and close evidence.
Check the condition that triggered the alert, the market and time frame, the alert message, the delivery channel, the entry window, invalidation, stop, target, update rule, and final status. A screenshot of a chart alert is only a starting point.
If the signal cannot show the original alert and the final close record together, treat the history as incomplete.
Alert checks
What to inspect in a TradingView signal.
Trigger logic
Ask what condition fired the alert, which chart time frame was used, and whether the rule changed later.
Message fields
Look for symbol, side, entry, invalidation, stop, target, time frame, and update rule in the alert text.
Delivery path
Webhook, email, bot, and chat delivery can add delay or formatting errors that matter for fast markets.
Result link
The provider should connect the original alert to the update trail and final status.
Official context
Webhooks create delivery events, not verified trades.
TradingView explains that a webhook can send a request when an alert triggers, and warns users not to place sensitive credentials in webhook bodies. That is useful delivery context, but it is separate from strategy proof and risk review.
Review standard
Do not confuse automation with accountability.
A reviewable TradingView signal has a source chart, alert timestamp, delivery record, risk fields, updates, and final close. Missing alerts, changed settings, or edited messages should be disclosed in the record.