WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 3 years ago

Last modified 2 years ago

#1596 closed task (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)

stats-plugins.downloads-section1.png (21.8 KB) - added by obenland 4 years ago.

Download all attachments as: .zip

Change History (26)

#1 @pedroghandi
4 years ago

is it frown upon to rank the plugin based on download numbers? Or they wont be ported?

for example:


Last edited 4 years ago by obenland (previous) (diff)

#2 follow-up: @dd32
4 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 @pedroghandi
4 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.


4 years ago

#5 @pavot
4 years ago

Since Active Installs is the primary metric for the plugins, can we have stats for it alongside to Downloads Per Day and Downloads history?

It's important to know what adoption rate your plugin has: what % of users who installed your plugin stick with it and didn't delete it in a day or two.

https://www.evernote.com/shard/s1/sh/0febcb40-7199-4153-a106-a5e4e5be41a6/4136da073a6b4e31/res/b66a9193-67cf-4b13-b7c1-7a0643b47bce/skitch.png

#6 @niravmehta
3 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

#7 @dd32
3 years ago

In 2985:

Plugin Directory: Add an internal API endpoint which will be used to update the stats stored within postmeta.
Currently other w.org systems have to query the DB directly, bypassing WordPress actions and filters, which results in stale data or data not being passed to another service.

See #1596

#8 @dd32
3 years ago

In 2986:

Plugin Directory: Use the new stat fields introduced with r2985.

See #1596

#9 @dd32
3 years ago

In 2991:

Plugin Directory: Add a shim to allow us to retrieve the downloads count from postmeta (although the count is stored elsewhere for now).

See #1596

#10 @dd32
3 years ago

In 3011:

Plugin Directory: Implement the 'popular' category as number of active_installs.

See #1584, #1596

#11 @dd32
3 years ago

  • Type changed from enhancement to task

#12 @dd32
3 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.


3 years ago

#14 @obenland
3 years ago

In 3327:

Plugin Directory: Move download stats to wp-admin.

Download stats are not terribly useful to users.

See #1596.

This ticket was mentioned in Slack in #meta by obenland. View the logs.


3 years ago

This ticket was mentioned in Slack in #meta by obenland. View the logs.


3 years ago

#17 @dd32
3 years ago

#1772 was marked as a duplicate.

#18 @dd32
3 years ago

As mentioned in #1772 we also need to ensure that a % sign is added to the percentage displayed.

#19 follow-up: @samuelsidler
3 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 @obenland
3 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.

#21 @obenland
3 years ago

In 3384:

Plugin Directory: Update version stats to handle the new data source.

See #1596.

#22 @obenland
3 years ago

In 3385:

Plugin Directory: Remove stats from single plugin page.

See #1596.

#23 @obenland
3 years ago

  • Milestone set to Plugin Directory v3 - M5
  • Owner set to obenland
  • Status changed from new to assigned

#24 @obenland
3 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed in dotorg12073].

#25 @samuelsidler
2 years ago

  • Milestone Plugin Directory v3 - M5 deleted

Milestone Plugin Directory v3 - M5 deleted

Note: See TracTickets for help on using tickets.