Analytics

Every community has an analytics view that summarizes its members' expertise and activity. Every member of the community can read it — as the Signals tab of the community's People page, or at /community/<id>/analytics — so it's a shared picture, not an admin-only report.

Two modes

The dashboard auto-detects the mode that fits the community. It opens in Academic when at least 30% of the members have a publication, those members have two or more on average, and at least one member in five has three or more; otherwise it opens in Professional. A community of more than 500 members is judged on a random 500 of them. Analytics mode lets you switch between Academic (research mode) and Professional for the current session (the switch isn't saved).

Research mode

For research-oriented communities:

• Overview — publications, total citations, research areas, and authors; publications by year; recent highlights; most cited publications. Group research areas by fields, subfields, topics, or MeSH terms.
• Expertise Map — drill down from topics and domains to the authors behind them.
• Trends — publication output over time, rising and declining topics.

A time-range selector (all time, last 3 years, last 2 years, this year, a specific year, or a custom range) applies across the tabs.

Professional mode

For professional and industry communities:

• Snapshot — members, organizations, skills, and cities; Member Roles; and geographic distribution. Clicking a role's bar opens the People page filtered to the members in that role category, classified by the same rules as the chart. A city its members write with other capitals (LYON and Lyon) is one row of geographic distribution, as it is in the Network tab's clusters. The member map is on the People page's Map tab (below).
• Skills & Expertise — top skills (raw or clustered), seniority distribution, Hidden Gems (niche expertise shared by two or three members), skills and education by role, career backgrounds, and career flow. Top skills count a skill once: a difference of case does not split it, and a skill JOGL Network knows counts once across its English and French names and is shown in your language. The same goes for the skills figure on Snapshot.
• Network — education network, shared organizations (current or all-time), and geographic clusters sized for events (15+ members), dinners (5–14), or seeds.

Community fields

Under Overview in research mode and Snapshot in professional mode, a Community fields section charts the community's own list fields (Choice from a list and Several choices from a list), such as the questions of a sign-up form you imported. Each field gets a card with a bar per choice, counting the members who hold it, and says how many members have a value in it:

• A member who picked several choices of a field counts under each of them, so a field's bars can add up to more than its members.
• Other answers counts the members whose value names none of the field's choices, as it was imported.
• A choice archived since still shows while a member holds it, marked as archived.
• The members a card counts out of leave out those who archived their profile, so that total can be lower than the member count on Snapshot, which includes them.

The counts are those a member filter on that choice returns. They are read from the members' current values rather than from the cached analytics, so they do not wait for the daily job or the Refresh button. A field is charted while Show in analytics is on in its settings, which a new field starts with (see Custom fields), and never when it holds a sensitive kind of data. Admins see every such field; other members see the fields whose values are visible to members. The section is hidden when there is no such field. The same breakdown is in the API's and MCP's community analytics, as custom_fields.

Member map

Two surfaces plot members geographically, and they are not the same map:

• The Map tab of the People page groups the community's geocoded members into city buckets and plots up to 3,000 of them. The cap counts buckets, not members: it was sized against one community of 15,130 members whose 15,071 geocoded members fell into 2,342 city buckets, well inside the cap for that community. A community whose members are spread across more cities reaches the limit sooner, whatever its member count.
• The standalone /community/<id>/map route reads the cached analytics locations instead and plots up to 200.

Freshness

Analytics are computed in the background and cached, so the dashboard opens on the last computed figures rather than recalculating them on every visit.

• Once a community has five members, a daily job recomputes its analytics, skipping any day its member data has not changed.
• Opening the dashboard recomputes any figure more than a week old.
• In professional mode, the dashboard shows when its figures were last updated (Updated …) next to a Refresh button that recomputes them from the current member data. Use it after an import the daily job has not reached yet; allow about a minute for a large community.