getuserfeedback.
Docs

Segment as a source

Forward identify and track 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 and events to drive who sees a survey, with full context on each response.

Every identify and track event Segment sends arrives in getuserfeedback.com. Targeting can use those traits and events right away.

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. Keep it private — anyone with the URL can post events to your workspace.

2. Add a Webhook destination in Segment

  1. In Segment, open Connections → Destinations → Add destination.
  2. Search for Webhooks 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. Enable the destination.

Segment will start streaming 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.

What we accept

We accept every Segment event type — identify, track, page, screen, group, and alias. Each event is stored against the user whose identifiers it carries.

  • 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.
  • page, screen, group, and alias are stored when an identity resolves; they don't drive targeting on their own today.

Events without a resolvable identity are skipped. 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.
  • 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