Track the product actions that matter
Send named events and scalar properties alongside pageviews. Follow signups, trial starts, purchases, and feature usage through the same analytics pipeline.
How to install ↗Define an event contract
Name events after completed actions, such as signup_completed or report_exported. Keep names stable and put varying context in properties. Supported values are strings, numbers, booleans, and null; nested objects are not part of the current browser contract.
Track actions after initializing the SDK
analytics.track('signup_completed', { plan: 'starter', method: 'email' });
analytics.track('purchase_completed', { revenue: 49, currency: 'USD' });Explore activity and trends
Search and filter the activity feed by event and request context. Use top events and date-ranged time series to inspect changes, then build ordered funnels or save a chart.
Keep your properties intentional
Avoid passwords, form contents, access tokens, and unnecessary personal data. The SDK removes full page URL queries, but a property you explicitly send is still data you chose to collect.
Keep event volume understandable
Accepted page and track events drive the reports. Plans are based on customer ARR with monthly visitor allowances rather than an event bill. Replay uploads have a separate rolling storage budget.
Frequently asked questions
Are pageviews automatic?
The SDK sends an initial pageview by default. Add router handling for client navigation that does not trigger popstate.
Can I attach a user ID?
Call identify after login. Subsequent events carry the explicit user ID while anonymous identity continues to rotate daily.
Can properties contain arbitrary objects?
Use scalar properties. The current browser SDK does not support nested objects or arrays as event properties.
Start with a clear measurement model.
Install the SDK, then explore traffic and product activity with the same definitions.