Skip to main content

Track transactional delivery and engagement

Transactional sends — password resets, receipts, order updates — still generate the same delivery and engagement signals as a Broadcast. This page shows how to capture delivery status, opens, clicks, and bounces so your application can react to each event and your analysts can see the numbers alongside marketing sends.

Before you begin​

  • API access enabled for your account, with an API key or token that can read event data (confirm the exact steps in your account).
  • The endpoint or portal area where transactional events are exposed. Most accounts offer both a pull method (query events for a message) and a push method (webhooks that call your endpoint) — check which are turned on for you.
  • A message identifier returned when you sent the transactional message. Store this ID so you can correlate later events back to the original send.
  • If you plan to receive webhooks, a public HTTPS endpoint that can accept POST requests.

Steps​

  1. Capture the send identifier. When you submit a transactional send, record the message ID (and the subscriber address) from the response so every later event can be matched to it.
  2. Choose pull or push. For occasional checks, query the events endpoint by message ID. For real-time reactions, register a webhook subscription for the event types you care about — typically delivered, open, click, bounce, and spam_complaint (confirm the exact event names in your account).
  3. Handle each event type. Persist delivery and bounce events to update your own records; treat hard bounces and complaints as suppression signals. Opens and clicks are engagement signals and may fire multiple times per subscriber.
  4. Secure and acknowledge webhooks. Verify the payload signature (if provided), return a fast 2xx, and process asynchronously so retries do not pile up.
  5. Reconcile. Periodically pull events for recent message IDs to catch anything a webhook missed.

Result​

Your application receives or retrieves a timeline of delivery and engagement events per transactional message, keyed by message ID, and can act on bounces and complaints automatically.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.