Skip to Content

Live events

Go to Live in the workspace nav to see a real-time stream of everything happening in your workspace.

What you see

A scrolling feed of events, newest first:

Event typeExample
trackorder_completed fired by user_456
identifyuser_456 identified with traits (plan: “pro”)
pageuser_456 viewed /products/widget-x
delivery.sentEmail sent to user_456 for campaign “Holiday Sale”
delivery.deliveredWhatsApp delivered to user_789
delivery.openedEmail opened by user_456
delivery.clickedLink clicked by user_456 (URL: /checkout)
delivery.bouncedEmail bounced for user_101 (hard bounce)

Each event shows:

  • Timestamp
  • Event name
  • Contact (user ID or anonymous ID)
  • Properties (expandable)
  • Source (SDK, API, webhook, internal)

Filtering

Filter the live stream by:

  • Event type — track, identify, page, delivery, or custom
  • Contact — search by user ID or email
  • Channel — WhatsApp, Email, SMS, Push
  • Campaign — filter to events from a specific campaign
  • Outlet — set the workspace location chip, or type outlet:loc_<id> in the search bar to narrow the stream to a single outlet (every event is stamped with location_id by the analytics consumer)

Metrics bar

Above the event stream, a real-time metrics bar shows:

  • Events/second — current ingestion rate
  • Sends in-flight — messages currently being delivered
  • Active contacts — contacts who fired an event in the last 5 minutes

Use cases

  • Debugging: “Did the SDK actually fire the signup_completed event?” — search by contact ID
  • Campaign monitoring: filter to a campaign and watch delivery confirmations roll in
  • Integration verification: after setting up a Shopify webhook, check that order events appear
  • Demo: show stakeholders real-time engagement during a campaign launch

Live debugger

Click Debugger in the top-right to switch to debug mode:

  • Fire a test event from the UI (select event name, enter properties)
  • See the full event payload as it flows through the pipeline
  • Verify that the event matches your schema and triggers the expected segments/journeys

What’s next