The default bug view has changed. See this FAQ.

A/B tests for social sharing widget



Mozilla Developer Network
Wiki pages
2 years ago
a year ago


(Reporter: hoosteeno, Unassigned)




(1 attachment)

From bug 875062 comment 43:

I think that our next step should be outlining 3 A/B tests we can run for placement and 3 A/B tests we can run for button design:

For location I suggest:
1) Top of the page under the title
2) Inside the right column TOC, at the bottom, if there is one on the page
3) End of the article (where they are now)

For button design I suggest:
1) Current design
2) Logo only, with no heading
3) A derivative of the fellowship design

First step on this is designs; second step is the test; third step is deploying the most successful combination.
Severity: normal → enhancement
Created attachment 8585763 [details]
3 styles in 3 positions

Here's a screen shot of 3 different styles displaying in the 3 different positions.

For the tests, of course, only one style at a time will be visible in one position at a time.

Comment 2

2 years ago
Commits pushed to master at
Bug 1145630: Social Sharing A/B tests

Styling for 3 different types of buttons going in 3 different places.


All hidden by default at the moment and need the class .show added to them to display.
Merge pull request #3142 from stephaniehobson/bug-1145630-sharing-ab-tests

Bug 1145630: Social Sharing A/B tests

Comment 3

2 years ago
Commits pushed to master at
Bug 1145630: Manually activate social experiment
Merge pull request #3187 from openjck/bug-1145630-manual-social-experiment-activation

Bug 1145630: Manually activate social experiment
Making this depend on the bug for storing the shortened urls in the db.
Depends on: 1182210
No longer depends on: 1182210
Depends on: 1194257
In bug 1182210 we decided not to store the short urls from bitly, because bitly charges extra to preserve the utm_* parameters. So, for this bug we need to change the share urls from short urls to regular long urls, which is bug 1194257 now blocking this bug.
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.