Observed events are the raw stream of events your widget has fired, regardless of whether you've configured a moment for them. They're the discovery layer — "what is my app actually doing?" — before you commit to feedback prompts.
Where to find them
On the Moments page, click the Observed events tab.
You'll see a list of every distinct event name your widget has reported, with counts and most recent fire time.
Why this view exists
Two common workflows:
1. "What events are even firing?"
Your app fires events. You want to see them all in one place to figure out which ones are worth turning into moments.
2. "Did my new event get instrumented correctly?"
You ship a new event from your app. You expect to see it appear in observed events within seconds. If it doesn't, the instrumentation is broken — wrong name, wrong widget, wrong API key. Catching this here is much faster than catching it in production a week later.
Promoting an event to a moment
In the observed events list, each event has a Create moment action. Clicking it opens the create-moment drawer pre-filled with the event name.
You then fill in the prompt copy, sampling, and cooldown — same as creating a moment from scratch.
Events without moments
Events that don't have a moment configured still show up in observed events with their fire counts, but they:
- Do not show a prompt to the user.
- Do not produce feedback items.
- Are not visible in the main feedback list.
They're informational only. The moment configuration is what activates them.
Retention
Observed event records are retained for the purposes of the discovery view. We don't expose a retention setting today; if you have a specific retention need (e.g., compliance), contact support.
Privacy
Observed events store only:
- The event name.
- The time it fired.
- The identified user (if you've called
identify()).
They do not store arbitrary event payloads. If you want to attach metadata to a moment reaction (e.g., "the export that just completed had 5,000 rows"), pass it as part of the user identification or include it in the follow-up text. Free-form event payloads aren't supported today.