Track Events
Use track to record product actions such as signups, purchases, feature usage, page views, and activation milestones.
Track a small set of meaningful events first. A few stable event names with useful properties are easier to query than a large stream of low-signal UI clicks.
When to call it
Use track when something happened in your product and you want it available for segmentation, retention, funnel analysis, SQL, or Ask AI.
Good first events often describe:
- activation moments
- conversion steps
- recurring feature usage
- billing or account lifecycle changes
SDK examples
Use track() where the product action happens:
altertable.track('checkout_completed', {revenue: 49.99,plan: 'pro',currency: 'USD',});
distinct_id ties an event to a person, device, or session. Client-side SDKs can manage anonymous IDs automatically. Server-side SDKs and direct API clients should pass a stable ID on each call.
Call identify() when you know who the user is, so anonymous and authenticated activity can be analyzed together.
API reference
For HTTP request details, batching behavior, response shape, and error codes, see POST /track.
Best practices
- Use clear event names and keep them stable over time.
- Track meaningful product actions, not every low-level interaction.
- Include only properties you plan to filter, group, or query.
- Avoid secrets and regulated sensitive data in event properties.