Difference between revisions of "FrontPage AB Testing"
(Starting on the frontpage task) |
Brandon Bot (talk | contribs) (Refactored to use standard open task categories Category:OpenTask, Category:DevelopmentTeam) |
||
|
(3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
<noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''[[PairDays?|3]]''') [[FrontPage AB Testing]] ('''[[Who?|?]]''') {{JustTinyEditIcon|FrontPage AB Testing}}<noinclude></big> | <noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''[[PairDays?|3]]''') [[FrontPage AB Testing]] ('''[[Who?|?]]''') {{JustTinyEditIcon|FrontPage AB Testing}}<noinclude></big> | ||
__NOTOC__ | __NOTOC__ | ||
| Line 11: | Line 10: | ||
*# where they came from | *# where they came from | ||
*# which version of the page they saw | *# which version of the page they saw | ||
| + | *# how long they stayed on the page | ||
*# what action(s) they took | *# what action(s) they took | ||
* There is an easy method for generating a report that compares the number of people who took each action across each of the candidate pages | * There is an easy method for generating a report that compares the number of people who took each action across each of the candidate pages | ||
* There is an easy method for adding a candidate front-page and weighting how often it gets shown to visitors | * There is an easy method for adding a candidate front-page and weighting how often it gets shown to visitors | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Steps to get to [[DoneDone]] == | == Steps to get to [[DoneDone]] == | ||
* All visitors to our site are assigned a session cookie | * All visitors to our site are assigned a session cookie | ||
* Every access to the mainpage outputs the session id, as well as the version of the page that is displayed into our access log | * Every access to the mainpage outputs the session id, as well as the version of the page that is displayed into our access log | ||
| + | |||
| + | == Queries to Answer == | ||
| + | |||
| + | Give a page (e.g., MainPage) | ||
| + | * Where did they come from (referrer) | ||
| + | * Which content did they see | ||
| + | * How long did they stay on that page | ||
| + | * Where did they go | ||
| − | [[Category: | + | [[Category:OpenTask]] |
| + | [[Category:DevelopmentTeam]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 21:00, 7 February 2008
What (summary)
Why this is important
Our front page gets more traffic than any other page on our website. We need to have an easy mechanism for easily making changes to the front page and measuring the effects of those changes. This ability will help us iterate our way to a page that really satisfies someone rather than a page that confuses everyone :-)
DoneDone
- All visitor browsing trails that hit the front page are instrumented to record:
- where they came from
- which version of the page they saw
- how long they stayed on the page
- what action(s) they took
- There is an easy method for generating a report that compares the number of people who took each action across each of the candidate pages
- There is an easy method for adding a candidate front-page and weighting how often it gets shown to visitors
Steps to get to DoneDone
- All visitors to our site are assigned a session cookie
- Every access to the mainpage outputs the session id, as well as the version of the page that is displayed into our access log
Queries to Answer
Give a page (e.g., MainPage)
- Where did they come from (referrer)
- Which content did they see
- How long did they stay on that page
- Where did they go