Inquiry Regarding Limit on ConversionValueRuleOperations via MutateConversionValueRuleSetsRequest

[Nishant Pandey]

Hey Google Ads API Team,

We recently encountered an issue when using the MutateConversionValueRuleSetsRequest. We found that it now only accepts a maximum of 500 ConversionValueRuleOperation resources. Adding any further rules results in the following error from the API:

{
  "Failure": {
    "errors": [
      {
        "errorCode": {
          "collectionSizeError": "TOO_MANY"
        },
        "message": "Too many.",
        "location": {
          "fieldPathElements": [
            {
              "fieldName": "operations",
              "index": 0
            },
            {
              "fieldName": "update"
            },
            {
              "fieldName": "conversion_value_rules"
            }
          ]
        }
      }
    ]
  }
}

This behavior was also confirmed on the Google Ads UI, where attempting to add a 501st rule results in an unexpected error asking users to try again later.

Could you please confirm whether this change is expected? Additionally, is there any documentation available that outlines the various limits related to Conversion Value Rules?

Looking forward to your response.

Best regards,
Nishant Pandey

[Google Ads API Forum Advisor]

Hi Nishant,

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

With regards to your concern, it appears that you are encountering the TOO_MANY collection size error while creating conversion value rules. Make sure the number of conversions value rules per customer. I would recommend you to check this help center article Set up conversion value rules for more information. Note that there is nowhere mentioned in the documentation on the specific limit on the various limits related to Conversion Value Rules. Since this behavior is confirmed in the Google Ads UI where attempting to add a 501st rule results in an unexpected error, it is obvious that the API will also not allow adding more than 500 conversion value rules.

In order to further investigate, can you kindly provide the complete API logs (request and response with request-id and request header) generated along with the uncropped UI screenshot of the Google Ads account (with visible customer ID) of where you are encountering this same issue to further assist you better. 

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. 

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.!5004Q02vGzle:ref" (ADR-00286777)

Thanks,
 

Google Ads API Team

Feedback
How was our support today?