You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Users can now merge and delete accounts; usernames can be reclaimed. This has the potential to create account name collision in our data set. Please start collecting wallet address to Identify users. Currently, we rely upon the federated username only. @dirtyanalytics and @tammycamp
The text was updated successfully, but these errors were encountered:
If you guys switch to identifying based on wallet address there will be a period of time where many users are double counted in Amplitude, is that ok? Basically "active users" is based on a 30 day window so if a user is active and gets re-identified with wallet address Amplitude thinks it's a new user, but still also thinks the old username is a unique user.
If wallet address is a better unique key in the long term it's probably better to make the switch sooner than later.
All that needs to be done is update any and all calls to analytics.identify to look something like this:
Users can now merge and delete accounts; usernames can be reclaimed. This has the potential to create account name collision in our data set. Please start collecting wallet address to Identify users. Currently, we rely upon the federated username only. @dirtyanalytics and @tammycamp
The text was updated successfully, but these errors were encountered: