User Data #
User data encompasses two general categories of data, which we clean, aggregate and combine on your behalf in order to compile a fully transparent User profile minimizing possibilities of human or machine error caused by misinterpretation. After setting up the ingestion pipeline, we require you to push all of new user data in daily (or shorter) cycles in order for our models to learn from the most recent actions.
Analytics data #
Often called "event data", these are timeseries database records denoting actions of individuals interacting with your app during the course of their usage. Some typical behavioral data subcategories we leverage for a wide variety of use cases are:
- user identifiers - GAID, IDFV, IDFA (where possible), or a custom ID, please encrypt user identifiers using a cryptographically secure method, for example a salted sha256 hash function - we never process any personally identifiable information of your users to ensure their privacy is protected
- activity - session started/ended, push notification interactions, ...
- monetization - ad viewed, IAP viewed/bought, subscription bought, ...
- progression - tutorial completed, level completed, currency received, first shop visit, ...
- social - joined a club, referred a friend, connected a social profile, supported friend, ...
Full specification of each app varies and its understanding is subject to interpretation, always to be validated and confirmed either through manual testing process or in communication with the assigned Data Officer on your side.
Behavioral data is also the most volume-heavy category, often spanning gigabytes to terabytes worth of database rows. We recommend defaulting to one of our integrated partners if possible:
If your data warehousing technology isn't listed above please contact us, our very own engineering team is more than capable (and happy) of adding your storage in a matter of days.
Contextual information #
Includes data sources which describe environmental parameters rather than information related to the user's playthrough. Mostly relevant for personalization of first time user experience, the subcategories of contextual information we distinguish are:
- device information - device OS type & version, memory size, display resolution, ...
- acquisition (on Android) - country, paid/organic, CPI or CPA, source parameters, ...
- retargeting information (cross-promo) - source app & parameters, source user profile, ...
This data may be provided in a denormalized form - attached to behavioral data as parameters of certain events (such as registration or first session), or directly by granting us developer access to your third parties' management accounts.
IAP catalogue #
Usually managed by your liveops designers, IAP catalogue includes definitions of most or all of your IAP bundles, whether it's starter packs, best value deals, seasonal bundles or anything else. Automated integration is required for any personalization use-cases, as we optimize for long-term impact and require parameters such as:
- IAP UUID,
- bundle contents,
- availability / exclusivity,
- and others...
As these definitions typically live in CRM systems, we provide some out-of-the-box integrations to get you set up faster:
If your CRM system isn't listed above, or if you use an in-house solution let us know so we t streamline the experience for you.
Identity directory #
This dataset represents a way for you to forward us any additional aggregated information about the players that you have readily available and may include:
- player ID mappings,
- tester flags,
- cheater flags,
- custom segmentations,
- custom AB testing attributes.
Data definitions #
In the initial stage of our cooperation we always ask to share any readily available technical documentation and interpretation guidance relating to behavioral events or contextual parameters, typically in a form of a document, spreadsheet or a more formal specification - for example a JSON schema.
Data definitions represent a living document which is to be kept up-to-date at all times to avoid operations issues. For best experience, we recommend notifying your Assetario Success Manager about any major remote changes or releases ahead of time, so we can facilitate a seamless transition.