Personalization

When you identify your users, getuserfeedback.com unlocks three things: targeting, personalization, and behavioral segmentation.

Targeting

Show surveys to the right people at the right time. Targeting rules can use any combination of user identity, traits, and behavior:

• Who they are — filter by plan, role, company, or any trait you send.
• What they've done — target users who have (or haven't) responded to a specific survey.
• When — control timing based on signup date, last activity, or session count.

Without user identity, targeting still works for broad rules (page URL, device type, time-based) but can't distinguish between individual users.

Personalization

Surveys can adapt based on the traits you send. For example:

• Show a different opening message to users on the free plan vs pro
• Skip a question about onboarding if the user signed up more than 30 days ago
• Route feedback to different channels based on the user's company

This works with any trait you pass via identify() — plan, role, company, signupDate, or anything custom to your app.

Behavioral segmentation

Responses are tied to real user profiles, so you can slice feedback by any trait or behavior. See which segments are happiest, which are churning, and what the common themes are — across sessions and devices.

This works because getuserfeedback.com stitches user activity across the login boundary and across devices. See Identity resolution for how that works under the hood.

How to identify users

Each get-started guide covers the exact setup for your integration:

• Google Tag Manager — intelligent mode reads your data layer automatically
• React SDK — identify() via hooks
• JavaScript SDK — identify() on the client

User identity is flexible — you can pass a user ID, an email, device identifiers, traits, or any combination. Send what you have.

Without user identity

You don't have to identify users to collect feedback. Surveys work fine without it — responses just won't be tied to a known person. This is a good fit for public-facing pages, pre-login flows, or anonymous surveys.