When you ask users for additional information, avoid asking for information that you may already have. For example, if a user signs up through a social connection that uses the OpenID Connect protocol (such as Google or Facebook), the identity provider (IdP) may return more user information than you think. To learn more, read OpenID Connect Scopes.
- Shortening registration forms.
- Avoiding repetitive questions.
- Collecting more relevant information.
- Increasing conversion rates.
How it works
Every time a user authenticates through Auth0, Auth0 updates their user profile. The data used to update their profile can come from different sources:- Attributes supplied by the .
- Attributes created dynamically with Auth0 Actions.
- Attributes returned from calling APIs such as FullContact and Clearbit.
- Attributes managed by the application.
Use action triggers
With thepost-login
action trigger, you can modify a user’s user_metadata
and app_metadata
fields during the login flow. This is useful for tasks such as storing application-specific data on the user’s profile, recording whether or not specific operations have occurred for a user, or caching the results of expensive operations on the user profile so they can be re-used for future logins. To learn more, read Manage User Metadata with the post-login Action Trigger.
Use the Management API
You can use the Auth0 Update a User endpoint to update the profile data of an authenticated user, including theapp_metadata
and user_metadata
fields. To learn more, read Manage Metadata Using the Management API.
Use the Lock library
You can use theadditionalSignUpFields
option to add custom fields to user signup forms. When a user enters data into a custom field, Auth0 stores the value in their profile’s user_metadata
field. To learn more, read Lock Configuration Options.