Still confused - some additional questions

Hi Xiaoming, Tanks for your kind reply. I'm still confused and I have to make sure, we get the whole picture, before we preceed in any direction with this project. Here are some additional questions, the numbering is responding to your answers. 1. To be sure: The quick start page says

Best practises for developing a new tool with different devs while keeping old tool running?

Currently we are running our own a Google AdWords API tool for internal use. This tool is several years old and there's lot more than transitioning to the new Ads API to do to keep it up to our needs. Now we decided to do a fresh start with different developers and a complete rewrite of our app

Re: Is there an annual audit for each API application?

I would like to bump up my question. Could anybody provide me with some more details on this topic? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~

Is there an annual audit for each API application?

Following all the buzz around the pressure on API devs using scraping or scraping data, I stumbled upon the statement of Raven CEO P. Keeble : > > Raven submitted its application for Google AdWords’ annual audit. If you > pass the audit, yo

Re: best practices for preventing any interruption for API usage

Perfect! Thanks a lot! We do not disable a developer token based on algorithms, we always reach > out to the developers a couple of times before taking any action. However, > in practice, we find that developers tend to miss the email due to various > reasons, and would notice only much later o

Re: best practices for preventing any interruption for API usage

Hi Anash, thanks for your clarification. Topic 1-4 seems obvious - I spend a lot of time reading and trying to understand all the RMF and T&C. If we fail with basic stuff like keeping our contact information upto date, then it's obviously our own fault. We are concerned about problems which migh

best practices for preventing any interruption for API usage

Our company is relying heavily on AdWords API for internal reporting and monitoring. In the meantime uninterrupted API usage is business critical. We read about tokens getting revoked for a variety of reasons and so we're really concerned that one day we'll run into troubles. From our own exper

Re: Transfer a token and free API units to another account

Thanks Ewan for clarifying this! You are right: a dev token is not tied to a specific account. I did some testing with my own account credentials. Login data is used for account access validation only. So we don*t need to transfer our token. One thing you should note though is that you're res

Transfer a token and free API units to another account

We got a dev token two years ago which is connected to our main mcc account. After a long and terrible annoying email exchange (several months of mostly repetitive mails) we finally managed to get free API units . Until now I was the only developer for our small in-house tools. Now we decided t