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.

Sign up for GitHub

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

Jump to bottom

Investigate alternatives to Google Analytics #634

Closed
1 task
sarayourfriend opened this issue Dec 23, 2021 · 2 comments
Closed
1 task

Investigate alternatives to Google Analytics #634

sarayourfriend opened this issue Dec 23, 2021 · 2 comments
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend

Comments

@sarayourfriend
Copy link
Collaborator

Problem

Currently we have Google Analytics set up but disabled for the frontend. GA requires careful configuration to avoid PII collection, requires a GDPR notice and strategy/cookie consent configuration. It also has massive numbers of features we will likely never use. WordPress and Openverse users may also have questions about Google's commitment to user privacy that could get in the way of folks trusting Openverse. It is also unused by WordPress.org and I don't think we should be the ones to introduce it there.

Description

Let's look into alternatives like https://www.goatcounter.com/ or https://plausible.io/.

Alternatives

Get rid of these types of things altogether. Do we need this for any specific reason? Are there alternatives that wouldn't require integrating with a 3rd party service (or self-hosting yet another service)?

Implementation

  • 🙋 I would be interested in implementing this feature.
@sarayourfriend sarayourfriend added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature 🕹 aspect: interface Concerns end-users' experience with the software labels Dec 23, 2021
@sarayourfriend
Copy link
Collaborator Author

Investigating further and GoatCounter could even be used to gather API usage data through a django middleware.

@sarayourfriend sarayourfriend mentioned this issue Feb 18, 2022
Merged
7 tasks
@obulat obulat removed the 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work label Mar 18, 2022
@obulat obulat transferred this issue from WordPress/openverse-frontend Feb 22, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Feb 23, 2023
@obulat
Copy link
Contributor

obulat commented Mar 27, 2023

Closing this issue because we have done the investigation and decided on the approach to analytics. For more info, see the project Usage Analytics#394

@obulat obulat closed this as completed Mar 27, 2023
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Openverse Backlog Mar 27, 2023
@obulat obulat added the 🧱 stack: frontend Related to the Nuxt frontend label Mar 27, 2023
dhruvkb pushed a commit that referenced this issue Apr 14, 2023
@AetherUnbound
Only drop load table if it exists (#634)
06046da 
* Add test to catch existing issue

* Ensure drop table SQL always succeeds

* Set up CLI param for skipping longer-running tests

* Add more test cases
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend
Projects
Openverse Backlog
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@obulat @sarayourfriend