Pages
Blogs
Flickr
Tags
amadesa api application clickmap click tracking code conference coremetrics corporate customer service email feedback google analytics heat map how to integration Marketing measure multiplicity omniture omniture discover optimization pathing plug-in rant simple sitecatalyst social media social networks statistics subject lines summit 2010 support Tao of J test & target testing twitter visual website optimizer web analytics yahoo web analyticsStuff I'm Checking Out
I am reading
Twitter: usujason- @OmnitureCare @ad0815 trying now. about 59 seconds ago from TweetDeckin reply to OmnitureCare
- @OmnitureCare k. i'll just append a prefix to the zero as a work around. about 3 minutes ago from TweetDeckin reply to OmnitureCare
- @OmnitureCare it's not the key, its a classification value. If it's zero, it ges dropped. about 6 minutes ago from TweetDeckin reply to OmnitureCare
- @OmnitureCare something weird with SAINT. Classifying a var with a single numeric digit. if the classification value is 0 (zero), no work. about 9 minutes ago from TweetDeckin reply to OmnitureCare
- In case you missed my webinar with Ian Michiels from the Aberdeen Group. http://bit.ly/aYqYhG about 16 minutes ago from TweetDeck
Avinash Kaushik
Crepuscular Light
Kevin Rogers
Pritesh Patel
Rudi Shumpert

Amadesa & Omniture Integration
Over a year ago, I had the opportunity to speak with Amadesa about creating an integration between their testing platform and Omniture SiteCatalyst/Discover. Having used Amadesa for A|B testing, I was happy with the reporting they provided but I was always finding myself wanting more. I wanted the ability to further dig into the performance of tests I was running using Omniture Discover in order to find hidden gems that were not easily uncovered in the Amadesa reports.
From that conversation, a straight forward integration was born between Amadesa and Omniture. If you are running both Amadeas and Omniture, there is no reason why you shouldn’t have the two products integrated, here is how:
1. Set up your A|B test using Amadesa. Contact your Amadesa representative for details on how to assign each test treatment a unique identifier that can be passed to Omniture.
2. Configure a Custom Conversion variable in Omniture. Identify an available eVar that will be used to capture test treatment identifiers. In my line of business, optimization is a critical component of the online business and I have dedicated multiple conversion variables used for tracking on-going optimization efforts. e.g. Home Page Optimization, Sign-up Optimization, etc.
3. Locate Omniture Page Code. The page code will look something like the code example below.
4. Update Omniture Page Code. Update the page code to include a reference to the Amadesa integration variable. For example, if you are capturing your Amadesa treatment version in eVar5, you would update your page code as follows:
s.eVar5 = (window.amadesaVesrion) ? amadesaVersion:”";
5. Deploy & Test. Deploy your updated code and run your Amadesa report in SiteCatalyst to verify data is being tracked correctly.
The real power of the Amadesa/Omniture Integration is the ability to uncover hidden gems. If you have the Omniture Discover product, you can explore how unique segments of your population are reacting to your test treatments.
Perhaps Amadesa is reporting that each of your test treatments are performing worse than your control, however upon further analysis, you discover that paid traffic is converting at a 60% lift for one of your test treatments. This gem would have been lost if you were simply relying on the out-of-the-box Amadesa reports but now, with your shiny new integration, you can target this test treatment to your paid traffic and watch the ROI roll in.