Click Fraud Blog

Case Study - Sometimes It Ain’t Click Fraud

 

 

June 11th, 2008

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

I was recently working with a client based in the US who had seen a masive increase in click through and no corresponsing increase in conversion. He contacted me with a view to investigate possible click fraud.

As a starting point I obtained an invalid click fraud report (see below). From this we can see an incredibly suspicious increase in clicks and cost per click

I asked for a copy of their web server logs to run through my analysis tool to see what was causing this problem.

The company works in the US mortgage space, a notoriously competitive and expensive place to advertise. An arena ripe for competitor click fraud attacks.

The client’s technical team went off to retrieve the logs for the particular weekend when the problem occcured, only to come back and report that the logs were not available. They could not be retrieved from the backups, they had gone missing! The month before and after were available but nothing for the suspicious weekend.

Lightbulbs lit up in my mind, but I did not want to alarm my client without any foundation. I thought this was an inside job.

Sure enough my client came back to me, a disgruntled employee had increased the cost per click and expanded the campaign widely . They also deleted the web server log files for the period in an effort to cover their tracks. The nett result was a click bill for perfectly valid clicks to the tune of tens of thousands of dollars. Needless to say the employee was shown the door very quickly.

The moral of the story, it’s not always click fraud, and only very trusted employees should be give the keys to your pay per click budget. The damage to the bottom line can be huge if your Adwords admin goes rogue.

These clicks were perfectly valid, and internal grudges is not an acceptable reason for a refund from Google.

Please bookmark or vote! These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Facebook
  • Google
  • StumbleUpon
  • Technorati
  • TwitThis
  • E-mail this story to a friend!

Other posts you may like

  • Other popular posts you may like

Tags:
Posted in Case Studies, Features |

June 11th, 2008

Comments

One Response to “Case Study - Sometimes It Ain’t Click Fraud”

  1. Russell Taylor Says:

    “These clicks were perfectly valid, and internal grudges is not an acceptable reason for a refund from Google.” Fortunately in both US and UK Law Google is responsible for their employees action and because the Cost Per Click was amended without the customer’s authorisation then they are responsible for the bill and not the customer. Google would legally not be able to recover this amount from their customer regardless of their stated Terms and Conditions. There are already several exaples of case law I know about which sets precedence for this, and these are well documented for anyone willing to search leagal records.

Leave a Reply

 Comment Form 

June 11th, 2008
June 11th, 2008