Analytics for https://public.peeringdb.com/peeringdb.kmz downloads

[leovegoda]

Is your feature request related to a problem? Please describe. https://public.peeringdb.com/peeringdb.kmz downloads are not visible in Google Analytics

It would be good to get some data for how the service is being used

Who is affected by the problem? @peeringdb/pc

What is the impact? The PC will have more information when making decisions and setting priorities

Are there security concerns? No

Are there privacy concerns? No more so than for Google Analytics

Describe the solution you'd like Data on the number of downloads and the cities or countries from which the downloads take place

Do you think this feature will require a formal design? Yes

Describe alternatives you've considered Do nothing

Move the location from the current free hosting to a place covered by Google Analytics

Could this feature request need support from the Admin Committee? No

What is the proposed priority? Low

Provide a rationale for any/all of the above Data means less reliance on anecdotes, personal experience and guesswork

[peterhelmenstine]

+1 Curious why this doesn't happen by default when adding new links? We have to do this for everything new?

[martinhannigan]

+1

On Wed, Mar 13, 2024 at 17:02 Peter Helmenstine @.***> wrote:

+1 Curious why this doesn't happen by default when adding new links? We have to do this for everything new?

— Reply to this email directly, view it on GitHub https://github.com/peeringdb/peeringdb/issues/1566#issuecomment-1995803106, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFA2YQU5J3PJEXYR6S257JLYYC5G7AVCNFSM6AAAAABEUPDNDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJVHAYDGMJQGY . You are receiving this because you are on a team that was mentioned.Message ID: @.***>

[leovegoda]

+1 Curious why this doesn't happen by default when adding new links? We have to do this for everything new?

I believe it is related to public.peeringdb.com being hosted on github.com instead of AWS.