This is the second article in the series on conducting a domain traffic test. The first article can be read by going to: How to Conduct a Domain Traffic Test - Part 1
For the past 8 years I’ve been looking at nRPM (normalised RPM) numbers and routing traffic to the best solutions at any point in time. This has produced significant gains for clients and well worth the effort of getting messy in the numbers.
So now that there is an agreed set of definitions for metrics what do we need to do to conduct a traffic test? There are two main approaches:
1. Using baseline data
2. Using the existing monetisation account
When conducting a traffic test most domain owners provide us with the previous month’s stats to be measured against. One of the problems with this is that we don’t have the raw traffic numbers to generate a normalised RPM. One of the good things is although the stats are taken from a different time period they can be useful in focusing attention on which domains are clear winners and losers. Regardless of the outcome we need to understand why we are winning or losing.
For example, what’s the point in claiming victory if the domain has twice as much traffic during the testing period compared to the baseline? Although good, it would be false to say that it was due to traffic optimisation.
For larger traffic tests it’s far better to adopt option two and run the test by integrating the existing monetisation account into the traffic mix and then sample around 20% of the traffic elsewhere. If the new monetisation sources win the traffic, then all of that domain’s traffic is then moved to the new provider.
For example, let’s imagine that you have all of your traffic going to an account at Domain Sponsor. You want to check out if they are still the best solution for your traffic so you ask me to setup a traffic test. The first thing we do is integrate your existing Domain Sponsor account into ParkLogic and then leave 80% of the traffic still flowing through to DS while we test other monetisation solutions with the remaining 20%.
So rather than having to move all of your traffic you are now only risking 20%. Remember that 20% will earn some money (hopefully more than DS) so your revenue risk is more than likely going to become a win. What’s even better is that we can clearly establish a nRPM for the traffic flowing through to DS and know beyond any doubt who is actually paying the best at that point in time.
With traffic optimisation it’s vitally important that each domain is reviewed and treated as a unique case. There is no point in optimising across an entire portfolio is you don’t also focus on the domains themselves. It’s like the old saying, “look after the pennies and the dollars will look after themselves.” The domains are the pennies and the portfolio is the dollars.
The next article will continue to unpack what metrics we focus on in a traffic test.
Michael Gilmour has been in business for over 32 years and has both a BSC in Electronics and Computer Science and an MBA. He was the former vice-chairman of the Internet Industry Association in Australia and is in demand as a speaker at Internet conferences the world over. He has also recently published his first science fiction book, Battleframe.
Michael is passionate about working with online entrepreneurs to help them navigate their new ventures around the many pitfalls that all businesses face. Due to demands on his time, Michael may be contacted by clicking here for limited consulting assignments.