We have a case where we set a registration flag to true if the login_count is 1. However, we have found that even if a user dont add their credentials to perform an actual login, e.g. their session is already stored as a cookie in the browser, and then they press our login button so we authenticate them again without making them write credentials, the login count is still 1 and then we registrate them again. Is there some way of distinguishing between the actual login sequence, and just authenticating them when they are sort of already logged in in auth0?
I saw someone writing that you could use event.transaction.protocol and event.request.query.prompt, but when i console log this in both cases (actual login and just authentication) both of the values above are the same. It seems like the event in the authentication is just the actual login event (when the count increased), as i verified by checking timestamps etc.
How can i find out in an action trigger that an event is the type of event that doesnt increase the login count, so i can seperate between the actual registration and the authentication that follows.