Questions about the Google Ads Query Language v6

230 views
Skip to first unread message

FW API

unread,
Feb 17, 2021, 8:55:55 AM2/17/21
to AdWords API and Google Ads API Forum
Hello,
I have some question about the language specification.

1. Is there a maximum length to queries?

2. Are there limits on certain clauses within queries? For example the old Adword API produced TOO_MANY_PREDICATES errors. Are those still a think? If so, what are the limits?

3. How exactly does the LIKE operator work?

Thank you.

Google Ads API Forum Advisor Prod

unread,
Feb 17, 2021, 9:53:08 PM2/17/21
to api.fw...@gmail.com, adwor...@googlegroups.com
Hi,

Thank you for your questions.

Allow me to reach out to the rest of our team and we'll reach back to you with information that can be helpful.

Best regards,

Google Logo
Peter Laurence Napa Oliquino
Google Ads API Team
 


ref:_00D1U1174p._5004Q2CRwMV:ref

Google Ads API Forum Advisor Prod

unread,
Feb 18, 2021, 2:50:37 PM2/18/21
to api.fw...@gmail.com, adwor...@googlegroups.com
Hello - 

Thanks for your questions! I'll answer them inline:
  1. We do not specify a maximum length for queries, however they are limited by the maximum message length configured for gRPC. I believe that in our client libraries this limit is set to approximately 64MB.
  2. There are no limits to predicates in GAQL queries.
  3. The LIKE operator behaves almost identically to the SQL version, the main difference is it's case-insensitive
Hope this helps!

Best,
Ben Karl, Google Ads API Team

ref:_00D1U1174p._5004Q2CRwMV:ref

FW API

unread,
Nov 8, 2021, 3:08:33 AM11/8/21
to AdWords API and Google Ads API Forum
The answer to question is apparently wrong. In case of more than 20k predicate values the API produces FILTER_HAS_TOO_MANY_VALUES.

Google Ads API Forum Advisor

unread,
Nov 12, 2021, 10:24:18 AM11/12/21
to api.fw...@gmail.com, adwor...@googlegroups.com
Hello - 

Indeed it looks like I was mistaken, thanks for clarifying this and linking to our documentation!

Best,
Ben, Google Ads API Team

ref:_00D1U1174p._5004Q2CRwMV:ref
Reply all
Reply to author
Forward
0 new messages