Managing Identity
Last updated
Last updated
Identities are used to merge user in to a unified view, across sessions in a browser, and across devices and platforms.
If a user views your website, and logs into your site, you may send an identify
message letting Fanplayr 360 know that this user should be identified by a specific email
, and userId
.
When this same user logs into your phone app, you can make another identify
call with the email
address and events and profile information from both devices and sessions will be linked.
The identify
message has two parts:
The type
must be set to "identify"
The identities
object must be provided. This is an object containing key/value pairs; the key being the type of identity ie "email", or "userId".
Identify events can be sent at any time, although we suggest
When you send an identify
message, the userId
and sessionId
are recorded. Any events collected, or user , with the same userId
or sessionId
is merged into the same Profile.
It is important to only use identify
when you are sure of having the correct identifying information, otherwise you may end up linking profiles that are not related, and there is no way of unlinking these later.
The following example identifies the current session / user by both email
and webPush
identities.