Groups

Use Groups when user traits alone do not describe the audiences you want to inspect. Groups let you model accounts, workspaces, projects, properties, playlists, or any other object your users belong to.

getuserfeedback.com builds this graph from supported integration group data. Segment Group calls can connect known users to configured Groups, then those Groups become available in the segment builder.

What to configure

Open Groups settings. Organization admins can add the Groups their workspace sends.

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

Field	What to enter	Example
Name	The human-readable Group name your team uses.	Accounts
Group ID	The stable lowercase key integrations use for that Group.	account

You can add more than one Group, such as Accounts, Workspaces, and Projects. The name is display-only. Renaming it does not change the Group ID or the relationships integrations send.

Send group data

For Segment, use the same Group ID in the Segment source settings. A Segment Group call then supplies a particular group's groupId, its traits, and the known userId connected to it.

For example, a configured Group can have the name Accounts and ID account. A Group call with groupId: "acct_123" refers to one account in that configured Group. See Segment as a source for the payload shape.

Group calls are positive, additive observations. Connecting the same user to a second group instance does not replace the earlier connection or declare the user's complete group membership.

Build a group audience

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

Examples:

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

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

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

Group-derived membership is best effort and may be stale. You can use it to inspect and compare audiences, but it cannot drive flows, deliveries, or other automated targeting.

What can break

• The Group ID does not match. The ID in Segment source settings must match the ID in Groups settings exactly.
• 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.
• The user is not known yet. A Group call does not create a user profile; its userId must already resolve to a user in the workspace.
• Only new Group calls apply. Changing Groups settings does not replay all historical events.
• Removing a Group is not data deletion. It hides that Group from audience authoring and stops new calls from updating the graph. Existing graph data and the Segment source's selected Group ID remain. Re-adding the same Group ID makes the retained graph data available again.
• The group has no traits yet. Send group traits such as plan or status in the Segment Group call.

Next

• Set up Segment as a source
• Personalization