Optimize gym visits with real-time occupancy data
Real-time occupancy data helps members make informed decisions about when to visit β avoiding peak-crowd times and improving the on-site experience. Zenoti exposes two occupancy features: Crowd Meter (current real-time occupancy) and Crowd History (weekly occupancy trends). Both are surfaced in the Customer Mobile App and the Webstore for member self-service planning.
Audience: Administrators who configure occupancy data for fitness centers.
On this page
- Before you begin
- Crowd Meter β real-time club capacity
- Crowd History β tracking occupancy trends
- Set maximum capacity for your studio
- Set average workout duration for your studio
- Impacts and considerations
- Related articles
Before you begin
- Required roles: Owner or Administrator.
- Gym capacity and average workout duration are configured at the center level.
- Third-party occupancy providers can integrate with Zenoti via partner setup (see Impacts and considerations).
Crowd Meter β real-time club capacity
Crowd Meter offers a real-time snapshot of club or gym occupancy in the Customer Mobile App and the Webstore. The reading combines on-site check-ins with data from any integrated third-party capacity-tracking system the studio has connected via Zenoti.
Members see a current-occupancy figure plus a percentage relative to the studio's maximum capacity, so they can decide whether to visit now or wait for a quieter window. The reading updates as members check in and out.
If you use a third-party occupancy provider, contact your Zenoti representative to enable the integration β the partner setup is configured per center.
Crowd History β tracking occupancy trends
Crowd History gives members a weekly view of typical occupancy patterns. Unlike Crowd Meter (which is instantaneous), Crowd History is a "Recent Average Activity" reading derived from the last six instances of each weekday. For example, the Wednesday view is the moving average across the last six Wednesdays for that specific studio.
The Crowd History reading refreshes every four hours, so the trend lags briefly immediately after a rush.
Set maximum capacity for your studio
The gym capacity field is mandatory β members rely on the maximum occupancy value to interpret the Crowd Meter percentage.
- At the center level, click the Configuration icon.
- Search for and select Gym max capacity from the Fitness section.
- Enter a capacity between 0 and 9999.
- Click Save.
Set average workout duration for your studio
Fitness studios do not typically have a formal check-out process, so this optional field lets each club declare a typical workout length for occupancy calculations.
- At the center level, click the Configuration icon.
- Search for and select Average workout duration (in minutes) from the Fitness section.
- Enter the average workout duration in minutes. The valid range is 0 to 180 minutes.
- Click Save.
Impacts and considerations
- If Gym max capacity is not set, Crowd Meter cannot render a meaningful percentage β members see current occupancy but not a capacity-relative view.
- Workout-duration estimates affect the rolling-window calculation: a low value overstates occupancy (each checked-in member is assumed to leave sooner), a high value understates it.
- Crowd History is updated every four hours; immediately after a rush, the displayed trend will lag briefly.
- Third-party occupancy integrations require a partner-level setup. Reach out to your Zenoti representative to configure the integration.
Troubleshooting
- Crowd Meter shows 0% despite members being on-site. Confirm that members are checking in on the Visits page or Kiosk β occupancy is derived from check-in events. If members bypass check-in (for example, a side entrance), occupancy under-reports.
- Crowd Meter reads above 100%. The gym max capacity may have been set below actual build-out capacity. Verify the Gym max capacity center-level setting. The feature accepts values 0β9999.
- Crowd History is empty. The rolling-average refresh job may not have completed for the previous interval. Reach out to your Zenoti representative β Support can re-run the aggregation on request.
- Third-party readings disagree with Zenoti readings. The third-party feed and Zenoti feed compute occupancy using different assumptions (badge-in/badge-out vs. check-in with workout-duration estimate). Small disagreements are expected; large disagreements indicate one side is missing check-in events.