Studio overview

What the Analytics Studio surface in Cockpit consists of, and the plain statement that these are Cockpit features with no partner-facing endpoints behind them.

Analytics Studio is the reporting surface inside Cockpit: a catalog of datasets over the tenant's data, a chart builder, and cohort analysis on top of them.

These are Cockpit features, not partner endpoints. There is no analytics, metrics, reporting, semantic-layer or dashboard API on the public gateway; no embeddable dashboard; and no guest-token or scoped-read-token flow for putting one of these views inside your own product. Nothing on this page can be called from your code.

What the surface consists of

Three things, in the order an operator meets them:

  1. A dataset catalog. The datasets available to the tenant, each with a title and description. Views declared by an installed App's analytics.json appear here alongside whatever the platform's own apps register.
  2. A chart builder. Pick a dataset, pick a measure and a dimension, scope it to a date range, and get a chart.
  3. Cohort analysis. Follow a set of entities over time. This one has a hard requirement on how a dataset was declared — see Cohorts.

What that means for you

If you are shipping an App: this is your audience. The quality of what an operator can do here is decided almost entirely by your declaration — the roles you set, whether your dimensions are readable, whether your title states the grain. See Semantic roles.

If you are building analytics into your own product: this surface is not a component you can reuse. You build the query side yourself, from the event stream and the commerce API, into a store you own. There is no shortcut, and there is not one coming that you should plan a release around.

If a customer asks you to "just embed the Cockpit charts": there is no embed and no guest token. The honest answer is that the charts live in Cockpit for staff who have Cockpit access, and anything inside your product is something you build.

Maturity

Analytics Studio is early and still moving. Its shape, its navigation and its capabilities are all subject to change, which is exactly why this group is three short orientation pages rather than a feature reference: a reference would be wrong within a release.

Check the changelog for what has actually shipped before you tell a customer anything about it.

Do not reproduce the UI

Do not screenshot or quote the Analytics Studio UI in your own material. Its demo fixtures include real customer names, so a screenshot is a disclosure risk rather than a documentation shortcut. Describe what an operator can do; do not show their screen.

Where to go next

Was this page helpful?