Groups

Use Groups when user traits alone do not describe who should see a flow. Groups let you model accounts, workspaces, projects, properties, playlists, or any other object your users belong to.

getuserfeedback.com builds this graph from analytics events you already send. New matching events connect identified users to configured groups, then those groups become available in targeting.

What to configure

Open Groups settings. Groups settings are available to organization admins when Groups is enabled for the workspace.

Add one row for each kind of group you want to use.

Field	What to enter	Example
Name	The kind of group. Use the product word your team uses.	Account
Id	The event property that carries that group's id.	account_id

You can add more than one group type, such as Account, Workspace, and Project.

Send group data

The Groups settings page tells getuserfeedback.com which event properties represent the groups you care about. Each integration has its own payload shape for sending those properties.

Segment is supported today. See Segment as a source for track event and group call examples.

Target by groups

After matching events arrive, open the segment builder and add a user connection condition.

Examples:

• users in Accounts
• users in Accounts where plan is enterprise
• users in Workspaces where status is active
• users in Projects where lifecycle is beta

Groups work alongside normal user traits and event rules, so a segment can combine both:

• users who viewed Billing
• and are in Accounts where plan is enterprise

What can break

• The property name does not match. account_id and accountId are different properties.
• The event has no usable identity. We need an identity we can resolve to a person before we can connect that person to a group.
• Only new matching events apply. Changing Groups settings does not replay all historical analytics events.
• The group has no traits yet. A property like account_id can connect a user to an account, but group traits such as plan or status need to be sent by a supported integration.

Next

• Set up Segment as a source
• Personalization