Help > English > Administrator > Manage a Site > Data telemetry FAQ

Data telemetry FAQ

Description

Seeking to improve the product from usage data, Open LMS has started the product telemetry initiative. This document covers key questions our clients may have about the initiative.

Why should I participate in the data telemetry project?

One of the most used practices in the technology industry for the continuous improvement of products is the capture of anonymous data on the use of platforms. Through this information and in an aggregated way, product teams can answer questions such as:

  • What components of the product are used most frequently?
  • Are the improvements made to the product actually being used?
  • What is the flow of actions that users take to perform certain tasks?
  • What enhancements can be made to the product to help users complete common tasks?

Anonymous data can help answer these questions and measure the effects of the improvements made to determine if they have the desired effect.

By sharing anonymous usage data, customers can directly influence the product feature and enhancement roadmap. Sharing anonymous usage data you contribute to influencing the product roadmap and help us to provide a better user experience based on your platform usage.

How is data telemetry done in Open LMS?

Data telemetry in Open LMS is done through a plugin that is available on all client platforms and adheres to the following principles:

  • It’s optional: Customers can participate in data collection or opt-out at any time through a request to Open LMS’ Help Desk.
  • It is anonymous: We do not collect or store information that allows users to be identified. Email addresses, names, surnames, etc. are not captured.
  • It’s global: Clients agree to anonymous data collection on behalf of the organization or institution for all of its admin users.

What data is captured for telemetry in Open LMS?

  • “Page view” events: This tracks the type of page an anonymous user is visiting. EJ: quiz, collaborate, course overview. The content of the page is NOT visible to Open LMS.
  • “Form submission” events: When the action of submitting a form is performed, the event is captured as “action performed”. EJ: Quiz submitted, course settings saved, PLD rule created. The content of the form or the information submitted is NOT visible to Open LMS at any time.

What kind of users are captured in Open LMS telemetry?

The initiative is only aimed at administrator users of client sites. We don’t track teachers, students, or any role other than administrator. If in the future we explore expanding the target audience, Open LMs will inform in a timely manner and through the company’s communication channels the intention to do so. It would be updated in the privacy and data policies so that clients can make a decision regarding continuing, limiting, or stopping participation in the initiative.

What information is held for each user?

Open LMS does not capture personal information that allows us to identify who the observed user is.

Each user has an anonymous ID code that allows us to determine that the actions performed were done by the same user to facilitate analysis. This code is NOT related in any way to personal IDs, social security numbers, email, names, usernames, or any other factor that allows us to identify the user.

The user profiles within the analytics platform only have the anonymous code as information associated with the user as seen in the following image:

What information is captured per event?

Open LMS captures the following data per event:

  • Browser: The name of the browser used in the event.
  • Browser version: The browser version number used in the event
  • City: City in which the anonymous user is located when performing the event.
  • Moodle Context Level: Application information indicating the navigation hierarchy in which the event happened.
  • Country: Country in which the event was registered.
  • Course id: Identifier of the course from which the event was registered, if applicable.
  • Current URL: URL where the event was executed.
  • Anonymous device ID: Anonymous identifier of the device from which the event took place. It has nothing to do with IPs, MAC addresses, or any other type of real device identification.
  • Anonymous user ID: Anonymous identifier of the user. It has nothing to do with the Moodle user id, emails, names, or any other type of personal information.
  • Initial referrer: Url of the application form which the user came before registering the event.
  • Initial referring domain: Application domain.
  • Insert ID: Unique identifier of the registered event.
  • Timestamp: The moment at which the event was registered.
  • Operating system: Operating system of the device from which the event was recorded.
  • Page type: Classification of the page or form from which the event was registered. EJ mod-quiz, course-edit.
  • Active plugins (authentication, blocks, filters, local, modules, reports, themes, tools): Indicates the plugins for each plugin category that were active during the event.
  • Region: Name of the region in which the event was captured.
  • Screen height, screen width: Dimensions of the computer from which the event was recorded.
  • Site language: Language configured for the site at the time of capturing the event.
  • User role: User role in the context in which the event was captured.

The following screenshot shows what an event looks like when it is captured: