When attempting to update user attributes in a development environment using the JavaScript SDK and subsequently searching for the user in the Statsig admin UI, it is important to understand the expected behavior and requirements for user data to be logged and visible.
Users initialized as anonymous will only have a stableID. If you assign them to a feature or test, they will appear in the Users tab, searchable by stableID, although there may be a delay as data takes time to reach the Users tab.
To see a user's profile updated with additional information such as userID and email in the Users tab, you must enrich their user object with these details and then trigger a subsequent event. It is important to note that only 'production' data is displayed in the Users tab.
However, you can view assignments in real-time for both production and lower environments in the Diagnostics tab. To log the user object, you must call the logEvent API or alternatively use checkGate or getExperiment, as merely initializing the SDK will not log the user object.
For debugging purposes, you can use the Exposures Log stream for any test or gate under the Diagnostics tab, and the Event logstream under the Metrics page to view any custom logEvent events sent to Statsig.