Why identify your users
By default, someone who submits feedback through your widget shows up as an anonymous visitor. Identifying them links that submission, and every survey response and session afterward, to a real user profile: name, email, plan, account ID, or whatever else you send.
This is what powers Segments, Reports, and AI Themes being able to group and filter feedback by who submitted it.
Option 1: identify() for logged-in users
Use identify() when your users log in, or can switch between accounts during a session. Call it once you know who the user is, typically right after login, passing a user ID and an object of attributes such as name, email, plan, and account ID.
This is the right option for any app where the same browser session might represent different people over time.
Option 2: user_data for static sites
Use user_data if your site doesn't have a login system, or the visitor's identity is already known when the page loads (for example, a WordPress site identifying a logged-in member via a server-side hook). Set user_data as part of your Userback initialization instead of calling a separate method afterward.
Where identified data shows up
Once a user is identified, their attributes appear:
On the feedback item itself, in the User Data section.
In their User Profile panel, under Users & Segments.
As condition fields when building a Segment (for targeting or reporting).
In AI Themes and Reports, wherever feedback can be grouped by user or account attribute.
What's next
User Properties and Custom Attributes Reference: the full list of fields you can track.
Users and Creating Segments: group identified users for targeting and reporting.