Events

Event quality

Useful signals start with consistent events. Each event should have a clear name, a timestamp, and a stable identifier for the user, customer, account, or workspace it belongs to.

Event properties

Properties add context such as plan, usage amount, feature name, subscription status, or revenue impact. Keep property names stable so mappings and signal rules remain reliable.

Reviewing events

Use the Events area to check whether incoming data is complete and understandable before enabling signal routing for a team workflow.