Problems updating Google ADS API revenue

Mauro Gomes Barletta

unread,

Jun 24, 2024, 11:48:45 PMJun 24

to Google Ads API and AdWords API Forum

Since June 17th, we have been having problems updating revenue for our Google Ads campaigns. We are using lib 24.0.1, reaffirmation method. We've been using it for a long time and we've never had this kind of problem, could you help us?

conversion_adjustments { adjustment_type: RESTATEMENT restatement_value { adjusted_value: 5.360000133514404 } conversion_action: "customers/7328754187/conversionActions/277180252" adjustment_date_time: "2024-06-18 16:32:46-03:00" gclid_date_time_pair { gclid: "CjwKCAjwmrqzBhAoEiwAXVpgoli9PZ1DrhqG95Zqhy4zt0MSikByljAZ3fUhzy8JGMn0GBf9Ul4LTxoC1PQQAvD_BwE" conversion_date_time: "2024-06-16 22:41:55-03:00" } } partial_failure: true partial_failure_error { code: 3 message: "The conversion for this conversion action and conversion identifier can\'t be found. Make sure your conversion identifiers are associated with the correct conversion action and try again., at conversion_adjustments[0]" details { type_url: "type.googleapis.com/google.ads.googleads.v17.errors.GoogleAdsFailure" value: "\n\340\001\n\003\230\007\005\022\272\001The conversion for this conversion action and conversion identifier can\'t be found. Make sure your conversion identifiers are associated with the correct conversion action and try again.\"\034\022\032\n\026conversion_adjustments\030\000" } }

Google Ads API Forum Advisor

unread,

Jun 25, 2024, 6:03:30 AMJun 25

to mauro.b...@getninjas.com.br, adwor...@googlegroups.com

Hi,

Thank you for reaching out to the Google Ads API support team.

Based on the information provided, I understand that you are getting CONVERSION_NOT_FOUND error while adjusting conversions using the Google Ads API. Kindly note that the adjustment fails with a CONVERSION_NOT_FOUND error if any of these conditions are met:

The conversion was never reported.
The conversion was reported less than 24 hours before the adjustment attempt. In some situations, this could lead to a TOO_RECENT_CONVERSION error instead.

I would recommend you to kindly refer to the "Requirements" documentation for more information. I would suggest you to refer to the Monitor offline data diagnostics documentation as it helps to find the overall health of the conversion upload processes. If you are still facing these issues even after following these requirements, then kindly share us the updated API logs (request and response logs with request-id and request header) generated at your end to better assist you further.

You can send the details via Reply privately to the author option, or direct private reply to this email.

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJRz1:ref" (ADR-00243595)

Thanks,

Google Ads API Team

Register for the upcoming workshop: Performance Max and the Google Ads API!

Ben Webster

unread,

Jun 25, 2024, 10:13:38 PMJun 25

to Google Ads API and AdWords API Forum

Hello,

Since the 17th June we have also been getting the exact error above with the only difference being we currently use V16 and not V17. We adjust values on multiple customer accounts and all are experiencing this error.

Thanks,

Ben

Google Ads API Forum Advisor

unread,

Jun 26, 2024, 2:47:57 AMJun 26

to bweb...@mediahawk.co.uk, adwor...@googlegroups.com

Hi,

I will check with our team regarding your issue and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

Google Ads API Forum Advisor

unread,

Jun 26, 2024, 8:26:32 PMJun 26

to bweb...@mediahawk.co.uk, adwor...@googlegroups.com

Ben:

This is part of a larger know problem just discovered. There is a team of engineers working on it. I'll report back here when I have an update.

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJRz1:ref" (ADR-00243595)

Thanks,

Bob Hancock
Google Ads API Team

Google Ads API Forum Advisor

unread,

Jul 10, 2024, 8:57:08 PMJul 10

to adwor...@googlegroups.com, bweb...@mediahawk.co.uk

Folks,

This issue should be fixed now. Let me know if you continue to experience any issues.

This message is in relation to case "ref:!00D1U01174p.!5004Q02tJRz1:ref" (ADR-00243595)

Thanks,

Anash Oommen
Google Ads API Team

Reply all

Reply to author

Forward