Content
- Registrations & Addressability
- Issue management
- Booking
- Registration codes
- App features
- Residents (App)
- Team members (Cockpit)
- KPIs
- Hist. KPIs
- What has changed with this update?
This article defines every metric shown to you in Allthings Insights, so you can correctly interpret the figures.
Registrations & Addressability
| Metric | Definition |
|---|---|
| Registration & Addressability Rate | Shows the registration and addressability rate as a percentage, split into three series: Registration rate (residential) — the percentage of units with at least one registered person, compared to all units in the selected scope. Registration rate (commercial) — the percentage of companies with at least one registered person, compared to all companies in the selected scope; this refers to companies, not units. Addressability rate (residential) — the percentage of units for which at least one addressable person is on file. A stored name or email address is enough — full registration is not required. Not available for purely commercial apps. |
| Number of registered persons | Shows the same three categories as an absolute number of persons instead of a percentage: Registrations (residential) — number of people who have completed registration in a rental relationship, as of the selected point in time (monthly view: end of each month). Registrations (commercial) — number of people with completed registration who are associated with a company; shows the number of people, not the number of companies. Addressable persons (residential) — number of people considered addressable (see above). |
Issue management
| Metric | Definition |
|---|---|
| Tickets created | Number of tickets created in the selected period, grouped by category. |
| Tickets closed | Number of tickets created in the selected period that have reached the status "Closed", grouped by category. |
| Avg. Time to First Response | Average business time (Monday to Friday) between ticket creation and the first response from a person in property management with access to the affected app. Only calculated for tickets that are already closed. |
| Avg. Time to Full Resolution | Average business time (Monday to Friday) between ticket creation and full resolution. Every ticket counts once in the average calculation. |
Booking
| Metric | Definition |
|---|---|
| Confirmed bookings | Number of confirmed bookings for bookable assets in the selected period. |
| Total revenue | Sum of booking prices in the selected period. Shown separately per original currency of the bookable asset — there is no automatic conversion into a single currency. Use the currency filter to see only the corresponding bookings. |
Registration codes
This tab shows all registration codes issued for your apps. Because the list can be very large, it's only displayed once you enter a search term — you can search by code, the resident's name or email address, unit, address (incl. street, postal code, city), property, or app name.
- Code: the registration code itself.
- Used on: the date the code was redeemed, if already used.
- Permanent: indicates whether the code can be used more than once.
- Email/name of the resident: the person who redeemed the code.
- Period, unit, address, property, app: the code's assignment.
The data is refreshed roughly every 30 minutes.
App features
Overview of all features enabled in your apps (e.g. Marketplace, Concierge, Documents, Sharing place).
- Type: the technical name of the feature.
- Label (DE/EN/FR/…): the displayed name per language — only the languages enabled for the app are shown.
- Enabled: indicates whether the feature is currently active.
- Channels: the number of levels (app, property, building, or unit) on which the feature is visible.
The data is shown live, with no delay.
Residents (App)
Overview of all users of your apps, split into the categories Commercial, Residential, All residents, and No period/company (people not currently associated with an app).
- Email verified: indicates whether the email address has been confirmed.
- Created / Last login: registration date and most recent login.
- Type: the person's account type.
Use the search field to search specifically by name, email address, or ID.
Team members (Cockpit)
Overview of all team members with access to your apps in Cockpit, split into Active team members, All team members, Team members of external companies, and Commercial tenant admins.
- Permission: the assigned permission, shown with its label as used in Cockpit (e.g. "Issue management | Manage tickets").
- Channel type / Channel name: the level (app, property, building, or unit) the permission applies to.
- Channel created / Channel active: the date the access was created or activated.
Note: the filter currently matches the permission's technical name (e.g. "app-admin" rather than "App Admin"); this technical name is shown as a tooltip when you hover over the cell.
KPIs
Current metrics for your apps:
- # Published / Private solutions: number of solutions by visibility.
- # Enabled connectors: number of active connectors (published & private).
- # Connected units: number of units reached via connectors or classic app features. A unit can be counted more than once if it's reachable through several connectors.
- 90-day trend / Solutions: the development of connected units, plus the 20 solutions with the widest reach.
The figures are refreshed once a day, so they reflect the previous day's status.
Hist. KPIs
Shows the monthly trend of key metrics for your apps:
- Monthly active team members: the number of team members who, in a given month, both held a permission on the app and were active on it.
- Users / Units / Buildings / Apps: the development of these metrics over the past 12 months. Users are recalculated monthly, the other values show the current status.
Use the Asset class filter and the date range (From/To) to narrow down the view.
Note: historical data is only available from August 2026 onward, since data collection started at that point.
What has changed with this update?
The "Insights" analytics were moved onto a new technical foundation in mid-2026. They continue to provide the analytics you know, but now make it much easier to add further analytics. Feel free to let us know what would interest you.
- More accurate averages: "Avg. Time to First Response" and "Avg. Time to Full Resolution" are now calculated per ticket — every ticket counts equally, instead of first being averaged per category and building. This gives more precise values, especially for categories with few tickets.
- Broader coverage for "Avg. Time to First Response": the first reply from any authorized person in property management now counts, not just a fixed set of people.
- Corrected revenue calculation: for bookable assets assigned to multiple properties or groups, revenue is now counted correctly instead of sometimes being counted more than once.
- A leaner overview: the "Pinboard" (posts, comments, likes, sentiment analysis) and "Engagement" (engagement rate) areas have been removed, as they were rarely used.
- New technical foundation: Registrations & Addressability, Issue management, and Booking now run on a new, extensible data foundation — the definitions and figures remain the same in substance.
Interesting Notes:
- Values for the last 1–2 months for "Avg. Time to First Response" and "Avg. Time to Full Resolution" are provisional: only tickets that are already closed are included. As further tickets from this period are closed, the displayed average may still change retroactively.
- In Issue management, the daily view covers the last 12 months, and the monthly view covers the last 2 years.
- Revenue is not converted into a single currency.