Re: Api V201702 catch upload offline conversion error

Hi Mike, Unfortunately, you would need to wait for 24 hours before trying to upload a new conversion. Along with that, you would also need to comply with the validation rules listed on this page . Reg

Re: Api V201702 catch upload offline conversion error

Hi Vishal, We're currently in the process of uploading every conversion action with their accurate values through the API to take advantage of all the machine learning that tCPA and tROAS has to offer. We have a significant number of offline conversions that we would like to upload as soon as w

Re: Api V201702 catch upload offline conversion error

Hi Vishal, We're currently in the process of uploading every conversion action with their accurate values through the API to take advantage of all the machine learning that tCPA and tROAS has to offer. We have a significant number of offline conversions that we would like to upload as soon as w

Re: Api V201702 catch upload offline conversion error

Hello. TY for your help, The TOO_RECENT CLICK was not my problem. It was the fact than i did not manage to catch errors in order to correct it. I've found the response here : https://developers.google.com/adwords/api/docs/samples/php/error-handling in did not have the ->enablePartialFailure()

Re: Api V201702 catch upload offline conversion error

Hi, Please refer to this document for details on each of the error messages in your email. The fix for TOO_RECENT_CLICK error would be to wait for up to 24 hours (i.e.

Api V201702 catch upload offline conversion error

Hello, i've an issue when migration on the v201702 I used tu use try / catch to uplad conversion as sometimes i've errors like EXPIRED_CLICK or CONVERSION_PRECEDES_CLICK and also TOO_RECENT_CLICK But with the new api, when i try it i have always a fatal error I use this demo : https://develope