How Logins Count Work

• Login Count Attribute

The Logins Count attribute refers to the number of times the user has logged in. If a user is blocked and logs in, the blocked session is counted.

This field is updated at the following moments:

• After the user authenticates with username and password in an Auth0 database connection through Universal Login.
• After the user authenticates through /oauth/token with any credential supported by the endpoint: password, passwordless OTPs, native social, etc.
• After the user authenticates through /co/authenticate (embedded login from Single Page Applications).
• After the user authenticates in an upstream Identity Provider. In this case, they might not need to enter credentials if there is already a session with the upstream identity provider.
• Before Actions/Rules execute. This behavior has the following implications:
  • When logging in as part of a signup flow login count will be set to one: logins_count = 1.
  • If the user is not redirected to the application after Actions/Rules execute (an error is returned, or they do not complete the MFA), the logins_count is incremented anyway.

The field is not updated in this scenario:

• If the user already has a session in Auth0 and there is no need to provide credentials (for example, SSO or Silent Authentication).
• If the user logs in by directly calling dbconnections/signup. If they do log in after signing up, it will be incremented in that first login.