Brian Quinton at MultiChannel Merchant published a great article yesterday on the Google CPA beta test (article here).  In addition to some of the same observations I have made previously (here), Brian highlights a few additional potential limitations to Google’s CPA initiatives that I think are worth mentioning.  These include:

• Advertiser Concerns Over Sharing Transaction Data with Google.  Several ad industry experts quoted in the article highlight this as a concern, especially for large clients.  Because Google often controls such a large share of their online advertising wallet (non-CPA based), the advertisers don’t want Google to know their actual ROI on that advertising, out of fear that this will lead to higher rates, more competitors, etc.
• Double Counting Conversions.  Conversions may take place days or even weeks after a user clicks on a Google CPA ad and picks up a Google tracking code.  But what happens if that same user also accessed another tracking link from a third party affiliate network for the same offer prior to the actual conversion?  The result is that the advertiser may get charged CPA ad fees from both Google and another CPA network for the same action.  This is one of the things that I love about the Jellyfish model, since our customers have a built in incentive (through cash back savings), to ensure that they utilize the Jellyfish CPA link immediately prior to their purchase, creating less likelihood of a double counting issue.  

The article is worth the read for anyone following Google’s CPA test.      

This entry was posted on Thursday, April 5th, 2007 at 5:33 pm and is filed under Google AdSense, Industry News, Cost Per Action Advertising. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.