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 or first-party SDK relationship observations. These connections make Groups 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.

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.

First-party JavaScript, React, and React Native clients can record the same relationship directly:

const relationship = {from: { collection: "user", id: "user_123" },to: { collection: "account", id: "acct_123" },};await client.graph.connect(relationship);await client.graph.disconnect(relationship);

disconnect() ends the connection established by earlier observations, regardless of which source recorded them. A later connect() can establish the connection again. Collection keys use lowercase kebab-case and IDs must be nonblank. Invalid relationship properties remain analytics events but do not update the graph.

Build a group audience

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

Examples:

• User in Accounts
• User not 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 a segment can combine both:

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

Each evaluated user is either in or not in the segment. A user who has not been evaluated yet satisfies neither condition. The segment page shows when the audience was last processed, whether processing is underway or needs attention, and an action to refresh the audience using the latest data available.

You can inspect these audiences, use them for a one-time manual Flow send, or use them as the audience for a recurring scheduled Flow. Each send uses the users who are in, or not in, the selected segment when its audience is planned. Membership changes after planning affect future sends, not the already planned recipient set. If the selected segment is archived or its definition can no longer be evaluated before delivery, that send may be suppressed. For an event-triggered Flow without a delay, you can use these segments in Audience to choose who enters when the event occurs. That audience is frozen for the event. Conditions remain delivery-time filters and can remove users from the frozen audience. Delayed event rules support Conditions but not Audience; they check Conditions before queueing the send and again before delivery. Relationship-dependent audiences are not available for segment triggers or runtime broadcasts.

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