Skip to main content

User Behaviour Analysis

Overview

Every product where user come and interact, there is need to do User Behaviour Analysis to identify:

  • What user wants
  • What excites user (or engages user)
  • How he interacts with our App (Web or Mobile)

This is done to improve both User Experience and to make the product useful to user (and make it part of their daily routine as few social media and entertainment services). The whole tracking of User Behaviour depends upon  4 Ws - Who, When, Where and What.


Solution Design

The Solution consists of 3 Key Components

  1. Event Tracker / Recoding APIs or Engine – This component would take input from different client Apps (Web or Mobile) and store them. The data transformation or normalization of input keys can be done in this component.
  2. Data Warehousing - The data required for different modules for analytics would be stored in the scalable storage (like HDFS, S3, )
  3. Analytics / Reporting - provide an interface / reporting dashboard that can be used by Business teams

Data Points

The data points for storage would be based on

  • WHO - This refers to the details of the users who is accessing the specific feature (interacting with Application) in any way. This can contain user’s unique id, role etc
  • WHEN - This is the timestamps when the interactions have been done.
  • WHERE - This refers to the details of the user devices, platform details, client IP address / Geo-location etc to track from where the interaction is made.
  • WHAT - This is the details of what has been accessed… feature used and action performed (viewed, created, deleted…)

Among these, WHO, WHEN and WHERE are to be recorded for ALL data points and modules.

Labels:

Comments

Post a Comment

Popular posts from this blog

Capturing Console Output using c#.net in Windows Form Application

There is a case when we need to use same library code in both console application and windows form application. This is fine if there are no messages displayed in the output window (usually the progress / log messages). one way is to create a log file in a predefined folder (TEMP) and open it after process is complete. Here is one method that can be used to capture the console output and redirected to a text box in the windows form application. Steps Create a new class as given in the snippet Take the temp reference of default output stream of 'Console' class and set new stream output that captures and shows the output in the text box Once new stream is set, all the console output is displayed in the referenced text box After work is done, restore the output stream to default // Create a class for capture using System; using System.Collections.Generic; using System.IO; using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Form...
Post a Comment
Read more

Change Default Content Overlay on Folder Icon in Windows Explorer

Want to Change (Default Folder Preview) to (Custom Preview image). Here’s how it can be done. Folder Properties Use the Folder Properties –> Customize –> Choose File. this will allow selection of an image that would be shown as preview of the folder. Modify desktop.ini [ViewState] Mode= Vid= FolderType=Documents Logo=C:\Temp\myFolderIcon.jpg Create folder.jpg simply create a file with name ‘folder.jpg’. It would then change the preview to this image.
Post a Comment
Read more