So many domain owners get incredibly confused by all the different companies that want to monetise their traffic for them. Which one is best? How do I really know if they are better than another? What is the best way to run a test? All of these questions are vital if you wish to get the most out of your domain traffic.
In this article I will unpack the critical success factors of what makes a viable good traffic test so that you will always know that you are monetising your traffic with the right provider.
For a start, to eliminate any discrepancies in timing, all traffic tests need to be conducted simultaneously. What you don’t want to do is change your DNS to point to parking company A and then a few weeks later change the DNS to parking company B. The two separate periods of time introduce large errors in determining who is the real winner.
Without the proper tools, running a simultaneous test can be difficult but with a good partner this is eminently achievable. As an example, we find that at ParkLogic a number of clients use our services purely for benchmarking one monetisation source versus another. We’re happy to work with anyone on this.
The most important factor in a traffic test is understanding the definition of success. So many people fall into the trap of believing that revenue is the only metric that should be paid attention to. So is that the revenue for December or for September? Is that the revenue where there happened to be a 20% increase in traffic or not? Or how about the revenue when it just so happened that an advertiser paid more for the traffic by a mistake?
As can be seen, revenue, although important, is not the best metric to pay attention to during a traffic test. Many domainers have migrated to RPM (revenue per thousand visitors) in an effort to remove the distortions caused by variations in traffic.
For example, if you make $100 from 1,000 visitors then you have an RPM of 100. Let’s imagine that you did a test and you made $200 from 1,000 visitors from a different monetisation provider. Many people jump to the conclusion that the second monetisation provider is the clear winner with an RPM of 200…..and they would be wrong.
The problem with RPM is that it depends upon the views reported by each of the monetisation providers. Sadly, there aren’t any standards on reporting views therefore each provider has a different set of filters applied to the traffic which can dramatically change the number of views reported and ultimately the RPM.
It wasn’t so long ago that some parking companies used RPM more as a marketing tool to say they had the best in the industry! This was easily achieved by just filtering the traffic more aggressively, reporting less views which meant a higher RPM.
For a proper traffic test what we need is an unassailable metric that can be verified for each monetisation source that we wish to test. The only way to do this is to count the raw unfiltered traffic (ie. URLs) that we send to each monetisation provider for each domain and then see how much revenue that generates. This provides us with a normalised RPM (ie. nRPM) that we can then use for direct comparisons at any point in time.
Let’s take a look at some actual data for a domain (XYZ.com) across a ten day period of time (see below). Day 1 is the latest day’s data and Day 10 is the oldest. There are columns for URLs, nRPM and Revenue for 4 parking companies (1-4). The easiest way to understand what is happening is to read the table from the bottom up so that you can get an idea what is happening as the algorithms seek to move in on the higher paying revenue solutions.
Initially, the domain is only with parking company 4 and on day 7 forced sampling was implemented to expose the traffic to the other parking companies. At Day 6 parking company 4 was being beaten by parking companies 1 and 2. More traffic then flowed to those parking companies and away from two and 4 until parking company 2 began to perform and parking company 4 completely dropped out of the race.
In this example, the traffic flowing between the monetisation providers is very dynamic and moves around quite a lot due to the switching regimes being adopted during the sampling process. There’s a lot of moving parts and reasons why the traffic flows where it does but the whole time the algorithms are focused on increasing the domains revenue.
In the next article in this series I will really unpack how to conduct a structured traffic test and why most domain owners get this wrong.
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.