Flexible rule limits

[Mark]

Hi,

I'm looking to migrate an app from v12. Since v13, we have to use Flexible User Lists instead of Expression User Lists.

Now, since "OR of ANDs is the only supported type for FlexibleRuleUserList.", we have to think differently. Instead of having a bunch of items in a single UserListRuleItemGroup, we have to have a single item per group, and then set the  UserListFlexibleRuleOperator to OR, so that each set of groups is in an alternative relation to others. This essentially means, if my logic checks out, that any individual rule item being true will result in the User List being applied.

I've implemented this as a proof-of-concept, but I keep getting "TOO_MANY" errors when trying to create or update user lists with 27 or more groups in each inclusive FlexibleRuleOperandInfo. This is weird, because when retrieving user list created pre-v13, it shows as many as 120+ groups being in a single FlexibleRuleOperandInfo. Anyway, I assume it's how the data is represented in the API since the removal of expression user lists and it cannot be created in the same way. 

So, in short, my questions are:

1. How many groups can I have in a single FlexibleRuleOperandInfo?
2. How many FlexibleRuleOperandInfo  can be added to  FlexibleRuleUserListInfo's  inclusive_operands[] ?

Thanks! 

[Google Ads API Forum Advisor]

Hi,

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

By reviewing your concern, I understand that you're encountering "TOO_MANY" errors when attempting to create or update user lists with 27 or more groups within each inclusive FlexibleRuleOperandInfo. Please note that the 'v13' is deprecated and about to sunset on June 7, 2023. I would recommend migrating to the latest version v15 and you may follow this link to Upgrade to the latest version.

In order to further investigate to answer your queries, kindly 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 the Google Ads account 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.

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.!5004Q02pUacp:ref"

Thanks,
 

Google Ads API Team