From 8ea7b07deb4e56ac1960ef8074983af045e48abe Mon Sep 17 00:00:00 2001 From: Cecila Schnell Date: Sun, 16 Nov 2025 14:27:23 +0000 Subject: [PATCH] Add 'Identifying Users (Simplified)' --- Identifying-Users-%28Simplified%29.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 Identifying-Users-%28Simplified%29.md diff --git a/Identifying-Users-%28Simplified%29.md b/Identifying-Users-%28Simplified%29.md new file mode 100644 index 0000000..bdac83c --- /dev/null +++ b/Identifying-Users-%28Simplified%29.md @@ -0,0 +1,7 @@ +
The knowledge on this web page is for tasks on the Simplified ID Merge API. The information on this page is for projects utilizing the Simplified ID Merge API. You may test your Identity Merge API by navigating to your project settings. For initiatives using Original ID Merge API, [iTagPro geofencing](http://dogetransparency.wiki/index.php/User:TammieWhiteside) please check with this documentation right here. Learn extra concerning the different ID Merge APIs here. Mixpanel helps stitching consumer behavior pre-login (eg: traffic from your website, [iTagPro geofencing](https://karabast.com/wiki/index.php/In_A_Single_Version_Of_The_Experiment) docs, blog) and [iTagPro geofencing](http://foratata.com/segunda-entrada) publish-login (once the person has signed up). What % of site visitors find yourself signing up? How much of my Purchase revenue can I attribute to a selected campaign? This system is named ID Merge. In this guide, we walk via methods to establish users in tasks using the Simplified ID Merge API and [ItagPro](https://git.zimerguz.net/issacn20301852) exactly how it really works underneath the hood. Mixpanel makes use of to determine the uniqueness of your customers. SDK after which connected to all the user’s events.
+ +
ID for [ItagPro](https://git.borg.unak.is/colleen93s9658) the user. ’s events shifting ahead. ID cluster will be attributed again to the identical consumer in Mixpanel. 1. Call .determine() when a consumer indicators up or logs in, passing in the user’s recognized identifier (eg: their ID out of your database). 2. Send at least one occasion after the .establish() name. Learn more in regards to the merge mechanism above. 3. Call .reset() when a user logs out. Any events previous to calling .identify() are considered anonymous occasions. Under the hood, Mixpanel will stitch the event streams of those users collectively. This works even when a user has multiple nameless classes (eg: on desktop and cellular). As long as you always name .identify when the consumer logs in, [iTagPro geofencing](https://wiki.novaverseonline.com/index.php/User:ChristoperBunny) all of that activity will be stitched together. It is strongly recommended to name .reset when a person logout or occasions out of an authenticated session to forestall the unintentional merging of a number of customers sharing one system.
+ +
Let’s stroll through a number of consumer flows the place ID Merge is beneficial, and when to name .identify() and .reset() to make use of ID Merge correctly. 1. A user lands in your product on a brand new gadget and interacts along with your product earlier than signing up. 2. The user returns later and indicators up on your product. 1. The person from the previous movement returns, however is on a new device and has not logged in yet. 2. The consumer logs in. 1. A first consumer begins using a brand new system. 2. The user logs in. 3. The user logs out. Should you don’t know the user’s identification at the time the event is tracked, then they’re an nameless person. This ID will persist on all occasions tracked by that consumer on that gadget, until you call determine() or reset(). If you’re tracking from servers, you’ll need to generate and handle the IDs your self.
+ +
The secret's to have an ID that is exclusive to each person and persists during that user’s session. We recommend generating a UUID and storing that worth in a cookie. All common server frameworks provide a easy strategy to set and retrieve cookies per request. Once the user logs in, you realize their true ID, it is best to leverage the new ID for [iTagPro geofencing](https://rentry.co/72802-itagpro-tracker-your-ultimate-solution-for-tracking) the person. IDs together. This is crucial to trace pre-login and submit-login habits precisely. Here’s a pseudocode instance using Django’s cookies and authentication. By calling .identify() at these specific points in consumer journeys, you'd be able to hyperlink the pre and submit-login occasions to the identical consumer on Mixpanel. Besides, calling .establish when the users re-open the app in a logged-in state ensures that every one occasions in the session are tracked with the user’s identifier such as consumer id. You possibly can observe the user’s distinctive identifier as a super property through .register() and person property via .individuals.set() as quickly as it is obtainable within the app i.e. on a profitable signal-up / login or when an app is re-opened in a logged in state. Within the instances when ID Merge shouldn't be carried out correctly, you possibly can depend on these properties for troubleshooting purposes.
\ No newline at end of file