getuserfeedback.
Docs

Segment as a source

Forward identify, track, and group events from Segment into getuserfeedback.com for targeting and context.

Last reviewed

Segment as a source

Use this when you already track users with Segment and want those traits, events, and group context to drive who sees a flow, with full context on each response.

Every identify, track, and group event Segment sends arrives in getuserfeedback.com. Targeting can use user traits and events right away, and Segment Group calls can update the account, workspace, or other group profile you configure.

1. Create the integration

  1. Open Integrations and click New integration.
  2. Under Data in, choose Segment.
  3. Click Continue.

You'll land on the integration detail page. Copy the Webhook URL shown there. It points at the ingestion subdomain and looks like:

https://segment.ingest.getuserfeedback.com/int_<id>

The URL is unique per integration. The page also shows a Shared secret — copy it too. Segment signs every request with it, and we reject any request that isn't signed with the matching secret.

2. Add a Webhook destination in Segment

  1. In Segment, open Connections → Destinations → Add destination.
  2. Search for Webhooks (Actions) and select the catalog entry.
  3. Pick the Source that sends the traffic you want to forward.
  4. Paste the Webhook URL from step 1 into the destination's Webhook URL setting.
  5. In the destination's advanced settings, paste the Shared secret from step 1 into Segment's Shared Secret field.
  6. Enable the destination.

Segment will start streaming signed events to getuserfeedback.com.

3. Verify it's working

Send a test event from Segment, then open Users in getuserfeedback.com. The user should appear within a few seconds. If nothing shows up, see What can break.

4. Connect users to groups from track properties

If your Segment track events include context like account_id or workspace_id, configure those properties in Groups. New matching events can connect identified users to those groups for targeting.

{"type": "track","event": "Feature Used","userId": "user_123","properties": {"account_id": "acct_123"}}

If account_id is configured for Account, this event connects user_123 to Account acct_123. Include the primary user identity your workspace uses for targeting. For most Segment sources, that is userId.

5. Configure Segment Group calls

If you send native Segment group calls, first configure the group type in Groups, then open the integration settings and set the matching Group key. For example, set both to account. Group keys use lowercase kebab-case.

The Segment groupId becomes the group id, and traits update that group's traits:

analytics.group("org_123", {plan: "enterprise",seats: 42,});

Leave the Group key blank to use the default group key. A Group call is stored as an event either way, but it only updates a targetable group when its key matches a configured group type.

If the Group call also includes userId, getuserfeedback.com connects that user to the group for targeting.

What we accept

We accept every Segment event type — identify, track, page, screen, group, and alias.

  • identify updates the user's traits and merges with an existing profile when userId, anonymousId, or email matches.
  • track records the event against the user's profile and makes it available in event-based targeting and segmentation.
  • group updates the configured group profile. When the call includes userId, it also connects that user to the group for targeting.
  • page, screen, and alias are stored when an identity resolves; they don't drive targeting on their own today.

User-scoped events without a resolvable identity are skipped. Group calls need a groupId; include userId when you want the same call to connect a user to the group. Identity stitching follows the same rules as our own SDKs — see Identity resolution.

What can break

  • No events arrive. Confirm the destination is enabled in Segment and points at the live Webhook URL. The URL is unique per integration — copy it again from the detail page if you suspect a typo.
  • Events are rejected (401). The Shared Secret in Segment must match the one on the integration detail page. If Segment's delivery logs show 401s, re-copy the shared secret and paste it into the destination's Shared Secret field.
  • Users look duplicated. Segment is sending events without a stable userId across login boundaries. Identity resolution merges those over time; see Identity resolution.
  • Integration is paused. Paused integrations reject inbound traffic and Segment surfaces 4xx in its delivery logs. Resume from Integrations.

Next