Fast answer
Ichimoku signals need line context and final records.
Before using an Ichimoku Cloud crypto signal, check the chart time frame, conversion line, base line, leading spans, cloud color, lagging span context, entry trigger, invalidation, stop plan, target logic, update trail, and final status.
If the alert only says price is above or below the cloud, treat it as trend context until risk and follow-up proof exist.
Cloud checks
What to inspect in an Ichimoku signal.
Line roles
Record which line or span triggered the alert, not just that the chart displayed an Ichimoku Cloud.
Time frame
Cloud readings can differ across charts, so the provider should lock the time frame and avoid after-the-fact switching.
Trend state
Check whether price is above, inside, or below the cloud and whether the call includes invalidation if the state changes.
Close record
The signal should include updates, stop handling, partial exits, failed setups, and final status.
Source context
Ichimoku Cloud combines multiple technical views.
TradingView's Ichimoku Cloud help page describes the indicator as a package of technical indicators for support, resistance, trend, and momentum, while also noting limitations from historical data. That means a cloud signal still needs a proof trail.
Review standard
Ichimoku calls should show the exact signal condition.
A reviewable Ichimoku record includes source chart, settings, time frame, trigger line, cloud state, lagging-span context, alert timestamp, invalidation, stop, target, update trail, and final status. Cropped cloud screenshots without line details should lower confidence.