Track and show traffic to module pages

Tracking and displaying traffic to module pages could be an indication of popularity or interest.

It would allow showing "hot" modules over various time periods. ("Hot this week" vs "Hot this year.)

I think this could help with the discoverability problem.

[oalders]

This is something I know we want to do in some form. We had talked about doing something as basic as parsing the nginx logs. Don't know if we could even just use the Google Analytics API for some useful stats? Even getting some traffic indicators into ES would be helpful as well. Tracking clicks on download links etc.

[lorn]

If we create a 'gateway' to count this? I mean:

curl https://metacpan.org/download/id/L/LO/LORN/LWP-Curl-0.12.tar.gz increase the download counter and 302 to http://cpan.metacpan.org/authors/id/L/LO/LORN/LWP-Curl-0.12.tar.gz

( or even the http://cpan.metacpan.org/authors/id/L/LO/LORN/LWP-Curl-0.12.tar.gz increase the download counter and 302 to the real url )

And we can use same principle in the metacpan API

Does anyone know how many downloads we have through metacpan api/site ?

👍 This topic :)

[monken]

Google Analytics tells us that https://metacpan.org/module/INGY/XXX-0.18/lib/XXX.pod is the most popular module. Go figure ;)

I remember that we thought about releasing the HTTP logs to the public. Not sure where that discussion went.

[ranguard]

Moved to wish list: https://github.com/CPAN-API/cpan-api/wiki/Wishlist