Comment by spar_x on 27/01/2025 at 00:20 UTC

27 upvotes, 2 direct replies (showing 2)

View submission: Massive Failure on the Product

View parent comment

This does not add up. You wrote that they were expecting 20k new users from this event, and only ended up with 300 users. The problem you describe would not have affected 19700 / 20000 users. Furthermore, if you already had these users' details previously, then you're saying that this only prevented existing users from being registered.. so these were not really "new users" at all and you already have their contact information anyway. This is a problem that should have been caught once you went live and it seems like remedying that problem would have been as simple as wiping that existing table with old user's details. It does not really explain the catastrophe that you described in the original post.

Replies

Comment by Yan_LB at 27/01/2025 at 00:26 UTC

10 upvotes, 2 direct replies

The users were already engaged with the "thing" and had already purchased only giving one info, the ID, now it was a campaign to transform those leads into users, it was a on live event for them

Comment by Dude4001 at 27/01/2025 at 00:33 UTC

6 upvotes, 0 direct replies

Getting existing users to login rather than re-signup is also very very fundamental to any user system. Comes out of the box in Django.