Posts about Web Development, Java, Magnolia CMS and beyond

Showing posts with label abtesting. Show all posts
Showing posts with label abtesting. Show all posts

7/14/2020

Redirect A/B Testing with Google Optimize

7/14/2020 Posted by Edwin Guilbert , 1 comment
It has been a while since my last post on A/B testing. Since then, a lot of things have changed, specially with Google Analytics API and how Google wants us to create experiments with their platform.

To cut to the chase, Google Experiments has been shut down in favor of Google Optimize. This has direct impact on the way we were integrating A/B testing on Magnolia, since we were using Analytics Management API to programmatically create and modify test experiments and this is not possible anymore with Optimize.

But not everything is lost since we can still take advantage of Magnolia Personalization and page variants in order to manually (not automagically) create and manage redirect experiments with Google Optimize.

Let's review what ab testing is for, from my previous post:

"In ab testing you could improve your conversions by comparing different versions of the same page. The idea is to change key elements that might improve your conversion rate. You usually have a original page (so called control page) and a variation of it. The users will get any of these versions randomly and after a period of time you can compare which version did better according to a goal (or conversion)."

... and how can be implemented in Magnolia with Google Optimize and the same example as before.

We are going to work with the demo website travel, specifically with the "about" page which contains a video. The goal here would be get this video played more times, so the metric we are going to use will be the play event on this element of the dom.

The original page looks like this:


And the variation will have a wider video, removing the left side links which might distract the visitor and prevent him from playing the video (our goal in this case).


To create a variation of a page, you just have to select "Add page variant" in the pages app of Magnolia.

          
Open the variant created and update the video component:


After publishing the variant, you need to connect these pages to Google Analytics using a Javascript snippet for tracking page views. You can embed this snippet with Marketing Tags in Magnolia (don't forget to include it in all your pages):


After publishing the snippet (or marketing tag in Magnolia) you need to send an event for every time a user plays the video included in the pages we want to test, so we need to create another marketing tag for that:



<script>
$(".video-wrapper video").on('play',function(){
  ga('send','event','video','play');
});
</script>

After publishing the snippet you need to actually record the number of play video events as conversions or "goals" in Google Analytics:




After the goal is configured, you might want to test it in the real time tab of Google Analytics, so every time you play a video in your page, an event gets registered as a conversion:


Additionally in order to use Optimize, you need to install it as a Javascript Snippet, including your container ID, in a similar way to what you did with Google Analytics:



At this point you finally have all prepared to start your ab testing on the page variants measuring video played metrics as a goal with Google Optimize:

"A redirect test is a type of A/B test that allows you to test different web pages against each other. A redirect test contains different URLs for each variant. Redirect tests are useful when you want to test multiple different landing pages, or a complete redesign of a page."

So lets create a redirect experiment with the following steps:

  • Create an experience of type "redirect test". Give it a name and provide the public URL of the page you want to test, in this case: http://yourserver/travel/about.html
  • Add as variant of the test, the variant of the page in Magnolia. The trick here is to use the internal URL of the page variant, in this case: http://yourserver/travel/about/variants/variant-0


  • Add as an objective the goal previously configured in Google Analytics, in this case, everytime a video is played:

  • Finally start the experiment! (don't worry about installation checked we are handling it with the marketing tags)


And thats all! Yu can always check how your test is going in the reporting tab of the Optimize dashboard. Remember you have to wait at least 1 day in order to see results.



After you are done testing you can always pick the winner and publish it as the final page in Magnolia :)

7/22/2016

A/B Testing webpages and google analytics experiments

7/22/2016 Posted by Edwin Guilbert , , No comments
A/B testing has been a trend among web content editors and marketers in the last few years. It is not a secret that high performing webpages will lead to more page visits, less bouncing rates and more conversions, which usually means more revenue.

However, we need to find out what we need to achieve with a specific page or content and try to measure it before performing any comparison tests.

We can measure how the webpage is performing through metrics, some examples are:
  • Call to actions (clicking on a button, playing a video).
  • Product purchases.
  • E-mail signups.
From these metrics you could calculate conversion rates, which basically states how many visitors have turn into customers in a given time frame. Examples of conversions could be visitors buying products in an e-commerce website or readers clicking on advertisements in a blog website.

You may be wondering: what ab testing has to do with any of this? Well, the answer is simple: In ab testing you could improve your conversions by comparing different versions of the same page. The idea is to change key elements that might improve your conversion rate. You usually have a original page (so called control page) and a variation of it. The users will get any of these versions randomly and after a period of time you can compare which version did better according to a goal (or conversion).

But we are not here just for explaining how ab testing works, we actually want to do some ab testing in a real web page with a concrete CMS and analytics software. So we will use Magnolia CMS for managing web pages and Google Analytics Experiments for recording/analysing statistics.

In Magnolia you can create variations of a page and editing them independently (this is only available on Enterprise editions).

We are going to work with the demo website travels, specifically with the "about" page which contains a video. The goal here would be get this video played more times, so the metric we are going to use will be the play event on this element of the dom.

The original page looks like this:


And the variation will have a wider video, removing the left side links which might distract the visitor and prevent him from playing the video (our goal in this case).


To create a variation of a page, you just have to select "Add page variant" in the pages app of Magnolia.


Open the variant created and update the video component:


After publishing the variant, you need to connect these pages to Google Analytics using a Javascript snippet for tracking page views. You can embed this snippet with Marketing Tags in Magnolia (don't forget to include it in all your pages):


After publishing the snippet (or marketing tag in Magnolia) you need to send an event for every time a user plays the video included in the pages we want to test, so we need to create another marketing tag for that:


<script>
$(".video-wrapper video").on('play',function(){
  ga('send','event','video','play');
});
</script>

After publishing the snippet you need to actually record the number of play video events as conversions or "goals" in Google Analytics:




After the goal is configured, you might want to test it in the real time tab of Google Analytics, so every time you play a video in your page, an event gets registered as a conversion:



At this point you finally have all prepared to start your ab testing on the page variants measuring video played metrics as a goal. You can automatically create experiments (as how Google calls them) in Magnolia using the A/B testing module:


As shown in the screenshot below that you can define the name of the experiment, the page, and variants involved , the duration and the goal for the test. The goal is dynamically retrieved from the Google Analytics account configured:


The module will create a Javascript snippet as a marketing tag, which you need to publish, so Google can forward users to one variant or the other:


After publishing the snippet you can already start the experiment in Google Analytics through the A/B testing module:


And that's all folks, you can always check your statistics in Google Analytics behaviour tab:


I hope you enjoyed my first post and find this useful. I will make a second part of this post explaining how to do ab testing manually without using the A/B testing and Personalisation modules  (both need the Enterprise version of Magnolia).