Use events to choose a meaningful moment
Understand the difference between defining an event and receiving it from your product.
Last updated 9 September 2026
On this page
What an event represents
An event records something that happened, such as route_saved or checkout_completed. It can provide the context for a question, a survey, or an in-app message. The name and properties should describe the action consistently across your app.
Prepare the event
Open Events for the selected app and review the definitions already registered.
Register a definition when you want a clear name, description, and expected properties.
Ask your developer to send that event from the point where the action succeeds.
Perform the action in a test build and check the recorded event or user activity before using it as a trigger.
A definition is not activity
Registering route_saved tells UserGist about the event; it does not record a route being saved. Similarly, typing an event name into a trigger does not make your application send it. If an experience never appears, confirm the actual event arrives for the test identity.
Use properties for context
Properties can narrow an event to the moment you care about—for example, a route saved with download_type equal to offline. Agree on the spelling and value type with your developer. A rule expecting a number cannot be tested reliably with a differently formatted text value. Keep unnecessary personal information out of event properties.