Analytics

Analytics (under Admin in the sidebar, or G then A) shows owners and admins how the guild is doing, with numbers you can act on. Each report covers the last 7, 30, 90, 180 or 365 days, with the period before it for comparison, and counts days in your guild's time zone.

How the numbers are kept

Most of Analytics is counted from what already happens in the dashboard: posts, votes, RSVPs, loot claims and awards, events and members. Two things are recorded just for it:

• Daily activity. Each day a member opens the dashboard is recorded once. Days before Analytics existed were filled in from what members did (posting, voting, RSVPing, claiming) and their last visit, so there is some history from the start.
• Joins and leaves. When someone joins or leaves (or is removed), it's noted with the date, so leavers can be counted and joining cohorts followed. Members who were already in the guild count as having joined when their account was created.

The reports

Every report starts with a row of headline numbers. Most show the previous period's value and the change, so you can tell at a glance whether things are moving. Hover a number for how it's counted.

Every chart has a table view (the icon in its corner) and a CSV download, so you can read the exact values or take them into a spreadsheet.

Activity

• Active members per day, with how many posted, voted, RSVP'd or claimed loot that day.
• Busiest hours: a week-by-hour grid of when members do things, in guild time. Use it to pick raid nights, post announcements when people are around, and schedule events people will actually see.
• Most active members: days active, posts, votes, RSVPs and claims, and when each was last seen.

Members

• Members over time, with joins and leaves per day.
• Retention by joining month: of everyone who joined in a month, how many were still members 30 and 90 days later, how many are still here, and how many of those were active in the last 30 days. A cohort with high 30-day retention but low 90-day retention tells you people stay through onboarding and drift afterwards.
• By role and by rank.
• Gone quiet: members not seen for 30 days, or never. A good list to reach out to before they leave.
• Recent leavers, with how long they stayed.

Events

• Turnout per event: going, maybe, declined and no reply for every event held in the period.
• Best days and hours: how many events were held on each weekday and hour, and the average turnout. Schedule where the bars are tallest.
• Most reliable attendees, and how many members didn't RSVP to anything.
• Upcoming events with their current RSVPs.

Forum

• Threads and posts per day, and posts by category.
• Time to first reply (median) and unanswered threads, so questions don't go cold.
• Top posters and what share of posts the busiest five write. A high share means the forum depends on a few voices; a welcome thread or a question of the week can widen it.
• Hot threads: the most replied-to threads of the period.

Loot

Only for games with loot.

• Hauls, items looted, handed out and sent to storage, and how long hauls take to finalize.
• Share of members who received loot: a quick fairness check.
• By category, top recipients (with their need and want claims), need versus want, and the most contested items with who got them.

Recruitment

• Funnel: of everyone who applied in the period, how many were accepted, used their invite, are still members, and were active in the last 30 days. A big drop between "accepted" and "used their invite" means invites are going astray; a drop after that means onboarding isn't landing.
• Time to decide (median) and waiting for a decision, oldest first. Applicants give up when they wait.
• Who reviews, and every invite link made in the period with whether it was used or expired.

Polls

• Turnout per poll: the share of members who could vote (at their rank) that did, with the leading option.
• Didn't vote: members who voted in nothing this period, most senior first.
• Who makes polls and the most engaged voters.

Storage

• Plan storage: how much of the plan's media storage is used, and at this period's pace how long until it's full.
• Storage over time (files still kept, by upload day), by kind, by folder, by uploader, and the largest files to look at first when space runs short.

Tips and tricks

• Check the busiest hours grid before moving raid night. If Tuesday 20:00 guild time lights up, that's when people are around.
• Use Gone quiet as a weekly ritual: a short message to three or four names keeps members from drifting away unnoticed.
• Compare Active this month with Members. If a third of members haven't opened the dashboard in 30 days, the website and Discord announcements are doing the work, and that's fine, but recruiting more members won't fix a quiet forum.
• A falling RSVP response rate usually means too many invites. Invite the roster that's actually expected, not everyone.
• Download a CSV of the members series each month and keep it; the guild's own history is the best benchmark it will ever have.
• If Storage says the plan is full in under 90 days, sort the largest files first: one raid video is usually worth a hundred screenshots.
• A poll with turnout under a third means most members never saw it. Turn on Show on website and post it to Discord.