You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We deployed Google Analytics on beta.peeringdb.com in 2.42.0 (November 2022) as a first step towards achieving the objectives set out in #1218
2.43.0 (January 2023) was the first opportunity to collect data from users testing against beta. One takeaway is that we probably need to encourage more organizations to test against beta.
The rationale behind #1218 remains, so we should move towards deploying Google Analytics on www and docs. That way we'll be better informed about who our users are and be in a better position to make good decisions.
Before deploying on www and docs we should deploy #1281 so we know which pages users are using.
Is your feature request related to a problem? Please describe.
We deployed Google Analytics on beta.peeringdb.com in 2.42.0 (November 2022) as a first step towards achieving the objectives set out in #1218
2.43.0 (January 2023) was the first opportunity to collect data from users testing against beta. One takeaway is that we probably need to encourage more organizations to test against beta.
The rationale behind #1218 remains, so we should move towards deploying Google Analytics on www and docs. That way we'll be better informed about who our users are and be in a better position to make good decisions.
Before deploying on www and docs we should deploy #1281 so we know which pages users are using.
There is a guide to deploying Google Analytics on MkDocs (docs) here: https://squidfunk.github.io/mkdocs-material/setup/setting-up-site-analytics/
Who is affected by the problem?
@peeringdb/pc
What is the impact?
All users should benefit from better product decisions
Are there security concerns?
No
Are there privacy concerns?
Not really. Users who object will have installed a browser plugin that ignores the Google Analytics URL
Describe the solution you'd like
These can happen in the same deployment.
Do you think this feature will require a formal design?
No
Describe alternatives you've considered
We looked at a range of web analytics tools and Google Analytics seemed like the best fit for us
Could this feature request need support from the Admin Committee?
No
What is the proposed priority?
Target of 2.45.0
Provide a rationale for any/all of the above
As above
The text was updated successfully, but these errors were encountered: