3 ms·
Honestly, having run a number of experiments with magic link, I wouldn’t recommend them. We saw our login success drop noticeably. We tried a few different appr
by scott_w 2y ago
Honestly, having run a number of experiments with magic link, I wouldn’t recommend them. We saw our login success drop noticeably. We tried a few different approaches over the course of a quarter but even our best attempt only mitigated the drop compared to having email/password and Google Login.
Obviously, your mileage may vary but it was a good reminder to always validate your assumptions, especially in your critical user flows.
- sebastiennight 2y agoI'm super interested as we've been debating adding email/password (since we only use Magic Links at the moment). How are you tracking login success rates?
- scott_w 2y agoPretty straightforward: you send an event for which variation your user saw and another when they login, attaching the login method to the attributes. You can use Mixpanel or Heap, which have mechanisms for mapping the non-logged-in user to your verified user on login, though you might need a bit of custom code to do it.
- sebastiennight 2y agoAh. We use June.so ; I'm assuming they might have a similar mechanism. We'll try and log login attempts so we can track this. Thank you!
- scott_w 2y agoNo worries! Our experience is that the hardest part (and it's not trivial) is associating the "anonymous user ID" to the newly logged-in user. Segment has an identify() function (I think Mixpanel has something similar), where you link the aliases, which then makes the reporting work. I've not tried June, so I can't say for sure, but it's a pretty common feature for product analytics. I'll be surprised if it's not possible.