Skip to content

Analyze analytics / event tracking for the SPA and define a plan for its setup #245

@GPortas

Description

@GPortas

Overview of the Feature Request

For the tools to analyze, take into account opensource tools.

It is important to decide whether this tracking should be configured to be done by default on any installation or only at a particular installation. (Potentially Harvard Dataverse).

Update:
The proposal from this issue could be a solution for this.

What kind of user is the feature intended for?

All of them

What inspired the request?

  • Frontend Weekly meeting

What existing behavior do you want changed?

None

Any brand new behavior do you want to add to Dataverse?

User event tracking

Metadata

Metadata

Assignees

No one assigned

    Labels

    FY25 Sprint 21FY25 Sprint 21 (2025-04-09 - 2025-04-23)FY25 Sprint 22FY25 Sprint 22 (2025-04-23 - 2025-05-07)GREI Re-archGREI re-architecture-relatedOriginal size: 20SPA.Q1.12User MetricsSPA.Q2.12Implement User Metrics MVPSize: 3A percentage of a sprint. 2.1 hours.

    Type

    No type

    Projects

    Status

    Done 🧹

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions