#1596 closed task (blessed) (fixed)
Stats page
Reported by: | obenland | Owned by: | obenland |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Plugin Directory | Keywords: | |
Cc: |
Description
Only take over active install stats. Total and by version.
Attachments (1)
Change History (26)
#1
@
9 years ago
#2
follow-up:
↓ 3
@
9 years ago
No, we won't be adding overall rankings, although it'd be technically possible to.
A rank doesn't offer an end-user anything which means anything, Ranked #34,125 of all plugins
is not helpful to a user, especially when that plugin is rated 5 stars, does exactly what the user wants, and is actively being developed.
Rankings also encourage people to "one up" another plugin, and that's not what builds a good community.
#3
in reply to:
↑ 2
@
9 years ago
yep, I thought so too. I was thinking in ways that those numbers can mean anything to the user. Like "ranked #34,124", "All time 569,037" is also not really helpful. Those numbers could relate to any period of time.
Replying to dd32:
No, we won't be adding overall rankings, although it'd be technically possible to.
A rank doesn't offer an end-user anything which means anything,
Ranked #34,125 of all plugins
is not helpful to a user, especially when that plugin is rated 5 stars, does exactly what the user wants, and is actively being developed.
Rankings also encourage people to "one up" another plugin, and that's not what builds a good community.
This ticket was mentioned in Slack in #meta by pcarvalho. View the logs.
9 years ago
#6
@
9 years ago
Can we add some sort of "insightful" stats that help the plugin author understand their users better?
- How many people who viewed the plugin page vs how many that actually downloaded (conversion rate!)
- active installs vs support thread creators (tickets / install)
- % of active installs who've seen that there is an update available, but haven't updated yet (btw, is that even tracked currently?)
- split of download count into new downloads vs updates
#12
@
8 years ago
Stats shortcode was added in r3221 and includes the Downloads counts which we were going to remove.
The API's which it uses, 'https://api.wordpress.org/stats/plugin/1.0/*
will need to be updated to use WordPress as well. The active versions stats JS also needs to be simplified to remove most of the version combining logic based on this change in r2985
This ticket was mentioned in Slack in #meta by obenland. View the logs.
8 years ago
This ticket was mentioned in Slack in #meta by obenland. View the logs.
8 years ago
This ticket was mentioned in Slack in #meta by obenland. View the logs.
8 years ago
#18
@
8 years ago
As mentioned in #1772 we also need to ensure that a % sign is added to the percentage displayed.
#19
follow-up:
↓ 20
@
8 years ago
I thought we were moving those stats to be backend-only, given that they don't provide much useful information for users.
#20
in reply to:
↑ 19
@
8 years ago
Replying to samuelsidler:
I thought we were moving those stats to be backend-only, given that they don't provide much useful information for users.
They were moved in [3327] but the data source still needs to be transitioned over to use the new directory.
#23
@
8 years ago
- Milestone set to Plugin Directory v3 - M5
- Owner set to obenland
- Status changed from new to assigned
#24
@
8 years ago
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in dotorg12073].
is it frown upon to rank the plugin based on those stats?
for example: