diff --git a/Identifying-Users-%28Simplified%29.md b/Identifying-Users-%28Simplified%29.md
new file mode 100644
index 0000000..9f1cd93
--- /dev/null
+++ b/Identifying-Users-%28Simplified%29.md
@@ -0,0 +1,7 @@
+<br>The knowledge on this page is for tasks on the Simplified ID Merge API. The data on this web page is for tasks utilizing the Simplified ID Merge API. You possibly can examine your Identity Merge API by navigating to your venture settings. For projects utilizing Original ID Merge API, please seek advice from this documentation right here. Learn extra about the completely different ID Merge APIs right here. Mixpanel helps stitching consumer behavior pre-login (eg: site visitors from your webpage, docs, blog) and post-login (once the user has signed up). What % of site visitors find yourself signing up? How much of my Purchase revenue can I attribute to a selected marketing campaign? This system is called ID Merge. On this guide, we walk by way of methods to determine users in projects utilizing the Simplified ID Merge API and precisely how it works below the hood. Mixpanel makes use of to find out the uniqueness of your users. SDK and then attached to all the user’s events.<br>
+
+<br>ID for the user. ’s events moving ahead. ID cluster shall be attributed back to the identical person in Mixpanel. 1. Call .determine() when a person signs up or logs in, passing in the user’s known identifier (eg: their ID out of your database). 2. Send at the very least one occasion after the .identify() call. Learn extra in regards to the merge mechanism above. 3. Call .reset() when a consumer logs out. Any events previous to calling .determine() are considered anonymous occasions. Under the hood, Mixpanel will stitch the occasion streams of those customers together. This works even if a person has multiple anonymous periods (eg: on desktop and mobile). So long as you always name .identify when the consumer logs in, all of that activity can be stitched together. It is strongly recommended to name .reset when a user logout or instances out of an authenticated session to forestall the unintentional merging of a number of customers sharing one machine.<br>
+
+<br>Let’s walk by just a few user flows where ID Merge is beneficial,  [portable tracking tag](http://www.infinitymugenteam.com:80/infinity.wiki/mediawiki2/index.php/Buoy_GPS_Tracker) and when to name .identify() and .reset() to make use of ID Merge correctly. 1. A person lands in your product on a brand  [portable tracking tag](https://ctpedia.org/index.php/Buy_Weight_Management_Device_In_California) new machine and interacts together with your product before signing up. 2. The person returns later and signs up for your product. 1. The person from the previous circulation returns,  [portable tracking tag](http://global.gwangju.ac.kr/bbs/board.php?bo_table=g0101&wr_id=1079833) but is on a brand new machine and has not logged in yet. 2. The consumer logs in. 1. A primary person begins utilizing a brand new gadget. 2. The person logs in. 3. The user logs out. When you don’t know the user’s identity on the time the event is tracked,  [ItagPro](https://rentry.co/15200-the-ultimate-guide-to-itagpro-tracker-everything-you-need-to-know) then they’re an nameless consumer. This ID will persist on all occasions tracked by that consumer on that machine, until you name identify() or  [portable tracking tag](https://lovewiki.faith/wiki/User:PatrickHope207) reset(). If you’re monitoring from servers, you’ll need to generate and manage the IDs yourself.<br>
+
+<br>The secret is to have an ID that is unique to every consumer and persists during that user’s session. We suggest producing a UUID and  ItagPro storing that worth in a cookie. All frequent server frameworks provide a simple strategy to set and retrieve cookies per request. Once the user logs in, you realize their true ID, you need to leverage the new ID for the user. IDs together. This is crucial to track pre-login and submit-login conduct accurately. Here’s a pseudocode example utilizing Django’s cookies and authentication. By calling .determine() at these specific points in person journeys, you'll be capable of link the pre and put up-login events to the same person on Mixpanel. Besides, calling .establish when the customers re-open the app in a logged-in state ensures that each one events in the session are tracked with the user’s identifier corresponding to person id. You may track the user’s unique identifier as a brilliant property by way of .register() and person property via .people.set() as soon because 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 circumstances when ID Merge will not be implemented properly, you may rely on these properties for troubleshooting functions.<br>
\ No newline at end of file