How should I best implement my code to have successful uploads of offline conversions

[freddi...@outlook.com]

Hello,

currently we have a job scheduled every hour which takes offline conversions from our database and pushes them to AdWords. However, it ran through the first 7/8 times before it started getting a rateExceededError.

The way our code works is:

first retrieve all the accounts/sub-accounts of the MCC

then proceed to push all of the conversions in our db from the last 24 hours to each account,

removing the successful uploads until the list of offline conversions is (hopefully) whittled down to 0 or all the accounts have been exhausted.

I did this because it was tricky to get information about which account the GCLID is linked to so it was easier to throw them all at the wall and see what stuck.

So, how should I refactor the code to work best on an hourly schedule and avoid the rateExceededError?

I'm not currently using the batch job service and have been reading about it but before I began a code refactor to implement that I wanted to make sure I wasn't missing a trick.

[Shwetha Vastrad (AdWords API Team)]

Hi Frederic,

You might run into RateExceededError if you have a basic access developer token and exceed your daily quota of 10,000 operations per day. The RateExceededError contains three fields, one of which is the rateScope which can used to identify the scope of the rate that was exceeded. It also contains the retryAfterSeconds field which is the suggested number of seconds your application should wait before retrying the request. 

This guide provides more details on how to handle RateExceededErrors. If the rateScope is DEVELOPER, I suggest that you apply for standard access for your developer token by completing the AdWords API Standard Access Application Form. 

I'm afraid BatchJobService doesn't support OfflineConversionFeedOperation. Let me know if any of the strategies listed in the guide I provided work for you. 

Regards,

Shwetha, AdWords API Team.