Closed Bug 846756 Opened 11 years ago Closed 11 years ago

a/b test positioning of products on start page

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED
2013Q1

People

(Reporter: atopal, Assigned: rrosario)

Details

(Whiteboard: u=user c=wiki p=1 s=2013.5)

We want to know if people can distinguish Firefox for Desktop, for Android, and Firefox OS even though they are using the same icon, and choose the right product on the start page. If they can, then changing the position of the products should have no effect on click throughs, if they can't there should be a pattern (like people clicking whatever is first in the list)

If it turns out that they can't distinguish those products, we need to work with marketing and creative to find a solution to the problem of similar names and identical icons.

For the first test, let's swap the position of Firefox for Desktop and Firefox for Android.
This seems like simple A/B test. See Bug 830753 for reference. That one was 2pts because we didn't know what we were doing back then.

For this, we need Ibai to create the content experiment in google analytics for us.
Whiteboard: u=user c=wiki p= s=2013.5 → u=user c=wiki p=1 s=2013.5
We need to define what's the goal of this. Is the amount of clicks to desktop? 

After that, I need the URL to the variation/s and I can generate the experiment.
(In reply to Ibai Garcia [:ibai] from comment #2)
> After that, I need the URL to the variation/s and I can generate the
> experiment.

Currently, https://support.mozilla.org/en-US/products shows:
Fx - Android - FxOS - Thunderbird

How about we add https://support.mozilla.org/en-US/products?b that shows:
Android - Fx - FxOS - Thunderbird

Is that enough or do we need more combinations?
We can make it work with it!

I'll put together the experiment and share the code this afternoon.
Assignee: nobody → rrosario
Deployed to prod now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
And the experiment is active.
You need to log in before you can comment on or make changes to this bug.