The Time Tracking functionality is optional and should be implemented on the client platform as needed. If you choose not to submit time spent data to the BackOffice(BO), you will still have access to the time spent retrieval APIs described in the _Fetching Time Spent Records _section. However, these queries will return a time value of 0 seconds, since no tracking data will be available for your users. The technical design and implementation of time tracking are entirely handled on the client side. We do, however, provide a few recommendations to guide you in ensuring meaningful and accurate time tracking:

​
🎯 What to Track

  • You should only track the time users spend actively engaging with learning path activities (e.g., while answering questions or interacting with learning content).
  • Do not track time spent on pages such as module results or review activities. These pages are informational only and are intended to show users their performance or feedback. As such, they do not reflect active participation and should be excluded from time tracking.

​
⏱️ When to Submit Time Spent Data

We do not enforce a specific submission pattern for reporting the time spent to the BO. However, we recommend choosing one of the following approaches based on your performance and reliability needs:
  1. 📶 Periodic Reporting
    Send time spent data at regular intervals (e.g., every 10 seconds) to ensure more consistent and guaranteed tracking.     ⚠️ This approach ensures reliable tracking but may introduce performance overhead, especially in low-bandwidth or resource-constrained environments.
  2. 🧩 Event-Based Reporting
    Submit time data when the user submits answers or closes the learning activity page.     ✅ This method is lightweight and still yields accurate results.
    ⚠️ However, relying on the page close event may be unreliable, particularly on mobile platforms, where such events are not always triggered consistently.