partial failure error while restatement purchase conversion

[Arjun Sharma]

Hi,

i am geeting partial failure error ,

gclid_date_time_pair {
  gclid: "*********"
  conversion_date_time: "2023-11-01 00:18:45+05:30"
}
conversion_action: "customers/2959363685/conversionActions/********"
adjustment_date_time: "2023-12-01 06:36:19+05:30"
adjustment_type: RESTATEMENT
restatement_value {
  adjusted_value: 1
}

HI 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.v15.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]

Hi,

Thank you for contacting the Google Ads API support team.

By reviewing your concern, I understand that you are encountering 'CONVERSION_NOT_FOUND' error, could you please confirm that you have already considered the Validation rules in Upload Conversion Adjustments? The adjustment fails with a 'CONVERSION_NOT_FOUND' error if any of these below 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.

Please note that when creating a ConversionAdjustment, the partial_failure attribute of the  UploadConversionAdjustmentsRequest should always be set to true. Follow the partial failures guidelines when handling valid and failed operations simultaneously.

If the issue still persists, could you please provide us with the complete API logs (request and response with request-id and request header) generated at your end and uncropped UI screenshot of where you are facing the issue.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qWTay:ref"

Thanks,
 

Google Ads API Team