Page MenuHomePhabricator

Investigate whether metrics exist for certain pages on wikidata
Closed, ResolvedPublic5 Estimated Story Points

Description

Purpose:
As part of the KR "We have created one assumptions map of reuser groups and journeys that guides improvements to access methods and documentation, resulting in more reliable resources." we'd like to get quantitative metrics on what we believe to be current or potential entry points to data access method documentation. This will help us build a baseline of the current state of usage and later be able to directly see the influence of any changes we make

To investigate:

Clicks for:

  • Help button on WDQS UI
  • Help dropdown on WDQS UI
  • Tools button on WDQS UI
  • Tools dropdown on WDQS UI
  • Data access link in the footer on wikidata.org
  • Data access link under Get Involved ("..how you can retrieve and use data from Wikidata") on wikidata.org
  • Developers link in the footer on wikidata.org
  • Tools on the upper right hand corner on wikidata.org

Pageviews:

Unique referrers for the following:

Deadline:
17.7.2026

Output:

  • Documentation (suggest a sheet) where we have for each required page / data point whether there is a table where we can access this, the table name, and if not whether we want to request tracking / follow up ticket ID for this.
  • Completed linked follow up ticket with full scope / detail for providing reporting dashboard for these numbers. Please note: this is to support Ifrah and Elisha for contextualising their work, rather than a specific success metric.

Event Timeline

Helloo, just checking in - I assume this would be done closer to 15.5 instead of 30.04?

Yes, but we can hopefully get to this in the next two weeks. Can you move it into the backlog and position it in regards to the priority to your other tasks, @Ifrahkhanyaree_WMDE?

It's been in the prioritized position, did that a couple of weeks ago! 2 weeks sounds good, thank you

Hey hey, what does the timeline look like for picking this up?

Hi good morning 👋 I'm hopeful that we can pick this up on Monday next week :)

Just as an fyi - I'm looking into this myself :) and will continue it post my vacation

Adding some notes (so I don't forget), after a short exploration this morning:

WDQS

  1. Help button click: no event / network calls. The user is linked directly to the linked page. As such, must check if there is a data table for page views of this page, where we could ascertain the referer as being from WDQS? But please note, there's also a help link banner at the top of the page... So cannot differentiate with referer
  2. Same as point 1 for help dropdown menu.
  3. Same as point 1 for tools button.
  4. Same as point 1 for tools dropdown menu.
  5. There is a network call for this (https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Data_access) - need to find corresponding table. However, the footer links are tiny!
  6. Not sure what this is referring to.
  7. There is a network call for this (https://developer.wikimedia.org/) - need to find corresponding table.
  8. For menu - are we meaning every click?

Am wondering, if instead of looking for clicks - we re-frame this slightly to look at page views and referrers. Then and/or create segmentation of users (anonymised) who view this content and then go on to create queries (to then infer the resources used have been reliable / useful)?

Also looked at event.mediawiki_web_ui_actions -do we have any knowledge about this? Also _interactions (table appears empty) for 2026... And then there is a frequent event for w3c.reportingapi.network_error - when a user clicks on items here. However, I think this is only sending info when there is an error.

Final note for clarification: what's the expected output of this task?

@catherine.kelsey.wmde it might be easiest to go over this in a quick meeting since I went through this originally with Andrew.

In a quick answer: I'd be fine with page views and referrers only, if that's what we have. It also all doesn't have to be "exact", it's to get an understanding of what data we have, what for and to continue to track that in a superset graph (there is a linked task).
And for missing things, I'd like to collect a list of what is not there, prioritise if we really do want tracking there and request tracking from the WMF for those.

Hey @Ifrahkhanyaree_WMDE sure - have put something in for tomorrow! Was just adding here my notes ahead of this :)

karapayneWMDE set the point value for this task to 5.Jul 14 2026, 2:38 PM
karapayneWMDE set Final Story Points to 1.
karapayneWMDE changed Final Story Points from 1 to 5.Jul 28 2026, 2:47 PM