A user who gets to the bottom of an article on either mobile or desktop web is shown a list of other articles that are related to the one they just finished. The notion is that if the reader has gotten to the bottom of the article, they might be looking to read more about the topic and surfacing articles that are similar might be exactly what they are looking for. This has been release on apps and saw a 16% click-through (For users who saw it). Additionally, 25% of the users who saw read more results clicked through at least 1x in a __ period (I can't tell from the query here: https://docs.google.com/spreadsheets/d/1iyNqWgC8lNWk3ckSQJS_ACrfeW1UrBHOf58L97oeNqM/edit?ts=560ae622#gid=1184183009)
A/B tests in mobile-web beta show an increased CTR from pages enabled with read more. Read more launched on mobile and desktop web. Editors who have 'see also' sections, appreciate the new format and do not feel that this is an unwarranted step in the wrong direction.
== Goal Visibility
This is part of our external goal for the quarter
Launching on Android and iOS has shown a high level of success. Though, obviously, results will be different on the web, we have no reason to think it will be better or worse.
= Success Metrics
%CTR (click through rate, clicks/views) is >10%.
Ideally, we will be able to ensure that these clicks are not-cannabilistic (increasing overall clicks as opposed to taking clicks from blue links)--this might be possible to measure using the 'referer' field in page logs and doing a before/after analysis or, ideally, a/b test.
= External Dependencies
Community Liaisons are instrumental for this rollout.
Not sure if the new feature will be welcomed on desktop, which we, as a team, haven't touched yet. We hope the added configurability offered to editors (over the app editions), and the commitment it shows to honoring editor control in this regard, will be well received.
Not sure if we will be able to a/b test referrals from page (would likely require url appends..)
= Product Plan
This will be tested in beta first.
A user reaching the bottom of an article is shown the title and lead image for 3 articles that relate to the article they just finished.
We are able to measure the engagement clicks/impressions with this feature.
== User Stories
- A user reaching the bottom of an article is shown the title and lead image for 3 articles that relate to the article they just finished so that they can continue reading about that topic.
- Someone editing a wikipedia article can manually change the article suggestions using wikitext so that they can correct any erroneous or sub-optimal suggestions.
- An project stakeholder (such as PM or data analysit) is able to measure the engagement clicks/impressions with this feature so they can determine if it is adding user value.
== Metrics Implementation
We will want to track:
- impressions of read more suggestions (the lump--not each item suggested)
- clicks to read a suggested article
- the position of article (1,2,3)
- ideally: whether or not article was edited manually
- overall referrals from a page with read more
- overall referrals from same page without read more
== Timeline Estimate
- build read more according to mobile web specs
- launch on mobile web beta
- measure impact using event logs CTR (referral data won't be helpful at these numbers)
- discuss with community
- launch on mobile
- build for desktop
- launch on desktop (open discussion about whether we launch in beta first and/or do progressive rollout)
## Delivery Estimate
End of December on desktop?