Anonymous Usage Tracking without Personal details in all Edwiser Products

  • Here is an overview of the different data collected by Edwiser products and why it will be beneficial for the Edwiser community.

    Goal -

    • To generate statistics about the usage of Edwiser products and its various features.
    • This knowledge will help us improve those features that are popularly used by the community.
    • In turn help in catering to Edwiser communities needs in a better way.
    • Provide future updates to existing products after taking into consideration the various WordPress & Moodle environments of Edwiser users.
    • This information also be used to better debugging and the roll-out of the zero-error product

    Things we would NEVER do -

    • The would never collect any personal or sensitive information like email address, user results, etc.
    • Nor would we collect any type of information that could expose the personal information of you or your students,

    Data Collected during this process -

    The data are is automatically gathered unless disabled within the product.
    All the data points mentioned here may not be included as part of all Edwiser products some of these are product specific. The ones which are specific to the product will be explicitly mentioned below.
    The Data collected primarily falls under the following categories

    Site Details
    Information like Edwiser plugin settings, Site URL, Moodle Version, Active WordPress theme, Active Moodle Theme, Active WordPress plugins, Active Moodle plugins, Total Courses, Categories & Users, etc.
    This information helps us understand the WordPress and Moodle environment used by Edwiser users and accordingly develop solutions that would work well in these environments.

    Many times we end up losing a lot of time when it comes to resolving issues that arise on the sites of a few WordPress and Moodle users.
    Usually, these WordPress and Moodle sites are hosted on a shared hosting service, and without the necessary information about the server doing any debugging could cause more issues.
    To reduce the time lost in debugging an issue and to always provide a stable solution to you we need the following details,

    • Installed Plugins = To check whether 3rd party plugins are causing any conflicts with Edwiser products.
    • Product Settings = To understand the various features used by Edwiser users,
    • System Language = For debugging issues related to Edwiser Bridge,
    • System Settings = For debugging issues related to Edwiser RemUI,
      • Blog Active
      • CacheJS Active
      • Messaging
      • Theme Designer mode
      • Multi-Lang Filter
      • Moodle Debug Mode
      • Moodle Debug Display
      • Moodle Memory Limit
      • Moodle Max Exec_Time
      • Moodle Curl Cache
        Database Name = To make sure that Edwiser products are compatible with all Database types.
        PHP Version = To make Edwiser products compatible with the popular and most stable PHP version used by Edwiser users.
        PHP Settings
    • Memory Limit
    • Max Execution Time
    • Post Max Size
    • Upload Max Filesize
    • Memory Limit

    License Key
    Apart from this, we check whether the license applied on the site is active or not. This helps us understand the number of Edwiser users using a particular product and accordingly decide how better we could support them.

    This is the first step towards making all Edwiser products zero-error ones and giving you Edwiser users a superior experience of using Edwiser products.


    1. Phase wise implementation of Tracking Code across all Edwiser products,
    2. Roll out Crash Report & Defect Notifier systems as part of all Edwiser products,
    3. Showcase site analysis data generated from a site to its Administrator so this information also helps in improving the installation and not just Edwiser products.
    4. Improved Knowledgebase that resolves issues at a fast rate.

    If anything is unclear and you have any questions related to the tracker then comment below.

Log in to reply