Last modified: 2012-09-27 12:14:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T41768, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39768 - Article Feedback Shows CTA5 to readers too frequently
Article Feedback Shows CTA5 to readers too frequently
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ArticleFeedbackv5 (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-29 17:02 UTC by Fabrice Florin
Modified: 2012-09-27 12:14 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Article-Feedback-Bug-CTA5-Only-for-Readers.png (192.34 KB, image/png)
2012-08-29 17:02 UTC, Fabrice Florin
Details

Description Fabrice Florin 2012-08-29 17:02:23 UTC
Created attachment 11036 [details]
Article-Feedback-Bug-CTA5-Only-for-Readers.png

It appears that readers get CTA5 (View feedback) too frequently after they post feedback on English Wikipedia.

I just posted feedback 5 times in a row as a logged-out user on the Golden-crowned sparrow page and got CTA5 each time:
http://en.wikipedia.org/wiki/Special:ArticleFeedbackv5/Golden-crowned_Sparrow

Note that this CTA5 call was intended primarily for editors, not for readers:
http://www.mediawiki.org/wiki/Article_feedback/Version_5/Feature_Requirements#CTA_5:_View_feedback

This issue could be related to the anomaly that increased the number of anonymous moderators in recent days. If readers are getting this CTA5 as frequently as I am, then of course they would be viewing the feedback page more often.

Note that this could be caused by old cookies picking up CTA5, because when I post feedback using Chrome in incognito mode, I get CTA1 instead. Either way, this needs to be investigated further, as it could be causing too many readers to go to the feedback page.

One possible option would be to restrict all non-editors from seeing this CTA5.

Also, something strange is going on with the URL for the CTAs, as you can see in the attached screenshot: instead of saying CTA5, it is showing a long number, instead of CTA5 in the ref tag at the end of the URL. Could this have something to do with it?
Comment 1 Matthias Mullie 2012-08-29 17:18:34 UTC
The thing in the url is the id of the feedback post, so that it can be retrieved on placed on top of all other feedback, so that's normal.

Also, constantly getting CTA5 is normal as well: your first visit, you're being bucketed one of the CTA's (according to the percentages)
The core bucketing code saves your bucket in a cookie, so for every new visit, you will consistently get to see CTA5.
If you got bucketed CTA1, you would consistently be seeing CTA1.
Comment 2 Fabrice Florin 2012-08-29 17:50:11 UTC
I think we may have a misunderstanding about what we would like to do with the CTAs. 

We don't want people to be getting the same CTA all the time, which is a bit repetitive and get annoying over time. Instead, we would rather show a different CTA each time, that is appropriate to your user group.

So if you are a reader, we would alternate between these CTAs:
* CTA1 - Edit - 50% of the time (unless this is a protected or semi-protected page)
* CTA4 - Create an account or log in - 20% of the time (if they are logged out)
* CTA5 - View feedback page - 20% of the time 
* CTA2 - Learn more - 10% of the time (or in place of CTA1 if this is a protected or semi-protected page)

But if you are a registered editor, we would alternate between these CTAs:
* CTA5 - View feedback page - 90% of the time 
* CTA6 - Visit Teahouse - 10% of the time (if they are auto-confirmed)

And if you are an anonymous editor, we could alternate between these CTAs:
* CTA5 - View feedback page - 70% of the time 
* CTA4 - Create an account or log in - 20% of the time (if they are logged out)
* CTA6 - Visit Teahouse - 10% of the time (if they are auto-confirmed)

Would this be possible? Or does the current bucketing scheme not support this scenario? If there is an issue, we could redesign this to match what the technology can do. 

This is an important feature to get right, because with an an estimated one million feedback posts per month when we reach 100% deployment, this will be a very high traffic feature, that could have a big impact on the behavior of people who post feedback.
Comment 3 Matthias Mullie 2012-08-30 15:22:39 UTC
Pushed update to constantly rebucket users (rather than always serving them the same CTA) to Gerrit (https://gerrit.wikimedia.org/r/#/c/22032/) & prototype

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links