Your operational data, in your own dashboards.
Reports inside a platform answer the questions that platform thought of. Connecting Power BI to Zooza hands you the tables themselves, so a franchise network can put occupancy next to marketing spend and a studio owner can build the one chart nobody shipped.
It is a data connection, not a canned dashboard. You get the tables and join them yourself.
How the connection works
Zooza writes your data to storage and gives you a credential to read it. Power BI connects to that storage like any other source.
The source
Azure Data Lake Storage Gen2 Your data sits in a single location in Azure storage. In Power BI you add it as an Azure Data Lake Storage Gen2 source rather than as a Zooza-specific connector, which means it behaves like any other enterprise source your analyst already knows.
The credential
SAS token Activate the integration in Zooza and you are given a URL and a shared access signature. Paste the URL into Power BI, choose Shared access signature (SAS) as the credential type, and you are connected. No API key, and nothing to expose in a browser.
The history
the whole company The export carries your entire company history rather than a recent window, so year-on-year comparisons and cohort work are possible from the first connection.
The ten tables you get
Joined on keys like schedule_id, instructor_id and place_id. Most useful questions need two or three of them together.
Who and what: Registrations, Orders, Programmes
Registrations carry the booking with its payment, schedule, client and trial workflow. Orders hold every purchased product with payment and user. Programmes hold the configuration behind them — pricing, make-up rules, trial options, auto-enrolment.
When and where: Sessions, Schedules, Places, Attendance
Sessions give every instance with status, time, location, instructor and attendance metrics. Schedules carry capacity, booking counts, pricing and performance. Places covers active and inactive locations. Attendance records who turned up, per session.
Cost and tagging: Instructor rates, Rate types, Labels
Instructor rates come with a recalculated per-minute amount, which is what makes a true cost-per-session chart possible. Labels are the tags you applied to programmes, classes and bookings, so your own taxonomy survives into the reporting.
What to know before you plan around it
Two of these are genuine gaps in what is documented. We would rather say so than let an analyst discover them mid-build.
Refresh frequency is not documented
The help article does not state how often the export refreshes, so treat this as reporting rather than live monitoring until you have confirmed the cadence with us. If your dashboard needs to be current to the hour, ask first.
It is tables, not a dashboard
There is no pre-built Zooza dataset or report pack. Someone has to model the joins. For a network with an analyst that is a feature; for a single studio with nobody to do it, the built-in reports are the better answer.
It is a read, not a write
Power BI reads what Zooza exports. Nothing flows back, so a correction belongs in Zooza and arrives in the report afterwards.
The SAS token is a credential
Treat it as one. It reads your whole operational history, so it belongs in the Power BI connection rather than in a shared document.
Setup detail lives in the help centre: help.zooza.online/settings/power-bi-integration/ · help.zooza.online/settings/power-bi-data-description/
Questions before connecting Power BI
-
What exactly do I connect to?
Azure Data Lake Storage Gen2, using a URL and a shared access signature that Zooza gives you when you activate the integration. In Power BI it is the standard ADLS Gen2 source with SAS as the credential type — nothing bespoke to install. -
Which tables are available?
Ten: Attendance, Programmes, Sessions, Labels, Orders, Places, Registrations, Schedules, Instructor rates and Instructor rate types. They join on keys such as schedule_id, instructor_id and place_id. -
How far back does the data go?
The export carries the entire company history rather than a rolling window, so year-on-year and cohort analysis works from the first connection. -
Can I see cost per session?
Yes, and this is the one most platforms cannot answer. Instructor rates include a recalculated per-minute unit amount, so joining them to Sessions gives a real cost line next to the revenue in Schedules. -
How often does the data refresh?
The documentation does not say, and we would rather tell you that than guess. Ask us before you build anything that depends on a specific cadence — for term-level and month-level reporting, which is most of it, this has not been a constraint in practice. -
We do not use Power BI. Can we get the data another way?
Yes. The REST API exposes the operational entities directly if you would rather pull them into your own warehouse or app, and there is a spreadsheet export for anything that just needs to reach a bookkeeper.
Put your classes next to everything else you measure.
Ten tables, the whole history, and a standard Azure source your analyst already knows how to connect.
