The platform records message and engagement events at high volume. They flow into an analytics store for millisecond-fast aggregations and dashboard queries, and are also fanned out to your developer webhooks for real-time integration.

​
Event types

CategoryExamples
Lifecyclequeued, sent, delivered, failed, revoked, expired
Engagementopen (email), read (RCS), click, reply
Qualityhard bounce, soft bounce, spam complaint, unsubscribe
Sessionconversation started (user reply), conversation ended (24-hour window closed)
Dashboards use these streams for KPIs: delivery rate, open/read rate, click rate, reply rate (RCS conversation), bounce rate, and unsubscribe rate.

​
Developer webhooks

Events are also delivered to your HTTPS endpoints as signed JSON payloads. Common event names: message.delivered, message.failed, message.read, conversation.started. See Webhooks API for the full event catalog, signing, and retry behaviour, or follow the Webhooks quickstart.

​
Campaign automation

CONDITION steps in campaigns can branch on engagement events — for example “opened email?” or “clicked link?” — enabling behaviour-based flows without polling the API.

Webhooks

Event types, HMAC signing, and retry semantics.

Campaigns

Flow steps that branch on events.

Billing API

Usage and tier data drawn from the same event store.