Fast answer
Crypto signal conditional-order checks prove whether trigger price, trigger source, order type, margin status, and final status were visible.
Before accepting a conditional-order result, record the trigger price, trigger source, order type after activation, venue, pair, side, size, margin state, triggered timestamp, fill or cancellation, updates, and final close record.
If a provider posts a conditional entry without showing whether the condition triggered and what order was created, the result is incomplete.
Trigger checks
What to inspect in crypto signal conditional-order records.
Trigger price
The activation level should be visible before the move, not reconstructed after the result.
Trigger source
The record should show whether the trigger used last price, index price, mark price, or another exchange rule.
Post-trigger order
A conditional order may create a market or limit order, so the resulting execution type matters.
Final status
A reviewable record shows triggered, canceled, filled, partially filled, or expired status.
Source context
Conditional orders can trigger later and still fail, so the record needs trigger and post-trigger evidence.
Bybit describes stop-entry orders as orders that trigger a market or limit order when a specific price is reached. CSR treats that trigger as only the first step; the review still needs the created order, fill, cancellation, and final status.
Review standard
A reviewable conditional signal separates activation from execution.
For CSR evidence review, conditional-order records should include original alert, trigger price, trigger source, venue, pair, side, order type after trigger, size, margin state, fill or cancellation status, updates, and final outcome.