Skip to content

Apaleo Power BI dashboard

We bring bookings, groups and revenue from the Apaleo API into Power BI for each property. We built a real-time dashboard for DutchSail.

For DutchSail, we developed a real-time dashboard that lets coaches monitor performance in the simulator as it happens

“The experts at Data Science Lab helped us streamline our dataflow by looking at the broader picture as well as solving the difficult IT issues we had […]” Dirk-Jan Korpershoek, DutchSail

Read the case study

Which guests stay longer, and which channel do they come through?

At aparthotels and hotel groups, stays range from one night to extended periods, alongside group bookings and additional services. To compare these by property and channel, you need to bring Apaleo data into your own model.

Book a call

Every property, every channel and every stay in the same model

Discuss your hotel figures

Length of stay and channel mix

Bookings by length of stay and booking channel, for each property, so you can see where short and long stays come from.

Groups and room blocks

Room blocks alongside how many rooms have been booked from each block, and which groups return.

Extra services alongside accommodation

Breakfast, parking or cleaning from the services booked, alongside room revenue for each property.

Near real-time where it matters

Just as we built a real-time dashboard for DutchSail, we refresh the data via webhooks whenever a booking changes.

Stay and property definitions set before loading

  1. Account and scope

    A read-only OAuth client, and which properties, rates and services are included.

  2. One property checked

    Reservations and revenue for one property in the model, checked against the reports in Apaleo.

  3. Expand and refresh

    All properties, finance, webhooks for changes and permissions by location.

Why use your own model alongside Apaleo’s reports?

Talk it through with us

A good fit if

You have multiple properties or brands, want to combine Apaleo data with accounting, revenue management or a second PMS, or compare data over longer periods.

Not a good fit if

You have one property and the standard occupancy, ADR and RevPAR reports answer your questions. In that case, your own model adds little.

What determines the scope

The number of properties and channels, which other systems are involved, how up to date the data needs to be and who manages the model.

Does this work with our other tools?

Apaleo is API-first, so its data is readily accessible. We can bring in other systems too, provided they support an integration or export.

The Reports API, a monthly export or your own model built on the Core API?

The Reports API

Choose this if you want key figures for each property, such as ADR, RevPAR and revenue. The figures are already aggregated, so you can’t drill down to individual reservations.

A monthly export

Choose this if one report goes to the owner each month. You’ll then have to link it to finance manually each time.

Your own model

Choose this if you want to look at individual reservations or include the channel manager and accounting. Our advice: start with length of stay by channel.

We brought visitor and behavioural data together in one model for sport and ticketing

We built a real-time dashboard for DutchSail and a platform for ticketing and behavioural data for See Tickets. We have worked in data and AI since 2016, as a partner of Microsoft and Databricks.

Book an introductory meeting

Which properties are included and which figures you’re missing: that’s where the first conversation starts

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your point of contact. In our first conversation, we’ll discuss how Apaleo works in your organisation and which figures you’re missing.

Which property would you like to see figures for first?

Tell us how many properties run on Apaleo and what other systems you use alongside it. We’ll reply by email, or we can arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Through the Apaleo API. A data-loading step retrieves reservations, groups, rates and financial data, then prepares them for the model. This means the PMS does not have to be queried again for every report.

You can read how we build each dashboard on the Power BI dashboards page.

The Core API for bookings, reservations, blocks and groups, inventory and rate plans, and the Finance API for folios and invoices. There is a separate Reports API for key metrics.

Apaleo documents everything at apaleo.dev.

With OAuth 2.0. For the data-loading step, we use a client with the client credentials flow and read-only access. Your administrator creates it in Apaleo.

That way, nobody has to share a personal password.

Occupancy, ADR and RevPAR by property and day, length of stay by channel, group block pickup, revenue from additional services and invoices by corporate client.

For the financial side, read about the financial dashboard.

Almost. With webhooks, you can subscribe to events in Apaleo, such as a new or amended reservation. We then retrieve only that change instead of everything again.

For reviewing performance afterwards, an update once a night is often enough.

It provides key metrics such as property performance with ADR and RevPAR, arrivals and revenue. We use it to check the figures in our own model, so both give the same results.

You can drill down to reservations in our own model.

Yes. If some of your hotels also run on Mews, read about the Mews Power BI dashboard. Both systems can feed into one model, using the same definitions.

That is useful for a group with hotels on different systems.

We define this in the model by property or region. A hotel manager sees their location, the revenue manager sees all properties, and the management team sees the overall figures.

We keep guest data out of the model if it is not needed.