
I recently had an opportunity to assist a client in setting up an Eloqua hosted campaign that utilized A/B testing using Omniture Test & Target. This was my first experience with Test & Target and from what I’ve seen so far it looks like a great tool for marketers to add to their toolkit.
The campaign consisted of Eloqua hosted landing pages, forms and thank you pages. The landing pages have traffic driven to them via Google Adwords. Eloqua captures the lead information and sends it to Salesforce, passing along a campaign id for closed loop reporting on the Salesforce end.
Omniture SiteCatalyst is leveraged to provide more segmented reporting on the Omniture end. Each landing page corresponds to a different campaign and pageNames are kept track of in the Omniture parameters as well – something that was key to setting up roll up reporting in Test & Target as well.
Now for the Test & Target part, this is the cool part. Each landing page has two versions (“A” & “B”). These are different landing pages in Eloqua and there are also “A” and “B” versions of the form and thank you pages. Now, when a lead comes into the landing page from a google ad (they go to the same url for “A” and “B” versions) Test & Target will route the lead to either the “A” track or the “B” track. 50% will go to the “A” version and 50% to the “B” version.
That’s it, you’ve got your usual closed loop reporting via Eloqua and Salesforce (you can see in Salesforce the track as well “A” or “B”), plus more reporting in Omniture SiteCatalyst and Test & Target. In Test & Target the reporting is straight forward, which version of landing pages worked better overall (“A” or “B”) to get a call to action click through and to get a form submission, plus on an individual page level, which version worked better.