Product Analytics
Altertable can ingest product analytics events and identities into the built-in product_analytics catalog.
Once enabled, product behavior data lives in the same lakehouse namespace as your other catalogs. You can federate it with operational, billing, support, and warehouse data, then consume it the same way with SQL, dashboards, insights, or AI agents.
That means product questions do not live in a separate analytics silo. You can connect feature usage to revenue, support activity, billing state, and any other source already available in Altertable.
Enable Product Analytics
Open Catalogs, choose New Catalog, and enable Product Analytics for the target environment.
After the catalog is enabled, authenticate an SDK or direct API client with a Product Analytics API key, identify users when they are known, and track the product events you want to analyze.
Tables and views
When you enable Product Analytics, Altertable creates the catalog tables for you and exposes API endpoints that make ingestion easier. As your application sends events and identity updates through the Product Analytics API, Altertable writes the resulting data into these tables and views:
Table | Description |
|---|---|
main.events | Raw events (everything /track receives) |
main.identities | Raw identities (everything /identify receives) |
main.identity_distinct_ids | Raw distinct IDs mapping |
main.identity_distinct_id_overrides | Raw distinct ID overrides (impacted by /alias) |
analytics.events | Identity-resolved events |
analytics.identities | Alias & anonymous-resolved identities |
analytics.web_sessions | Aggregated session data |
analytics.web_pageviews | Page-level analytics |