Group analytics

Groups are a powerful feature in PostHog that aggregate events based on entities, such as organizations or companies. They enable you to analyze trends, insights, and dashboards at an entity-level, as opposed to a user-level.

To clarify what we mean, let's look at a few examples:

1. For B2B SaaS apps, you can create a company group type. This enables you to aggregate events at a company-level, and calculate metrics such as number of daily active companies, company churn rate, or how many companies have adopted a new feature.```

2. For collaborative, project-based apps like Notion, Jira, or Figma, you can create a project group type. This enables you to calculate metrics like project pageviews, users per project, and project engagement.

3. For a communication app like Slack, you can create a channel group type. This enables you to measure metrics like average number of messages per channel, number of monthly active channels, or total number of channel participants.

4. For a social media app like Twitter, you can create a post group type. This enables you to measure average number of replies per post, or total count of unique posters per month.

The difference between groups and cohorts

Groups are often confused with cohorts, but they each serve different purposes:

• Groups aggregate events, and do not necessarily have to be connected to a user.
• Cohorts represent a specific set of users – e.g., a list of users that all belong to the same company.

Groups require additional code in your app to set up, while cohorts are created in PostHog and don't require additional code. This makes cohorts easier to use and quicker to get started. If your only goal is to create a list of users with something in common, we recommend cohorts instead of groups.```

How to create groups

Groups are created and defined in your code when sending events.

In the example below, we create a group type company. Then, for each company, we set the group key as the unique identifier for that specific company. This can be anything that helps you identify it, such as ID or domain.

We advise against using the name of the company (or any other group) as the key, because that's rarely guaranteed to be unique, and thus can affect the quality of analytics data.

// All events for that session will be associated with company `company_id_on_your_db`
posthog.group('company', 'company_id_in_your_db');

posthog.capture('user_signed_up')

Tip: When specifying the group type, use the singular version for clarity (company instead of companies).

We now have one company-type group with a key company_id_in_your_db. When we send the event user_signed_up, it will be attached to this newly created group.

A single event can only belong to a single group per group type. To elaborate what we mean, we'll continue using the example above:

• It is NOT possible to assign the a single user_signed_up event to two companies at the same time.
• It is possible to assign this event to a different group type, for example channel or post, in addition to the company group type.

// ❌ Not possible
posthog.group('company', 'company_id_in_your_db');
posthog.group('company', 'another_company_id_in_your_db');
posthog.capture('user_signed_up')

// ✅ Allowed
posthog.group('company', 'company_id_in_your_db');
posthog.group('channel', 'channel_id_in_your_db');
posthog.capture('user_signed_up')

Group type limit: There's a hard limit of 5 group types within PostHog, although within each group type you can have an unlimited number of groups.

Setting and updating group properties

In the same way that every user can have properties associated with them, every group can have properties associated with it.

Continuing with the previous example of using company as our group type, we'll add company_name, date_joined, and subscription as additional properties.

Note: You must include at least one group property for a group to be visible in the "Persons & Groups" tab.

posthog.group('company', 'company_id_in_your_db', {
    name: 'PostHog',
    subscription: "subscription",
    date_joined: '2020-01-23T00:00:00.000Z'
});

Properties on groups behave in the same way as properties on persons. They can also be used within experiments and feature flags to rollout features to specific groups.

Note: The PostHog UI identifies a group using the name property. If the name property is not found, it falls back to the group key.

For more on implementing group analytics, check out our guide on frontend vs backend group analytics implementations.

Using groups in PostHog

Now that we have created our first group type, we can take a look at how to use groups within PostHog.

Viewing groups and their properties

To view groups and their properties, head to the "Persons and Groups" tab on the navigation bar.

From here, you can select the group type you are interested in and view the groups and properties (by clicking the chevrons on the left).

You can also click on a specific group to see information such as all the events that have been sent by this group. From there, in the "Related people & groups" tab, you can also see all of the persons who have sent events that were associated with this group, as well as all the other groups associated with the events.

How to view group insights

You can use groups in insights to view aggregated events based on group type.

For example, let's say that we wanted to see a graph showing how many different organizations have signed up recently:

To do this, expand the menu next to the event you've chosen. This lists of all the group types available. Next, select the option for "Unique" with your group type name, such as "Unique organizations." This shows a graph with the total number of groups (organizations) that have signed up (as opposed to individual users).

Using groups with funnels

Another place where group analytics can be used is within funnels.

For example, you may want to understand how organizations move from their first visit to eventually signing up. You can do this by setting the "Aggregating by" field to "Unique organizations."

This shows how many organizations have made it through, as well as the percentage of organizations that dropped off. It's also possible to see exactly which specific groups dropped off at each step.

Using groups with feature flags

Groups in feature flags enable you to rollout a feature by group type (like company), instead of users.

To do this, create a feature flag as you normally would, and select the group type you wish to "Match by", using the drop down in the "Release conditions" section:

You also need to update your event tracking code for the feature flag to determine the groups of the current user.

// Make sure you have called posthog.group() earlier in that session

if (posthog.isFeatureEnabled('new-groups-feature')) {
    // Do something
}

Renaming group types

You can change how group types are displayed in the insights interface and throughout PostHog by in project settings.

Limitations

• A maximum of 5 group types can be created per project.
• Multiple groups of the same type cannot assigned to a single event (e.g., Company A & Company B).
• Groups are not currently supported for the following insights:
  • Lifecycle - Expected soon.
  • User paths - These only support user level analytics.
• Only groups with known properties are shown under 'Persons & groups'.
• Currently there is no functionality within the app to delete groups. If you need to delete a group for privacy or security reasons, please use the support modal.```

Further reading

• When and how to run group-targeted A/B tests