Dashboards and reports

Reports and exports

Run a report over your own data, filter it with a segment, and get it out as CSV.

The prepared Measure screens answer fixed questions. Reports are meant to answer yours: they run over the datasets your installed apps contribute, so what you can report on grows as your platform does.

How this will work. Analytics Studio is planned and not yet on your tenant. This page describes the reports, segments and exports as designed. Today, the way to get order data out is the CSV export of the order list in Commerce Studio, or an export profile in Integration Studio › Import & Export. See Bulk exports.
Datasets, briefly. Every app can publish one or more datasets: flat, read-only views over its own data. The products app publishes a product dataset (SKU, kind, enabled, family, manufacturer, categories), the customers app publishes customer data, and so on. Reports, segments, exports and the chart builder all work off the same list, so anything true of a dataset in one is true of it in all.

Find a report

The datasets are grouped by the app that owns them. Each names the dataset and how many fields it has. From a dataset you choose how to open it:

  • Timeframed report: KPIs, a trend and a breakdown over time.
  • Cohorts: retention and value by acquisition cohort. Only offered when the dataset has both a time column and an entity key.
  • Custom chart: hand it to the chart builder.

If a dataset you expect is missing, the app that owns it is not installed. See Apps and the Marketplace.

Run a timeframed report

A report has four controls: the dataset, a segment, the date range, and export. Below them:

  • Trend: pick what is plotted. You always get a record count, plus one entry per numeric measure the dataset declares. The bucket size follows the length of your range: roughly, days for a few weeks, weeks for a few months, months beyond that.
  • In this period: the record count, plus a total per measure.
  • Breakdown by the same bucket, newest first.

A dataset with no time column cannot produce a timeframed report.

Save a filter as a segment

A segment here is a named, reusable set of filters against one dataset. Build the filter once, use it on every report of that dataset instead of rebuilding it. (Do not confuse it with a customer segment in CRM, which selects organizations and exists today.)

  1. Name it for what it selects, not how: Repeat B2B buyers, not filter_1.
  2. Pick the dataset.
  3. Add filter rows. Each is a column, a comparison and a value: equals, not equals, greater or less than, in a list, matches a pattern, is empty.
  4. Save.

A segment with no filters matches every record. A report's default is all records.

Export

The plan is a one-off export: pick a dataset, set a row limit, download CSV. Every column of the dataset is included, and any report or breakdown you are looking at exports what is on screen.

Do not plan on scheduled delivery from Analytics Studio. If you need a file to land in an inbox or a folder every Monday morning, build it in Integration Studio, where scheduling, retries and failure alerting run today: an export profile plus a schedule, delivered by SFTP or Storage Sync. See Bulk exports and Build a workflow. CSV is the format to plan for; do not promise anyone a PDF.

What to check

Open the export in the tool that will consume it. Two things go wrong often enough to be worth checking on the first run: decimal separators when the file is opened in a German Excel, and a row count that is exactly your limit, which means the export was truncated, not complete.

Next

Dashboards and KPIs

The standard views planned for Analytics Studio, what each number means, and which ones to read first.

Build a custom dashboard

Build a chart, put it on a board, and freeze the result when you need a number that stops moving.