Since the SDK maintains the feature targeting ruleset in memory, it can only consider the user attributes passed to it when you call
identify. This ensures that there’s no network latency when you get a variation, since it does not need to call back to LaunchDarkly to look up other attributes.
In order to see the correct user attributes on the dashboard, you must include the custom fields in the user object when you get the variation. The user page will only display all of the user attributes seen by the SDK when doing an evaluation.