We’re doing signup tracking but not doing much past that, but are about to start doing a bit more tracking after the signup and I do not want to incur double MTUs because of a faulty alias/identify setup on my part. Currently, as soon as the signup is successful the client is calling
mixpanel.alias with the user’s new ID from our backend. Is that enough to ensure that if the backend then tracks an event for that user using only the user id that it will NOT count as an additional MTU? The backend does not currently have any clue what distinct id was generated for the user by the client.
Or, is it required that we call
mixpanel.identify and/or enable ID merge?
Best answer by mikesnare
The answer to this question after getting some help from support is yes, as long as at least 2 seconds have elapsed between the call to mixpanel.alias and subsequent calls to other mixpanel code using the new ID. It takes a little time for mixpanel to alias things so you want a little delay. In my case we delay backend requests by a minute, which give the front end plenty of time to call alias. Once the alias request has been processed, you can use either id and it will be a single user.