The following are a number of data fields collected by Localytics, outlining what is captured. It is important that prior to reading this article, you understand what a User is as defined by Localytics. For more background on how Localytics collects and analyzes data, read our Analytics Key concepts which can be found in our User Guide. For more on identifiers specifically in the context of Attribution, read our Attribution section within the User Guide.
The Localytics SDK identifies unique devices by creating a proprietary device ID which is generated using a combination of identifiers found on the device. The resulting unique device ID gets attached to all Event and Session data and it is what we use to count users. This ID is designed to persist through reinstalls. So, for example, if someone uses the app, uninstalls, and then reinstalls it, Localytics will treat them as a single user. Also, Localytics only becomes aware of users when a user first opens a version of the app that has Localytics installed.
Localytics allows your app to optionally assign an identity to a user, which we call the user's Customer ID. If your app has actively assigned a Customer ID, Localytics refers to this as a "known" Profile. If your app is either not assigning a Customer ID or the user is using the app with an unknown identity (e.g. not logged in), Localytics will assign a random identifier to which you can associate user-level properties, making their profile "anonymous." Your app can be configured to associate Profile Attributes with Customer IDs.
See the chart below for clarification:
|Profile Type||Customer ID||Description|
|Anonymous||Random value||Localytics-generated random alpha-numeric identifier|
|Known||Username / CRM number / etc.||Identifier communicated to Localytics by your app, usually upon log-in or authentication|
Importantly, if a user is first connected to an Anonymous Profile and later to a Known Profile - e.g. the user first uses the app anonymously, then logs in - the Known Profile cannot automatically inherit the Anonymous Profile's Attributes. Once a Known Profile is assigned, the user will be target-able based on that Known Profile (not the prior Anonymous Profile). Your app should have instructions to communicate important Profile Attributes upon setting Customer ID: they can be found here. You can also batch-upload Attributes either manually via CSV or programmatically via API.
For more on User Profiles, check out our documentation.
In addition to the above mentioned identifiers, Localytics can also collect a device's IDFA (iOS) or Google Advertising ID/GAID (Android) to attribute the source of the download. Similarly to Device ID mentioned above, these identifiers persist through reinstalls.
In addition, Localytics assigns an install ID, which is a random alpha-numeric identifier per app install that is created by the Localytics SDK and is Localytics-specific. When a user first opens your app, their initial Customer ID is the same as their Install ID.