The join_group event
join_group is a GA4 recommended event that records when a user joins a group, team, guild, or community within your product. It carries a group_id parameter identifying which group was joined. It is a social/engagement signal — useful for products where group membership drives retention — and like all recommended events it records the action and a non-identifying group reference, never the user's identity.
What this means
join_group is part of GA4's recommended events for general and social use cases. It marks that a user joined a group — a team, guild, channel, or community — and takes a group_id parameter identifying which one. Using the recommended event (rather than a custom name) means GA4 understands it consistently across reports and any future features built on recommended events.
Why membership is a useful signal
In products where belonging to a group increases stickiness — multiplayer games, communities, collaboration tools — join_group is an early indicator of healthy engagement. Correlating it with later retention shows whether group membership is a driver. The group_id should reference the group, never the member: it is fine to know which community grew, but the event must not encode who the person is.
- Recommended event with a group_id parameter
- Marks joining a team, guild, or community
- group_id references the group, not the member
How it appears in analytics and logs
join_group events show community formation. Users who fire join_group and then stay engaged suggest membership drives retention; few joins may mean the feature is hard to find.
Diagnostic use case
Track when users join groups or communities in your product, using join_group with a group_id, to study how membership relates to retention.
What WebmasterID can help detect
WebmasterID's convention matches: a membership event references the group by a stable non-PII id, never the individual who joined.
Common mistakes
- Inventing a custom name when join_group already exists.
- Storing a member identifier in group_id.
- Tracking joins but never correlating with retention.
Privacy and accuracy notes
join_group records a group_id, which should reference the group, not the member. No personal identifier belongs in its parameters. This is educational, not legal advice.
Related pages
- The sign_up event
sign_up is a GA4 recommended event that fires when a visitor creates an account. It carries a method parameter naming the registration mechanism, such as 'Google', 'email', or 'Apple'. It is a key activation event for products with accounts, marking the move from anonymous visitor to registered user — distinct from logging in, which returning users do repeatedly.
- The share event
share is a GA4 recommended event that fires when a visitor shares content. It carries method (the channel, such as 'Twitter' or 'email'), content_type, and an item_id. It measures sharing intent on your own site — the click of a share control — not whether the share was completed or what reach it earned off-platform.
- Recommended vs custom events
GA4 events come in three tiers: automatically collected, recommended, and custom. Automatic events fire without setup; recommended events have Google-defined names and parameters that unlock standard reports; custom events are ones you invent. The practical rule is to prefer a recommended name whenever one fits, because custom names miss out on prebuilt dimensions, reports, and predictive features.
- Event Explorer
Inspect social engagement events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.