markdown example

gistfile1.txt

# AB Testing in pagetorrent

## Limitations of Test and target

- Cross domain requests
- Can cause tracking issues when clicking outbound links. The request doesnt finish before the link does.
- Difficulty tracking periodical tests.
- Expensive license

## Pluses of Test and target

- Well established system
- Has simple built in reporting
- Has easy to use segments
- Pretty easy to setup a more straight forward test once you know how


## Pluses of using PageTorrent instead

- Inhouse, giving us more control
- Gets outside of the clientside decision making and requests to omniture's server
- Potentially integrate into DiMITRI and other aspects of our offering.
- Will save on company costs over time.


## How?

Ability to identify a container in A/B split test mode. Each view would then have some sort of test label field. The test mode of the container would have the options to do an even split, as well as resort to view filters. The view filters could then be used to label a test for certain URLs, and be 50/50.

- The even split would be evaluated if selected
- The split would be an AND relationship to the outcome of the view filters. The current view filter evaluation system stays as is

## Reporting

I imagine some of the stuff DiMITRI has going for it could be used here. I just do not know how easily we could tie a test into that to create a report system for 
A/B split testing.

### We would need: 

- Segmentation of browsers, operating systems, and the ability to setup custom segments. Such as url contains X, or referrer is from google, etc.
- To be able to view the data between a given date range.

<object width="425" height="344">
  <param name="movie" value="http://www.youtube.com/watch?v=rAXsN_p40R4&feature=feedrec"></param>
  <param name="allowFullScreen" value="true"></param>
  <embed src="http://www.youtube.com/v/-YUxbDEPFiM&hl=fr&fs=1"
  type="application/x-shockwave-flash" allowfullscreen="true"
  width="425" height="344"></embed>
</object>