php - Monitoring user tracking, statistics, and auditing for app -


I am trying to include user statistics in a site and have decided to take it in my user table: <

  • Go to the counter
  • The last visit time
  • At the time when the user registers
  • / Li>

    Do I miss other statistics? Should I track every login time in a separate table too? Is it considered good auditing or too much?

    There are also other usage statistics which I thought the pages could be helpful as well as ideas. Do you recommend enforcing your own tracking or use a solution like Google Analytics (I think it will add a lot of external code to the site, so I thought it would be your own page view Applying tracking would be better) any thoughts on this?

  • Deciding the extent of usage tracking on your website is ultimately personal decision is the long-term goals of your website / On.

    To consider some things:

    1. Is this data going by the web app owner to decide the future product? (Identifying the popularity of features, identifying high load sections of your site etc.)
    2. Is these figures being used by the web app owner for marketing reasons? (Campaign success ratio, conversion metrics, marketing goals, etc.)
    3. Is these statistics being used by your users for any feature (s)? (Link traffic for popularity, number of profile views, etc.)

    For # 1 and # 2, it is very important to determine whether you have user-based statistics or page-based statistics Believe it or both.

    For # 3, implementing on a consistent basis is easy, usually when you offer a new feature.

    This is the overall strategy in your case, (not knowing the above goals), I think you'll need it:

    • User login table ( Each line is the entry of a user login) - It helps you ever need to compile the statistics of the most popular times of your users' access, can users simultaneously "swarm" or spread the logs? Also, you should store the data in this table every month, and only your monthly metrics should be stored in the file on any other table or disk.
    • Access to the user's table fails - This table is generally overlooked but is extremely important
    • Active users' table - Locate a trend in active users on the site To take a snapshot of this table, use it with a combination of cronabesh
    • User page views table (each line is a user / page added) - fixed it Helps to determine which pages / features are more popular and help in determining future product direction

    All this is being said, third-party tools like Google Analytics Do not be afraid to use (especially if your case is # 2) There is no point in finding the wheel again and implementing the metric layer of our own usage (usually comes at a display cost Probably would be bandwidth and high performance).

    There are other tools like Mint () which you can install server-side and customize for your own usage metrics.


    Comments

    Popular posts from this blog

    asp.net - Javascript/DOM Why is does my form not support submit()? -

    sockets - Delphi: TTcpServer, connection reset when reading -

    javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -