[DATA] Login Tracking
Closed this issue · 0 comments
I have a new request regarding analytics that could help us better understand potential frictions in the login flow within the Explorer. Specifically, I propose enhancing the tracking to include the following events:
View Login Page
Triggered when a user enters the DCL Explorer without a cached wallet.
View Jump In Page
Triggered when a user enters the DCL Explorer with their identity cached.
Click Login Button
Triggered when a user clicks the Login button and is redirected to the authentication site.
We should also track the auth Request UUID here to link the explorer_v2 event with the auth page view and login events.
Login Success
Triggered when a user logs in successfully.
While we already have the identify event, we can use this to confirm the identity provided aligns with a successful login attempt.