Average Session Length: How to Calculate and Read It

Average Session Length in a Gaming Club: Formula, Where to Find It, How to Improve

Average session length is the total played time for a period divided by the number of sessions. In IZI the metric is called Average Session Length (field avgSessionDuration) and lives in Analytics → Session Report inside the KPI block. The value is expressed in hours and recalculates automatically when you change the date range. Extensions count as part of the same session — the session counter does not increment — so the average reflects the real play interval from first start to final end. Next to the number, IZI shows a percentage change vs. your chosen comparison period, giving you an instant trend signal without manual calculation. Alongside it you get related cards: total session count, total played hours, share of short sessions (under 10 minutes), and average hall occupancy — together they give a complete picture of how your capacity is being used.

Why Track Average Session Length

For a club owner this is one of the core monetization indicators for gaming time. When billing is time-based, revenue is directly proportional to average session length: at the same prices and the same footfall, adding 20 minutes to the average session grows gaming-time revenue by a proportional amount.

Three key use cases:

Situation	What to check	What it means
Short sessions increasing	”Sessions < 10 min” card	Technical failures, incomplete payments, or connectivity issues
Average length falling	avgSessionDuration with period comparison	Dropping engagement, audience mix shift, or a new competitor nearby
Low occupancy despite long sessions	avgLoadPercent + sessionCount	Not enough visitors, not short visits — a traffic/marketing problem

The Formula and How IZI Computes It

Average session length (hours) = Total played minutes for the period ÷ Session count ÷ 60

IZI calculates this on the analytics engine: avgDurationMinutes is computed as AVG(effective_end_at - effective_start_at) over completed and active sessions, then divided by 60 on the front end to display hours. The Session Report uses a complementary approach — playHours / sessionCount, where playHours is the sum of all session durations. Both methods produce identical results for completed sessions.

For active sessions, effective_end_at is replaced with the current timestamp, which is why the real-time figure can be slightly higher than the end-of-day value.

How to Find the Metric in the CRM

1. Open the target club in IZI CRM.
2. Go to Analytics in the sidebar.
3. Select the Session Report tab.
4. In the top KPI block, locate the Average Session Length card.
5. Next to the numeric value you will see the percentage change vs. the comparison period, with an up or down arrow.

To filter by zone, use the All Zones dropdown at the top of the page — it lets you compare PC, console, or VIP zones side by side.

To export the data, click the Export button. The download includes a breakdown by zone and device.

Related Metrics in the Same Section

Average session length does not work in isolation. These are the cards you should always read alongside it.

Played Hours and Session Count

The Played Hours and Session Count cards are the numerator and denominator of the formula. If average length rises but played hours stay flat, session count has dropped — that is a different problem with a different solution.

Sessions Under 10 Minutes

The Sessions < 10 min card counts sessions shorter than 10 minutes. IZI surfaces these separately because they distort the average and almost never generate meaningful revenue. The healthy threshold varies by club, but a share above 10–15% of total sessions is a signal worth investigating.

Common causes:

• A client paid but the device failed to start (technical fault)
• A cashier error when opening the session
• The client changed their mind and requested a refund

Average Hall Occupancy

The Average Occupancy % card shows what share of device working time was actually in use. Formula: played minutes ÷ (shift time × number of devices) × 100. An occupancy of 70–85% is considered high for most club formats — above that, clients start encountering wait times for seats.

For more on how occupancy is calculated, see How to Read the Hall Occupancy Report.

How to Interpret Changes

The percentage change next to each KPI card makes it easy to spot trends. That said, always read the number in context before drawing conclusions.

Average session length increased:

• A positive signal when played hours and revenue also grew.
• Neutral if only the average length increased while session count fell — the audience has narrowed to heavy players, not grown overall.

Average session length decreased:

• Check whether the share of short sessions rose. If yes, look for technical issues.
• Check whether the audience mix changed: a spike in first-time or unregistered visitors often pulls the average down.

Average session length stable but occupancy low:

• The issue is not session length, it is footfall. Focus energy on acquisition and repeat visit frequency.

Zone-Level Breakdown

At the bottom of the Session Report you will find the Occupancy by Zone table with columns: zone, device, hours played, occupancy %, number of devices, session count, and unique clients.

This lets you compare average session length and occupancy across zones. A common pattern: the console zone produces longer sessions than PC but lower traffic volume. Knowing this helps you make more precise decisions about expanding zones or redistributing devices.

The Hourly Heat Map

The Average Occupied Devices by Hour tab (heat map) shows which hours and days of the week carry the highest load. The redder the cell, the higher the average occupancy in that time slot.

The heat map complements average session length: instead of a single average across the whole period, it shows how load is distributed within the week. If Friday evening runs at near-full capacity for four hours while Monday morning barely registers, that is a direct input for differential pricing or targeted promotions by day.

For more on working with analytics periods, see Comparing Periods.

Parametric Benchmarks

Exact numbers vary by region, club format, and pricing model. These region-agnostic reference points apply regardless of market:

• Average session length above last month’s average at a stable session count indicates growing engagement.
• Sessions < 10 min share below 5% is a sign of a technically healthy operation.
• Occupancy in the 60–80% range is a comfortable operating window for most formats: enough revenue without queues forming.

To compare this metric across multiple locations in a network, use Organization Analytics — it provides a consolidated view across all clubs.

Frequently Asked Questions

Do session extensions affect the session counter? No. In IZI an extension is part of the same session. The session count does not increase, and time is recorded continuously from effective_start_at to the actual end.

Do bonus sessions count toward average session length? Yes, provided the session has been started and has a status of STARTED or ENDED. The payment method does not affect whether a session is included in the metric.

Can I see average session length by tariff? The Session Report does not offer direct tariff-level filtering, but zone-level breakdown is a useful proxy: if a zone runs only one tariff, the zone metric gives you the slice you need. For more on tariff structure, see Sessions Overview.

How often does the data update? In real time for active sessions (using the current timestamp in place of effective_end_at). Completed sessions appear immediately after they end.