I have a general understanding of what triggers the MAU count based on the documentation I’ve read.
However, I have a specific question for clarification. The logs indicate that a “Successful login” (log type s) triggers the MAU count. Is the actual trigger for the count the moment of token issuance/exchange, rather than the successful login event itself?
I am particularly concerned about the following scenarios, as they directly impact our operational costs:
If I use an Auth0 Action to deny a user’s access with api.access.deny()after they have successfully authenticated but before tokens are issued, will this user be counted towards our MAU?
More specifically, is the MAU count triggered at the moment of successful authentication, just before the flow transitions to the Post Login Action?
When a new user signs up via the Universal Login page, they are automatically logged in. If I use an Action with api.access.deny() to block this specific initial login, I assume that no tokens are issued. Can you confirm that this user would not be counted towards the MAU for that month, even though a login attempt was made?
As this is a critical issue for managing our costs, we would greatly appreciate a prompt response.
Hi again @pukukyunu, and thank you for your patience!
Neither a Login nor a Sign Up will trigger a MAU count increment if the api.access.deny() is called using an action, as no tokens are issued.
The best way to confirm this is to observe your usage data. You can monitor your MAU count in your Auth0 Dashboard by navigating to Settings > Subscription, or you can find it here. You will notice that login attempts that are blocked by your Action do not cause the MAU count to increase.
You will still see a “Successful Login” event in your logs for a user who is subsequently blocked. This is expected and simply means the user successfully provided valid credentials. The key is that you will not see a successful token exchange event following it. Instead, you’ll see the log from your Action detailing the denial.