DUP Track time spent on timed information entry page

[cameronpettit]

Description:

From #352. It seems that tracking this metric via snowplow is perhaps possible, but this team doesn't have the ability to modify the existing GDX Analytics dashboard to surface it. The team responsible for this dashboard is unresponsive.

This ticket is to investigate other avenues to capture the time spent on the timer page - Clickstream, CloudWatch, self hosted Snowplow, Google analytics, etc. This would be a good opportunity to investigate how we want to monitor analytics at scale for the upcoming PRDT project.

Acceptance Criteria:

Given I am a DUP analyst
When I want to know time-spent analytics on the DUP contact information page (the one with the timer)
Then I have a convenient way to access and view these analytics.

Development Checklist:

• Investigate alternatives other than the existing snowplow setup to gather website analytics, in particular time spent analytics.
• Make considerations for scalability and the ability to use a similar analytics setup for the PRDT project.
• Implement the solution as a POC, or include all findings in this ticket & create a new implementation ticket

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

Definition of Ready

• Acceptance criteria are included
• Wireframes are included (if applicable)
• Design / Solution is accepted by Product Owner (if applicable)
• Dependencies are identified (technical, business, regulatory/policy)
• Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • UI meets accessibility requirements
  • Unit tests are written
  • Work is traceable in GitHub
  • PR linked to ticket number
  • If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • Code is peer reviewed and has passed CI/CD tests
• QA:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • Code is potentially shippable to the production environment
  • Functional features have been tested and passed by QA
  • UI components tested by designer
  • Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • Reviewed and approved by Product Owner

Notes: