Events

Browse your project’s event catalog and explore schemas. Use this page to plan your tracking implementation and verify SDK instrumentation.

Path: /p/:projectId/events

Event catalog

The catalog lists every event name seen in the project:

Column	Description
Event name	The `name` field sent by SDKs or API
Volume	Total count in the selected time range
First seen	When this event name first appeared
Last seen	Most recent occurrence
Properties	Count of distinct property keys observed

Events appear in the catalog after the first successful ingestion. Auto-tracked events like page_view and click appear automatically once the Web SDK is initialized.

Schema exploration

Click an event name to open the schema panel:

Property keys — all keys ever sent with this event
Inferred types — string, number, boolean (based on observed values)
Sample values — recent examples for each property
Cardinality — how many distinct values exist (useful for breakdown planning)

Use schema exploration to:

Plan Insights filters — confirm property names before building queries
Audit SDK instrumentation — spot missing or misspelled properties
Review auto-properties — see which $-prefixed fields are attached

Example: auditing a purchase event

Expected schema for purchase:

Property	Type	Required
`revenue`	number	Yes
`currency`	string	Yes
`order_id`	string	Yes

If revenue shows as string in the schema explorer, fix your SDK call:


// Wrong — revenue as string
track('purchase', { revenue: '29.99', currency: 'USD' })
 
// Correct — revenue as number
track('purchase', { revenue: 29.99, currency: 'USD', order_id: 'ord-456' })

Well-known vs custom events

Type	Validation	Dashboard support
Well-known events	Protobuf schema enforced	Built-in commerce, signup, and engagement templates
Custom events	Any string accepted	Full Insights support, no schema validation

Well-known events like page_view, purchase, and signup have typed property schemas. Custom events work everywhere but won’t trigger schema validation warnings.

Building a tracking plan

Use the Events catalog as your tracking plan source of truth:


Event            | Trigger                    | Key properties
-----------------|----------------------------|------------------
page_view        | Every page load (auto)     | $url, $referrer
signup_started   | Signup form opened         | method
signup_completed | Account created            | method, plan
purchase         | Order confirmed            | revenue, currency, order_id

Share this table with engineering before implementation. After deploy, return to Events to confirm each row appears with the expected properties.

Common issues

Symptom	Fix
Event missing from catalog	Verify SDK init and project ID; check Live
Property missing from schema	Property wasn’t sent on any event — check SDK call site
Duplicate event names	Standardize naming (`signup` vs `sign_up` vs `SignUp`)
Unexpected auto-properties	Review Auto-tracking settings