Events

Events lists every event your SDKs and servers send. Rabolic adds an event name to the catalog the first time it arrives; there is nothing to define in advance.

Tiles

• Events ingested: accepted events in the period. Rejected and duplicate events are left out.
• Event types: how many event names, and how many are key events and conversions.
• Verified revenue events: purchases, renewals and refunds received from your server or a payment provider.
• Governance issues: naming problems found in the catalog.

Catalog

Filter by status (All, Active, New, No data, Deprecated) and type (Page view, Screen view, Custom, Identify, Revenue, Lifecycle).

The event page

Click an event to open it:

• total events, unique users, events per user and when it was last received;
• funnels that use it;
• its schema: each property with its type, an example value and how often it's set, with a check for sensitive property names;
• its top users.

Mark as key

Choose Mark as key on the event's page. You can give it a display name. Unmark key undoes it. Key events become goals and milestones in Journeys, and can be added as conversions in Project settings. See Key events and conversions.

Governance

The Governance tab points out events that need a look:

• names that aren't snake_case;
• the same event under two names, such as signup-completed or Signup Completed next to signup_completed;
• events that stopped arriving;
• new events nobody has reviewed.

Fix naming problems in your code: Rabolic doesn't rename events that were already sent.