Events

A member can see events recorded for the app’s active environment. A public key records an event for one subscriber.

How it works

An event has a name, a subscriber, and optional properties. The page lists the active environment, newest first, in pages of 10, 25, or 50. Search matches the event name or the subscriber’s name, email, or external id. The name filter lists names this environment has recorded. The subscriber filter lists people who recorded an event here. The segment filter uses this environment’s segments, including Android users, so the list can show events from that audience. Another environment is not included. An empty list stays empty. Opening an event shows the properties passed with it, colored and formatted, with a copy button, or that nothing was passed. The subscriber is a badge. Opening it shows that person’s email and platform. notification_opened is stored the first time a delivered notification is opened. notification_clicked is stored the first time that delivery’s link is reported. A notification or a segment can target either name, or any name the app recorded.

A developer, admin, or owner can delete selected events in this environment after confirming. A viewer can see the list and cannot delete. Deleting an event removes it from audiences that match that recorded name.

Recording an event does not send a notification unless an automation for that event name matches the subscriber’s segment. That send still happens when the event arrives. An audience of people who already recorded the name is a separate notification or segment.