My case is, when user sign in, I redirect them to page A, but when user sign up, I redirect them to page B (this page is to init their profile)
Well, some people say that I should use ‘loginCount’, if it equal to 1, mean user was just sign up then the app redirect user to page B.
The problem is, suppose user was signed up, and they had complete all steps from page B, now they are in page A as expect, but when user reload the page, the app redirect user to the page B, and they stuck in this page, because the ‘loginCount’ is still equal to 1, it only add up when the user actually sign in using email and password.
Interesting use case! I might recommend looking into using user and or app metadata instead of relying on login_count - This is typically managed through Actions:
My thinking is that you can set some sort of flag on the user profile when they signup, and then update it once they confirm their profile using the Management API.
I’m not entirely sure this addresses your specific use case, but hope it helps give you an idea as to what may be possible!