Store the minimum reliable fields
Each observation should include event ID, operator, market, selection, line, price, currency or format, timestamp and availability.
Normalize odds formats for analysis while preserving the original quote for audit.
Use meaningful alert thresholds
A fixed decimal change behaves differently across price ranges. Implied-probability or percentage-change thresholds can provide more consistent alerts.
Require persistence or confirmation from more than one source to reduce noise from temporary feed errors.
Label causes as verified or unknown
Connect official team news and event-status feeds where possible. If no reliable source explains the movement, keep the cause unknown.
Do not generate inside-information or fixed-match labels automatically. Those claims can be false and harmful.
Design alerts to reduce harm
Avoid urgency language, loss-chasing prompts and notifications aimed at minors or self-excluded users. Provide quiet hours and easy alert disabling.
An alert is a data event, not an instruction to spend money.