What does not exist yet

One dated list of the analytics capabilities that are not on the public surface today, so you do not spend time looking for them.

So you don't spend time looking for it, none of the following exists on the public surface today.

As of August 2026:

Not availableMeaning
An analytics, metrics or reporting APINo endpoint on the public gateway returns a metric, a series or an aggregate.
A semantic-layer APINo API to read or query dataset definitions.
A metric-definition APINo way to define a metric with a formula and reuse it, from code or from Cockpit.
An embeddable dashboardNo component, iframe or SDK for putting a platform chart in your own product.
A guest-token or scoped-read-token flowNo way to grant a viewer temporary read access to a dashboard or dataset.
A funnel builder, or an API for querying funnelsNeither in Cockpit nor on the gateway.
Forecasting, anomaly detection and natural-language queryingNot present in any form.
Scheduled export deliveryNo way to have a report or extract delivered on a schedule.
Prepared platform-wide revenue, orders or customers datasetsThe platform's own orders and customers apps do not ship an analytics.json.
A warehouse you can queryNo SQL endpoint, no read replica, no data-sharing target.

Two clarifications, because they are the ones people ask about:

  • analytics.json is not a query API. It publishes your App's data as datasets in the tenant's Cockpit. It does not give your code a way to query them. See The contract.
  • The Analytics Studio surface in Cockpit is not an API with a UI in front of it. It is a Cockpit feature. There is nothing behind it you can call — see Studio overview.

What does exist

For contrast, the three things you can build on today:

AvailableWhere
The event stream, delivered to your endpointStream commerce activity
Every commerce entity, readable and pageableBackfill, API usage
analytics.json, versioned and validatedMake your app's data analyzable

If you are relying on anything in the first list, build it on your own side from the second — see Getting data out.

Before you plan around a change

This list is dated on purpose. Check the changelog for what has actually shipped rather than inferring intent from the absence of something here, and do not commit a customer to a delivery date on a capability that is not in the second table.

Where to go next

Was this page helpful?