Groups let you organize users into meaningful collections and track behavior at the group level instead of just individual users. This is particularly valuable for B2B products where understanding team, workspace, or organization-level activity is crucial.

When you create groups, you can analyze metrics like group engagement, retention, and feature adoption. You can also segment your analytics by group properties to understand which types of organizations succeed with your product.

Here are some examples:

Workspaces (for productivity tools like Asana or Monday): Track metrics like workspace activity, average team size, and collaboration patterns across different organizations.

Accounts (for CRM or sales tools): Analyze account health, user adoption within accounts, and revenue metrics at the customer level.

Stores (for e-commerce platforms): Monitor store performance, product catalog usage, and merchant engagement across different retail locations.

The key is identifying the organizational units that matter most for your business model and user experience. By default, we create a default group called "Workspaces" so that you can easily get started with June.

Code

Replace GROUP_ID with a unique identifier, preferably the workspace ID from your database. Including the workspace's name is also suggested, along with any additional "traits" like avatar, company_size etc. This information will appear on the workspace's profile and can be used to filter workspaces in reports.

💡 Not sure which traits to add? We automatically map some standard ones: check out our guide

1
window.analytics.group('GROUP_ID', {
2
  name: 'Acme Inc',
3
  // Optional
4
  avatar: 'https://avatar.com/asd809sdhoif9as10nc29.png'
5
  // Add anything else about the company here
6
});

1
analytics.group('GROUP_ID',
2
{
3
  name: 'Acme Inc',
4
  // Optional
5
  avatar: 'https://avatar.com/asd809sdhoif9as10nc29.png'
6
  // Add anything else about the company here
7
});

1
analytics.group({
2
  userId: 'USER_ID',
3
  groupId: 'GROUP_ID',
4
  traits: {
5
    name: 'Acme Inc',
6
    // Optional
7
    avatar: 'https://avatar.com/asd809sdhoif9as10nc29.png'
8
    // Add anything else about the company here
9
  },
10
});

1
analytics.group(
2
  user_id="USER_ID",
3
  group_id="GROUP_ID",
4
  traits={
5
    "name": "Acme Inc",
6
    # Optional
7
    "avatar": "https://avatar.com/0sd9fsd8y97a0sf99asd.png",
8
    # Add anything else about the company here
9
  },
10
)

1
Analytics.group(
2
  user_id: 'USER_ID',
3
  group_id: 'GROUP_ID',
4
  traits: {
5
    name: "Acme Inc",
6
    # Optional
7
    avatar: "https://avatar.com/d78979as8hlsa9088f.png"
8
    # Add anything else about the company here
9
  }
10
)

1
curl https://api.june.so/sdk/group
2
-H "Content-Type: application/json"
3
-H "Authorization: Basic YOUR_WRITE_KEY"
4
-X POST
5

6
{
7
  "userId": "USER_ID",
8
  "groupId": "GROUP_ID",
9
  "traits": {
10
    "name": "Acme Inc"
11
  },
12
  "timestamp": "2012-12-02T00:31:38.208Z"
13
}

You can also create custom groups to track other organizational units, like accounts, stores, teams, etc. For example, if you're building a project management tool, you can measure engagement across different departments. This helps you understand:

• Which departments (e.g., engineering vs marketing) use the task collaboration features most actively

• How many team members are regularly participating in project discussions each month

• Compare feature adoption between different teams (e.g., which teams use the kanban board vs those who mainly use task assignments)

You can create a new group by clicking the "Create object" button in the top right corner of your object settings.

You can then define the singular name, plural name, and group type to create the new group. For example, if you want to track metrics at the department level within a single company, you can put "Department" as the singular name, "Departments" as the plural name, and "department" as the group type.

💡 group_type You'll need to use the group type later in the .group and .track methods to identify and track events for the correct group.

Code

Replace USER_ID and GROUP_ID with a unique identifier, preferably the user ID and workspace ID from your database. Including the company's name is also suggested, along with any additional "traits" like avatar, company_size etc. This information will appear on the companies profile and can be used to filter companies in reports.

💡 Not sure which traits to add? We automatically map some standard ones: check out our guide

1
window.analytics.group('GROUP_ID', {
2
  group_type: 'department',
3
  name: 'Engineering',
4
  headcount: 25,
5
  location: 'San Francisco',
6
  budget: 1000000
7
  // Add anything else about the department here
8
});

1
analytics.group('GROUP_ID', {
2
  group_type: 'department',
3
  name: 'Engineering',
4
  headcount: 25,
5
  location: 'San Francisco',
6
  budget: 1000000
7
  // Add anything else about the department here
8
});

1
analytics.group({
2
  groupId: 'GROUP_ID',
3
  traits: {
4
    group_type: 'department',
5
    name: 'Engineering',
6
    headcount: 25,
7
    location: 'San Francisco',
8
    budget: 1000000
9
    // Add anything else about the department here
10
  }
11
});

1
analytics.group(
2
  group_id="GROUP_ID",
3
  traits={
4
    "group_type": "department",
5
    "name": "Engineering",
6
    "headcount": 25,
7
    "location": "San Francisco",
8
    "budget": 1000000,
9
    # Add anything else about the department here
10
  },
11
)

1
Analytics.group(
2
  group_id: 'GROUP_ID',
3
  traits: {
4
    group_type: "department",
5
    name: "Engineering",
6
    headcount: 25,
7
    location: "San Francisco",
8
    budget: 1000000
9
    # Add anything else about the department here
10
  }
11
)

1
curl https://api.june.so/sdk/group
2
-H "Content-Type: application/json"
3
-H "Authorization: Basic YOUR_WRITE_KEY"
4
-X POST
5

6
{
7
  "groupId": "GROUP_ID",
8
  "traits": {
9
    "group_type": "department",
10
    "name": "Engineering",
11
    "headcount": 25,
12
    "location": "San Francisco",
13
    "budget": 1000000,
14
    # Add anything else about the department here
15
  },
16
  "timestamp": "2012-12-02T00:31:38.208Z"
17
}

Once you've implemented the group method in your codebase, it's time to track what your groups are doing in your product.