Analytics Studio

How to get analytics out of the platform today — there is no public analytics API, so the working paths are events, the commerce API, and shipping an analytics.json with your App.

Start here

Getting data out

The three paths that work today, and how to choose between them.

What does not exist yet

One dated list, so you do not spend an afternoon looking for an API that is not there.

The five groups

Stream commerce activity

Events and webhooks as the reporting feed — registering an endpoint, verifying a delivery, delivery guarantees.

Build your own reporting store

Pull versus push, backfilling, incremental sync, and the modelling traps.

Make your app's data analyzable

`analytics.json` in full — the only shipped, versioned contract here.

What the tenant sees

Orientation on the Cockpit surface — datasets, charts and cohorts. Not an API reference.

Limits and what's next

What is genuinely missing, and how to design so you are not caught out when it lands.

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

There is no public analytics API. The gateway at https://api.revenexx.com exposes no analytics, metrics, reporting, semantic-layer or dashboard endpoints, and there is no embeddable dashboard and no guest-token flow for putting one in your own product. Nothing in this section is a query API. If you need numbers inside your own application, you build the query side yourself.

Analytics Studio is early and still moving. Treat what you see in Cockpit as a preview of the operator surface, not as a contract you can build against.

There is one thing you can ship against today, and it is genuinely useful: an App can declare its own analysable views in an analytics.json, and those views show up as datasets in the tenant's Analytics Studio. That is documented in full in Make your app's data analyzable.

How this section is organised

Group	What it covers
Stream commerce activity	Using the event stream as a reporting feed: which events carry reporting value, registering an endpoint, verifying a delivery, and what the delivery guarantees mean for your numbers.
Build your own reporting store	The path most partners end up on: pull versus push, backfilling history, keeping in sync, and modelling commerce data without getting the grain wrong.
Make your app's data analyzable	The `analytics.json` contract in full — the only part of Analytics Studio with a public, versioned schema.
What the tenant sees	Orientation on the Cockpit surface your declared views land in. Cockpit features, not partner endpoints.
Limits and what's next	One honest list of what does not exist, and how to design around it.

Start with Getting data out if you are here to build something.

Where to go next

Getting data out — the three paths that work today.
Events — subscribe to commerce activity as it happens.
Webhooks — deliver that activity to your own endpoints.
API usage — pagination, filtering, rate limits and errors for the pull path.
API Explorer — every commerce endpoint, ready to try.
Apps — the App model that analytics.json belongs to.