Understand anonymous and identified users
Read customer context without confusing an identity with a real person’s name.
Last updated 9 September 2026
On this page
Both kinds of users matter
An anonymous user can interact with your product before signing in. An identified user has an external ID supplied by your app. UserGist supports both, so you can learn from customers who have not created an account as well as those who have.
Find a user
Select the correct app and open Users.
Search for the identifier you know and use the available identity filters.
Open the profile to review recorded properties and activity.
When investigating a response or delivery, match the app, identity, and time rather than relying only on a display name.
Understand identity links
Your SDK integration is responsible for identifying a signed-in customer and resetting its identity when appropriate, such as on sign-out. Explicit identity links can connect anonymous activity with an identified subject. Two records should not be assumed to be the same person merely because an email-like value matches. Portal-origin and SDK-origin identities can also be distinct.
Why some fields are missing
A profile only contains information that reached UserGist and was allowed by your settings. Missing name, country, or plan data is not evidence that a user lacks those attributes. Ask your developer to verify the properties being sent and your privacy configuration before building rules around a missing field.