Key events and conversions
Most projects send many events. Two settings tell Rabolic which ones matter.
| What it is | Where you set it | |
|---|---|---|
| Key event | An event that marks real progress, such as signup_completed or workout_started | On the event's page in Events: Mark as key |
| Conversion | A key event that counts as success, such as checkout_completed | Project settings → Project → Conversions |
Mark an event as key
- Open Events and click the event in the catalog.
- Choose Mark as key. You can give it a display name.
- To undo it, choose Unmark key.
Key events have a ★ in the catalog and on the Overview's Top events. You need the permission to edit reports: owners, admins and analysts have it.
Choose your conversions
- Open Project settings → Project → Conversions.
- Add a key event. Only key events are suggested: mark an event as key first.
- The first conversion is the primary one. Use Make primary to change it, or remove one.
Changing the project settings needs the project settings permission: owners and admins.
What they change
| Report | Uses |
|---|---|
| Overview | Counts of key events and conversions, and the conversion rate |
| Live | Conversions in the last 30 minutes, with a Conversion badge on each one in the feed |
| Sessions | A session is converted when it contains a conversion event |
| Journeys | Goals and milestones are your conversions, your key events and app installs ($app_first_open). The primary conversion is the default goal |
| Retention | "Came back and" can be one of your key events |
| Funnels | Any event can be a step, key or not |
| Alerts | The conversions metric counts conversion events |
Conversions are applied when a report runs, not when events arrive. Adding or removing a conversion changes past sessions and reports consistently.
Sessions
How Rabolic starts and ends sessions on the web (30 minutes without events) and in apps (30 seconds in the background), active time, conversions and revenue in a session.
Funnels
How Rabolic counts funnels per person across web, apps and server, with 2 to 10 ordered steps, a 1 to 90 day window, step filters, breakdowns and median timing.