Atlas is aware of the problem. They say the issue has to do with Google's API passing data incorrectly, but that the issue only affects a small percentage of accounts. In other words, although it’s a known issue it is not their biggest priority.
Atlas says they are waiting on Google to fix their API.
Google says, “Who’s Atlas?”
I have tried several fixes that Atlas has recommended.
1. Delete Channel and then add it back again.
2. Change from pixel to java tracking.
Do any of you who use Atlas OnePoint have similar problems? What did you do to resolve it? I find it hard to believe that I am just one of the unlucky few who have this problem.
In the past two years I've met with at least 200 of the top 1000 ppc advertisers. I have yet to find an advertiser whose use of AOP on Google goes well.
While it's true that the SE's API's tend to have more downtime than a Yugo, IMO AOP doesn't work well on Google because
a)it relies on Google's Traffic Estimator, which is 30% off at the individual keyword level 70% of the time.
b)it has a undereducated Google click model.
It it that small nice car produced in Yugoslavia?
