According to my dashboard at CMF Ads, in under 3 days CMF Spike sent it’s 50th visitor to my blog.  Below is a chart of the traffic received from Spike.  Considering it was Christmas Eve, a time traditionally dead for blogging, I consider these results quite promising.  In addition to the 35 Spike visits, there were also 12 visits from the CMF forum.  The biggest mystery (until I ask Ben) is why WordPress Stats only recorded 35 visits instead of the true 50.  Obviously, the plugin won’t count my own visit, leaving a gap of 14.

Date Referrer Views
12-26 cmfads.com/member/spikes 4
12-25 cmfads.com/member/spikes 7
12-24 cmfads.com/member/spikes 16
12-23 cmfads.com/member/spikes 8

Now let’s take a look at how Google Analytics views CMF Spike traffic.

CMF Spike Stats

As you can see, I received exactly 50 visits.  If Google doesn’t count my own visit, this still leave 11 Spikes unaccounted for.   I am going to attribute this discrepancy to “Drop and Run” traffic or visitors who have an ad blocker installed.  Since the Analytics code is in the footer, the entire page has to load before it counts the visit.  So what if 11 people chose not to stay and read.  38 visitors from Spike spent an average time on my site of over 2 minutes.  Their bounce rate was lower than my other traffic (mostly search engine) by 7%. 

Bottom Line:  The 50 visitors Spike sent from CMF Ads were mostly high quality.  64% of the traffic was considered “new”.  The 12 additional visits from the forum made up for the 12 Spike drop and run visitors.  A 12% surge in traffic over the Christmas holiday was well worth the $0.20 it cost me.