Testing Visual Web Optimizer

visual web optimizerThe one and only reason I have this website is to test out theories, ramble incoherently and to see if I can quickly deploy something that I want to use in business. It’s the one and only reason I have a blog, no vanity, honestly. I think 99% of the times I am too lazy to RTFM so I like to experiment here. This is the reason this site is constantly dying and exploding. I am testing Visual Web Optimizer.

Orange Donglebangs are a prime example of what I’m talking about.

Anyway, I have to keep rambling on about something to meet the 300 word criteria to make sure this article gets indexed and stays in a search engine. What a pain in the arse.

The reason for writing this post is to announce that I am testing  Visual Web Optimizer and as such, I shall ramble on.

We (our company, check my LinkedIn for who “we” are) were recently approached by a company that sells the service on a much larger enterprise level for bazillions of beer tokens. I know we won’t get the buy in for this until we do proof of concept. So this is the start of it by using a scaled down version with much simpler (and consequently cheaper) functional capabilities. I’ve used services before that have split/multivariate testing capabilities but VWO (Visual Web Optimizer) does a little more, for example:

  • A/B Testing
  • Multivariate Testing
  • Behavioural targeting
  • Heatmaps
  • Usability testing

I have 29 days left to test it. Thanks for reading this, you’re testing it as we speak. It’s pretty hard to write 300 words and I’m stuck at around 200 at this point, but by the time I have gone back and edited it and actually fixed the rambling a bit it will probably be way more that 200 words, thus rendering that reference completely useless. Shit happens.

Question: Can we push this into a small project scenario, is it viable?

Good question, I guess I’ll let you know at the end of the 30 day trial, or possibly not (since followup for this is for me only).

Leave a Reply

Your email address will not be published. Required fields are marked *