Page MenuHomePhabricator

Analyze performance of related pages feature
Closed, ResolvedPublic

Description

Currently 90% of users see related pages. 10% don't. We want to analyze the performance of related pages feature in these two buckets focusing on:

  • Feature on - does the user have the feature on?
  • CTR
  • Pageviews
  • Session length

Event Timeline

Chatted today with @ovasileva I advise a few things:

  • don't assume a user will be bucketed correctly. If a user exhausts localstorage on their browser (very easy in mediawiki) they will be re-bucketed on subsequent page views

Look at unique session ids in each bucket and compare to total amount to get a sense of click through rate in each bucket.
e.g.

  • events in feature-enabled bucket with unique user token / all events in feature-enabled bucket
  • events in feature-disabled bucket with unique user token / all events in feature-disabled bucket

@Jdlrobson Thanks! Just to be extra sure, is this sentence true too: "On each new page load, we decide randomly whether to record events during that pageview (1% probability) or not (99%)" - or is that instead decided once per session (when the new value for userSessionToken is generated)?

The first statement is not true. All sampling is per session.

I.e. If a user is bucketed for logging events and also bucketed with related pages disabled this should stay true until they clear their browser cache.

re-opening as continuation of analysis

ovasileva changed the task status from Open to Stalled.Oct 4 2017, 11:33 AM
ovasileva moved this task from 2016-17 Q4 to Product Owner Backlog on the Web-Team-Backlog board.

Note for the record: If I understand @phuedx correctly (T175918#3663909 ), the underlying data (from Schema:RelatedArticles) is affected by {T175918]}, i.e. all session-based metrics will be invalid.

Related pages data deprioritized due to more imminent requests.

ovasileva lowered the priority of this task from High to Low.
kzimmerman reassigned this task from ovasileva to Tbayer.
kzimmerman subscribed.

Closing as resolved because there was an analysis and answers; additional requests (reason for reopening) may no longer be valid.