| 11:37 am on Jan 2, 2006 (gmt 0)|
We got reduced from 23 Mln to 1.5 mln while we have much more accounts and traffic this/last month. Very weird, i asked my Google rep about it today.
| 12:18 pm on Jan 2, 2006 (gmt 0)|
I think and hope that this is a bug......
| 11:44 pm on Jan 2, 2006 (gmt 0)|
Armi, I don't think this is a bug. Rumors have been swirling for a long time that G would reign in API access, and now it looks like it's happening.
| 1:38 am on Jan 3, 2006 (gmt 0)|
This is just stupid.
Are people actually building 'business critical' tools around the Google API?
Our internal reporting systems (which are critical to our operations) rely on the API, and we're reluctant to do anything more with it due to concerns about running out of quota.
This change just solidified that decision. We can't rely on things that change without notice and have arbitrary limits.
Our quota is 20% of what it was previously. That's still 5x more than we've used in any previous month, but not enough 'padding' for my liking.
Is this a 'use it or lose it' change? Can anyone comment on what their usage history was vs. the quota they had available?
| 2:56 am on Jan 3, 2006 (gmt 0)|
Looks as though the following page gives an indication why this has happened (many knew about this but didn't expect the quota cut):
It looks as though you will have to pay if you are a medium/heavy user.
| 6:00 am on Jan 3, 2006 (gmt 0)|
I think something is being recalculated, and wouldn't go by what you're seeing right now.
I've seen API credits for one account change 3 times in the past day.
| 10:46 am on Jan 3, 2006 (gmt 0)|
With this Quota I canīt continue my campaigns....I donīt think that Google wants this.....
|Kings on steeds|
| 1:03 pm on Jan 3, 2006 (gmt 0)|
i spoke to google just about about this, stupid loss in credits, down from 44 million to just 1.5 we use that a day here... and from what they are saying it is sounding more like an error, and i am hopeing it is!
| 2:04 pm on Jan 3, 2006 (gmt 0)|
Inbound - the commercial dev program sounds great, but can anyone find any mention of it outside the announcement?
Annoying as it may be to pay for quota, I understand why they might do this.
At least then we'll be able to get support for the API and will have an option to get more quota if needed.
| 8:39 pm on Jan 3, 2006 (gmt 0)|
My Rep confirmed that it is an error.
| 9:11 pm on Jan 3, 2006 (gmt 0)|
Confirmed by ours well.
| 7:27 am on Jan 4, 2006 (gmt 0)|
The quota is back to normal as of this morning in our account.
|Kings on steeds|
| 10:40 am on Jan 4, 2006 (gmt 0)|
as is mine, looks as if this problem has been sorted!
| 4:42 pm on Jan 4, 2006 (gmt 0)|
The AdWords API announced [adwordsapi.blogspot.com] that it was a bug and that they're working to fix the issue.
[edited by: Brett_Tabke at 4:57 pm (utc) on Jan. 4, 2006]
[edit reason] added link... [/edit]
| 11:12 pm on Jan 4, 2006 (gmt 0)|
Allow me some ignorance on this issue, but would this API bug have anything to do with the horrible AdSense eCPM on my site the first four days of this year?