Kissmetrics tracks people.
People can be represented with usually at least 2 different names in their lifetime as a customer. One when they are first anonymous; another when they become known through signing up, logging in, or installing your app.
Kissmetrics has two techniques to connect these different names to represent the same person: alias and identify.
The generated ID is Base64 encoded, so the IDs are generated with only these characters: a-z, A-Z, 0-9, +, /, and =.
The function KM.i() will return the visitor’s Kissmetrics ID, in case you need to pass that along to another function.
Your API Key
255 char string
One of the person's identities
255 char string
Another of the person's identities
This tells us that events done by User 12345 and events done by [email protected] were done by the same person. If you log events or properties to either ID, they all refer back to the same one person.
Calling alias is not reversible, and should be used with some caution
There are only a handful of scenarios where it is appropriate to directly call alias:
You are identifying people by their email address, and they update their email address within your app.
You change your tracking schema to identify people…say, from email address to username.
After calling alias, the new alias does not appear in a person’s list of Customer IDs unless the new alias has triggered an event or has properties set on it.
It’s fine to call alias more than once with the same pair of identities.
It’s natural if a person has more than one alias.
The order you pass the two arguments does not matter.
Aliasing with Kissmetrics is now done in batches. Every 6 hours users who have had alias calls called on them are aliased together.
This means if you alias 2 users together and then look up that user, you will see two distinct users if the aliases have not been processed yet.
It won't necessarily take 6 hours for aliasing to occur, it could be aliased immediately or up to 6 hours depending on where you are in the cycle.
The Identify call triggers aliasing, so this affects both Aliasing users and Identifying users.
Updated about a year ago