Day 1: Group By

To kick things off, we're introducing Group By! Essentially, this allows you to track & gate features based on a nested property.

Example 1: Cursor - fast requests PER user

Take Cursor's team plan for instance. The org is paying for the subscription, but each user within that org is granted 500 fast requests per month. So in this case, the feature is tracked PER user.

Example 2: Supabase - GB disk size PER project

Another great example application of Group By is in Supabase's pricing. In their Pro plan, you can see that they have an allowance of 8GB disk size PER project. Once again, the organization pays the subscription, but can have multiple projects!

How it works

When creating a feature that should be grouped, simply specify the property to group it by:

1. /events

Next, when sending an event, simply specify the value of that field in the properties object. Below, we're specifying a particular user when sending a fast-request event

2. /entitled

Next, to check if a particular group (eg. user in this case) is entitled to the feature, simply pass in the property when calling entitled: