Best Practices for Implementing User Profiles in API Systems

Gabe · 2025-11-06 18:07:10.82387+00

We are on the original api, and do not have users implemented. Within our app, users have the ability to have multiple profiles, including single solo and partner profiles, but all unique users are tied to an account with a unique account id per valid phone number used in registration. What would be the best practice for properly implementing users including setting the distinct id, managing profile identity for users (maybe tying distinct id to account id and passing in an active profile id as a user property?), when we should be identifying users and resetting them (log in, sign up, log out, etc.), and setting user/profile properties when profile information is updated, etc?

Given your scenario—using the Original API, no users currently implemented, and each unique user tied to an account ID (per phone number), with the ability for each account to have multiple profiles (solo/partner)—here are the best practices for implementing user identity and profile management in Mixpanel: ---

- Use the unique account ID (tied to the phone number) as the distinct_id for each user. This ensures that all activity for a given account is attributed to a single user in Mixpanel. - For anonymous users (before registration or login), let the Mixpanel SDK generate a $device_id and use that as the distinct_id until the user registers or logs in. Learn more---

- Active Profile ID as a User Property: Since each account can have multiple profiles (solo/partner), pass the currently active profile ID as a user property (e.g., active_profile_id) on all events. This allows you to segment and analyze events by which profile was active at the time. - Do not use the profile ID as the distinct_id—this would fragment the user’s activity across multiple Mixpanel users, making it difficult to get a unified view of the account.---

- Call .identify(account_id): - On registration (sign up) - On login - When the app is re-opened in a logged-in state This links all pre-login (anonymous) activity to the account and ensures all future events are attributed to the correct user cluster. - Call .reset(): - On logout - When there is an explicit intent to switch to a new user (e.g., clicking "Sign-up" for a new account on the same device) This clears the current user’s identity and generates a new $device_id for the next session, preventing data from different users from being merged. Best practices---

- Set user properties (e.g., account-level info) after identification using .people.set() or equivalent, and always after the user is identified. - Set profile properties (e.g., profile name, type, etc.) as event properties or as user properties (if you want to persist them on the user profile) whenever the active profile changes or is updated. - Avoid creating profiles for anonymous users. Only set user/profile properties after the user is identified. More details---

1. Anonymous User: - Events tracked with SDK-generated $device_id as distinct_id. 2. User Registers/Logs In: - Call .identify(account_id). - All future events use account_id as distinct_id. - Set user properties (e.g., phone number, registration date). 3. User Switches Profile: - Pass active_profile_id as an event/user property on all events. - If profile info changes, update relevant properties. 4. User Logs Out: - Call .reset() to clear identity and generate a new $device_id for the next session.---

- Track the account ID as a super property and user property to assist with troubleshooting and querying. - QA your implementation to ensure no duplicate profiles and that all identifiers are correctly clustered. - Document your ID management approach for future reference and troubleshooting. Best practices summary---If you need to merge two account IDs (e.g., in rare cases of account consolidation), you can use the $merge API event, but this is not typical for most flows and should be used with caution.---References: - Original API: Best Practices - Identity Management FAQ - Client-side Identity ManagementIf you need more specific code examples or have a unique edge case, let me know!

kapa.ai is still learning and improving, please let me know how I did by reacting below.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Best Practices for Implementing User Profiles in API Systems

29 comments

1. Setting the distinct_id

2. Managing Profile Identity

3. When to Identify and Reset

4. Setting User/Profile Properties

5. Example Flow

6. Additional Best Practices