Once you have a better picture on the current state. It’s time to try and improve it. A good way to do it is by using the option to serve different pages to unique visitors and measure the differences.
Following our e-Commerce site example, there are few options to test:
- Create few versions of your ‘buy’ page.
- Change modules on a certain page.
- Change the landing pages.
- Change the funnel: number of pages, modules, steps etc’.
Few guidelines to gain more reliable results:
- Test a few elements at a time – If you change multiple elements on each page, it can be difficult to figure out which element or combination of elements was responsible for the best results. For example, create multiple pages but change only the main image on each page, and keep the same layout and text to ensure that any difference between the page results is due to the image.
- Use high-volume pages – The more often that people see a page or complete a goal, the less time it takes to gather data.
- Make bold changes – Users can miss small changes and you can end up with inconclusive results.
- Keep testing – With follow-up testing, you can build on the success of your experiment. Did one headline encourage a lot more purchases? If so, test it alongside a product image or an image of a spokesperson.
Types of goals
You can set up different type of goals:
- URL Destination goals – An experiment that uses a URL Destination goal focuses on getting users to view a specific web page. Use this kind of goal to find out things like how well your test pages encourages users along a path to a product page, a page that includes the location of your business, or pages on which you’re selling ads.
- Event goals – An event goal focuses on getting users to perform a specific action on a page. Use this kind of goal to find out things like how well your test pages encourages users to sign up for a newsletter, view a video, or click “Pay With Card” for a product.
- Session Duration goals – Use this kind of goal to see how well your test pages encourage users to spend time on your site. For example, if you’re running a news site, you want to see that users are spending enough time to read the articles, and enough time to validate the rates you charge for advertisements.
- Pages per Session goals – These goals help you understand whether users are consuming the amount of content you want. In many cases, you will want to combine this metric with the time they spent on your page. This is a good proxy to ‘consuming’.
How to (t)set
- Sign-in to the Google Analytics and select the view (profile) in which you want to create the experiment.
- Click the Reporting tab – It’s located on the top left of the screen.
- Expand the Behavior section (on the left menu), then click Experiments.
- If this is your first experiment, the page will look a bit empty (just like in the image below). Click ‘Create Experiments’ button in the image below and get ready.
Name your experiment and set an objective. The objective should be a goal we define in section Set Up Goals. There are other options to configure: percentage of traffic to this experiments. If you are running a more risky test you might want to limit the percentage of users that will get the new version. However, if you wish to see results faster, make the percentage higher.
In this step we will fill the two versions of the testing elements.
You can have more than two versions.
In this step we have the option to get the new JS code. If you are working in a company that got a team that run operations, you can also mail it to them (e.g. webmaster of the site) so they could add it to production.
This is the last step in the process. We review the test we are going to run. You can see in the picture below that GA found our code on one page and not on the other. It’s important to check it against your production servers so you will know for sure that data is being collected.
Only after you fixing all the issues, click on ‘Start Experiment’.
You should check the results after the first few hours to see that there isn’t any mistake in the definitions.
- A resource for users and developers to discover what’s possible with the Google Analytics Platform.
- Interesting code on Google Analytics: https://github.com/googleanalytics
- The Google Analytics experiments framework enables you to test almost any change or variation to a property in order to see how it performs in optimizing for a specific goal.
- Conduct A/B testing on the server side or client side.