Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ UVE: Add Analytics for "modes" and Future Time Machine Calendar #31521

Open
5 tasks
fmontes opened this issue Mar 3, 2025 · 2 comments · Fixed by #31580
Open
5 tasks

✨ UVE: Add Analytics for "modes" and Future Time Machine Calendar #31521

fmontes opened this issue Mar 3, 2025 · 2 comments · Fixed by #31580

Comments

@fmontes
Copy link
Member

fmontes commented Mar 3, 2025

Problem Statement

Currently, dotCMS lacks a system to track how users switch between different modes in the Universal Visual Editor (edit, preview, live) or use the future time machine calendar. Capturing these interactions is essential for analyzing user behavior, improving interface usability, and optimizing overall performance.

Objectives

  • Implement a reliable and secure tracking system for monitoring mode changes and calendar interactions within the Universal Visual Editor (UVE).
  • Ensure that the analytics do not intrude on user experience and meet data privacy standards.

User Story

As a product manager, I want to track every instance where users switch modes in the UVE and their interactions with the future time machine calendar while in live mode, so that we can better understand user behavior and improve the functionalities based on the collected data.

Acceptance Criteria

  • Every mode change from edit to preview to live mode is logged with a precise timestamp and user identifier.
  • Every interaction with the future time machine calendar in live mode is captured accurately.
  • The tracking system operates in a non-intrusive manner, ensuring no disruption to the normal usage of the UVE.
  • Efficient storage and security protocols are implemented for maintaining the integrity and confidentiality of the logged data.
  • A system to verify the accuracy and consistency of collected data is implemented, ensuring reliable analytics.

External Links

[Placeholder for external links to relevant project documents, user feedback, etc.]

Assumptions & Initiation Needs

  • The existing infrastructure is adaptable for incorporating new tracking functionalities.
  • Users consent to data collection according to privacy guidelines.

Quality Assurance Notes & Workarounds

Ensure that the tracking system's coverage and data accuracy are thoroughly tested across all user scenarios without causing performance lags.

Potential Challenges

  • Ensuring no impact on UVE performance due to tracking implementation.
    Solution: Use asynchronous data handling and lightweight scripts.
  • Compliance with data privacy laws can be challenging.
    Solution: Review and adhere to regulatory requirements during the design of the tracking system.

Impact on Existing Features

This tracking feature should seamlessly integrate with existing UVE features without altering their behavior or performance.

@zJaaal zJaaal self-assigned this Mar 5, 2025
@nollymar nollymar moved this from New to Current Sprint Backlog in dotCMS - Product Planning Mar 5, 2025
@zJaaal zJaaal changed the title ✨ UVE: Add Telemetry for "modes" and Future Time Machine Calendar ✨ UVE: Add Analytics for "modes" and Future Time Machine Calendar Mar 6, 2025
@zJaaal zJaaal moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Mar 10, 2025
@zJaaal
Copy link
Contributor

zJaaal commented Mar 10, 2025

Note to QA

I'm writting a technical document to setup and implement Analytics on core-web

Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: QA
Development

Successfully merging a pull request may close this issue.

4 participants