Fast answer
Bitget signal checks need margin and position context.
Before relying on a Bitget-labeled signal, check the contract, margin mode, leverage assumption, position-size context, stop logic, update cadence, and whether the provider labels liquidated, stopped, missed, and closed calls consistently.
Do not treat a futures venue mention as evidence of provider discipline.
Risk checks
What to inspect in a Bitget signal.
Margin mode
The alert should state whether the provider assumes cross or isolated margin, and whether followers may differ.
Liquidation context
Check whether liquidation distance, worst-case price language, or collateral shortfall risk is acknowledged.
Stop discipline
Stops should be visible before entry and preserved after closure, including when the trade goes wrong.
Result labels
Provider records should distinguish filled, missed, canceled, liquidated, stopped, and still-open calls.
Official context
Bitget documents liquidation and collateral shortfall rules.
Bitget's futures support explains liquidation and collateral shortfall calculations, including cross-margin allocation and isolated-margin cases. That makes margin context a required part of any reviewable Bitget signal record.
Review standard
Bitget calls should preserve the full futures context.
A reviewable record includes the original alert, contract, direction, margin mode, leverage assumption, stop or invalidation, update trail, closure note, and any missing-execution explanation.