How are you using personalized experiences (Audiences) for your tests?
The new Audiences feature gives you the ability to deliver a personalized experience that resontes with each visitor. It also provides huge opportunities for taking your Conversion Optimization tactics up a level.
How are you using the new audience features? Or, how do you envision using Audiences in the future?
It will be interesting to see what sort of audiences some people have created though.
Some really common ones I've seen are targeting logged-in or not logged-in users (based on a cookie), or targeting visitors who arrive from a certain PPC ad campaign (based on a query parameter like utm_campaign) or organic search (based on a referrer source like Google, Bing, or Yahoo).
These simple audiences are great for testing, but they're also good for running personalized content. For instance, right now we're geotargeting content to users in cities where we have an Optimizely Experience roadshow. We're actually not testing anything here -- just using Optimizely as a platform to quickly serve targeted content to these customers, and to help them find more information.
I've also worked with customers and partners who are really excited about using targeting based on other platforms like BlueKai. For instance, when a visitor is in a certain audience in BlueKai, that information can be used to determine whether a visitor will be served content through Optimizely. The same thing is possible with platforms like Qualaroo, where you can custom target experiments based on feedback a visitor has left previously.
I'm really excited to hear what everyone is using Audiences for -- I'm sure the Optiverse will come up with a lot of really cool ideas!
Setting custom cookies can be time consuming and difficult. But for some businesses, 'remembering' info about a user that isn't available by default, for instance a preference for discounted goods, consumption of a certain product information without purchasing, or simply spending a certain amount of time, can be a very actionable piece of information. Imagine taking that information, and delivering that visitor a highlight of a discounted product that meets their preference? That's creating an amazing experience that makes their life easier. Ultimately, there's no better way to improve your own business results.
The site has Facebook as a login option on their site. They then used that data to target experiments to people that liked specific competitors. This allowed them to have different messaging on their landing pages depending on what Facebook pages they have liked.
I thought it was a really cool way to use the Facebook data they were getting in the login to run creative experiments.
I have an "experiment validation" audience that I use to do live experiment testing/validation. I wrote a quick bookmarklet that I can use to set or expire a unique cookie on a site. Then I have an audience set up that restricts experiment display to the presence of that cookie. Thus, I can have an experiment be active but am the only person that sees it. It's particularly useful when working on an experiment that affects some complex scripting, AJAX function or doesn't easily load into the editor. I can also leverage the "Disable the force variation parameter" project code setting for added security.
Since adopting this method, I generally prefer it for validation because I'm looking at the actual, live experiment. I get a 100% accurate user experience that matches what a bucketed visitor will get rather than something simulated or temporarilly triggered.
I previously used the "optimizely_x" query string method to preview variations. Whenever I would pass around a preview link with that query string, someone would invariably say "well, it doesn't work if I (do something that ends up stripping out the query string)". That doesn't happen any more.
Also we have started to target UTM campaign strings from emails and testing different landing pages this way.
Optimization Co-ordinator at Widerfunnel
Optimization Co-ordinator at Widerfunnel