Equity consumer research
Stock alert delivery, webhooks and broker acknowledgements
Follow a stock event through publisher, notification, routing and broker state without mistaking an HTTP response for execution.

Name each stage in the chain
Keep separate records for a chart or publisher event, notification attempt, destination acknowledgement, order submission, broker acceptance and executed quantity. An upstream event may be valid even if a downstream action never occurs. A consumer comparison should therefore ask which service owns each stage and which failure states are exposed. This does not imply that every product offers automation or that every buyer needs it.
Document the actual rule instance
TrendSpider and TradingView describe notification or webhook mechanisms, but their documentation does not establish our observed reliability. Save the active rule, symbol, interval and session interpretation, including any frozen inputs that differ from the currently displayed chart. A backtest name and a cloud bot label are not enough to resolve actual operational identity. Define what counts as a missed event before comparing a chosen forward observation stream.
Retries require an identity rule
A repeated delivery attempt should have a stable event key so the receiving workflow can distinguish retry from a new instruction. Ask the operator for its actual duplicate handling and order status checks rather than assuming that repeating a request is harmless. A successful network response may acknowledge receipt without accepting a broker order. Conversely, a timed-out response can leave an uncertain action that needs reconciliation, not an automatic second order.
Keep consumer and provider conclusions separate
This publication did not connect a paid product to a broker or benchmark notification latency. The case below is an original state exercise. It helps a buyer ask for a complete route history, but it neither proves an outage nor certifies execution quality. Retain unresolved states and verify them against the component that owns the record. A highlighted successful trade cannot explain missing messages in the surrounding inventory.
Completed fictional case
Fictional event E17 fires once. The first webhook attempt times out; a retry uses the same E17 identity and receives HTTP 200. The destination records E17 once, but its broker order receives a rejection. Reconciled totals: one publisher event, two delivery attempts, one destination event, one rejected order and zero share fills. Counting the two attempts as two signals is wrong; treating HTTP 200 as a profitable fill is also wrong. The rejection reason needs the broker record rather than an invented explanation.
| Record | Represented finding | Boundary |
|---|---|---|
| Upstream | One event / two attempts | Retry identity retained |
| Destination | One acknowledged event | Not an accepted order |
| Broker | One rejection / zero fills | No achieved account outcome |
Primary references and inspection scope
- TrendSpider: alerts and execution connections
- TrendSpider: strategy-bot configuration
- TradingView: alert setup
Public-document inspection: 12 October 2026. The case arithmetic is original fiction, not a sourced provider outcome. No paid software, selected leader, broker route or subscriber account was tested.