Service updates.

Ask in plain English, get the governed answer. The assistant reads the measure catalog and the dataset schemas it has actually discovered — never a guessed column — and every write it suggests, from a chart to a quality rule, is proposed first and applied only after you approve it. Available on every tier; bring your own OpenAI key on Professional for unmetered use. It joins the Visual line as the Assistant station.

The Google Sheets connector now ships with a platform service account: share your sheet with one address and sync it — no Google Cloud project, key file or IAM work on your side. Connector errors now say what actually went wrong (sheet not shared, sheet not found) instead of a generic failure.

Accounts can now recover access with a password reset flow and verify their email address. Both run on single-use, expiring tokens, and the public endpoints are careful not to leak whether an address exists.

Charts over large event tables now read pre-aggregated rollups when the query planner proves the answer is identical — minute-level and coarser grains, kept fresh by the platform, with an admin surface showing what is materialized and how fresh it is. Dashboards over months of events get faster without a semantic change: if the rollup can’t answer exactly, the query reads the raw tables as before.

Surveys can now match your product: colours, logo and imagery are configured server-side and rendered consistently by all capture SDKs. Alongside them, in-app messages deliver announcements through the same SDK surface, with delivery and interaction tracked as first-class events.

Capture SDKs now implement explicit consent postures — full, cookieless and none — and an opt-out always outranks any consent signal. Session replay respects the same gate: it never starts for opted-out users and stops mid-session the moment someone opts out.

Nested JSON event properties are now first-class across the product: filter on them, group by them, and pick them from a discovered key catalog in charts, funnels, cohorts and the event explorer — no flattening step, no schema migration.

A batch of correctness work on the event path: ingestion is acknowledged only after a durable commit, stalled queue entries are reclaimed automatically, live tail applies filters exactly as the stored query does, and the merge path no longer risks dropping unmatched rows.

Built-in events now use a consistent az.* vocabulary (az.pageview, az.session_start, …) with one source of truth shared by SDKs, ingestion and the UI. Legacy $-prefixed names are aliased at ingestion forever — existing tracking plans keep working without a migration.