Most advice about meeting games is written from opinion. This guide does something different: it reports what actually happened in Meeting Games over 28 days, using aggregated and anonymized analytics, and then says what you can and cannot conclude from it.
The sample is small, and we say so throughout. Treat the numbers as one product's usage pattern, not an industry benchmark.
How we measured
- Source: Google Analytics 4 for meeting-games.com.
- Period: 20 September to 17 October 2026 (28 days).
- Filtering: Only traffic on the production hostname is counted. About 58 sessions came from local development and testing, and they are excluded.
- Aggregation: Event counts and user counts only. No room contents, answers, nicknames, or individual player records are used.
- Known limits: Analytics under-counts visitors who decline cookies or use blockers, and visitors in Europe, the UK, and Switzerland are counted only after they accept cookies. Event counts are not the same as unique rooms, so ratios below are approximations.
The headline numbers
| Measure | Value (28 days) |
|---|---|
| Sessions on the production site | about 1,217 |
| Rooms created (events) | 249 |
| Room joins (events) | 523 |
| Games started (events) | 153 |
| Users who submitted at least one answer | 336 |
| Total answers submitted | 4,005 |
| Invite link copied (events) | 188 |
| "Play again" clicks | 53 |
| "Try another game" clicks | 43 |
Two ratios are worth looking at, with the caveat that they divide event counts:
- About two joins per created room (523 joins for 249 rooms). On average a room is a small group, not a crowd, although an average can hide a few large rooms.
- About six in ten rooms led to a started game (153 starts for 249 rooms). Many rooms are created and then never played, which is a normal pattern when someone is testing the tool or the group does not show up. It is also the biggest opportunity: the lobby is where sessions are lost.
When teams play
| Day | Room joins | Share of joins |
|---|---|---|
| Monday | 76 | 15% |
| Tuesday | 96 | 18% |
| Wednesday | 89 | 17% |
| Thursday | 95 | 18% |
| Friday | 157 | 30% |
| Saturday | 1 | 0% |
| Sunday | 9 | 2% |
About 98% of joins and 98% of answers happened on weekdays. That matches the intended use: games inside work meetings, not weekend socials.
Friday stands out, with roughly 30% of joins and 31% of answers. We cannot tell from this data why. A reasonable guess is that Friday calls are more social, but that is an interpretation, not a finding. If you host recurring sessions, the practical takeaway is modest: Friday wrap-ups are a common slot for a longer, more social game, while Monday to Thursday use is spread fairly evenly.
Who joins and on what device
- Desktop: about 82% of sessions (1,003).
- Mobile: about 17% (204).
- Tablet: under 1% (9).
Average session length was about 7.6 minutes on desktop and about 4.8 minutes on mobile. Returning visitors averaged about 10 minutes per session against about 6.8 minutes for new visitors.
What this can and cannot tell you: it counts sessions on the whole site, not only people in a game, and it does not separate hosts from players. So it does not prove that hosts use desktops. It does suggest that you should expect many participants to be on a laptop beside the call, and that the joining experience on phones needs to be quick, because phone sessions are shorter.
What people do after a game
Some groups keep going: 53 "Play again" clicks and 43 "Try another game" clicks were recorded. We cannot tell how many distinct rooms those came from, or how many groups played a single game and stopped, so we draw no conclusion from them.
What this means for running your own session
These are suggestions grounded in the pattern above, not guarantees:
- Plan for a small room. If the average room is only a couple of people joining the host, a game that only works with 30 players is a poor default. Pick formats that are fine with a handful of people, like Would You Rather or This or That.
- Fill the lobby before you announce the game. Because many rooms never start, paste the link into the call chat early and start when people are in. See the Google Meet setup guide for the exact flow.
- Expect laptops beside the call, and phones for some. Share your screen so the whole room sees the same question, and keep prompts short enough to read on a phone.
- Match the game to the slot. Short formats suit Monday to Thursday openers. A longer trivia round is a better fit for a Friday wrap-up. The free online team games guide lists formats by time.
What we cannot say
- We cannot say how many people were in each room, how long each game lasted, or which game was played most, because those details are not recorded as per-room analytics in a form we can report accurately.
- We cannot say whether games improved any team's meetings.
- With about 1,200 sessions, week-to-week variation is large, and one big team joining on one day moves the totals.
We will only publish numbers here that we can define and reproduce. If you spot a number that looks wrong, tell us through the contact page.