RE: encoding ">" in query

[Google Ads API Forum Advisor]

Hi,

Thanks for reaching out to Google Ads API Forum.

With regards to your concern, I believe that the operator should be ‘>=’ instead of ‘=>’. For better construction of the request body, I would recommend using the query builder to validate your requests. You may use the ad_group query builder via this link (https://developers.google.com/google-ads/api/fields/v14/query_validator).

However, if the error persists after trying the suggested solution, then please note that in Google Ads API perspective we need the complete logs to be able to further investigate. With that being said, can you provide the complete request and response logs with request ID generated as shown in the respective?

Moreover, logging can be enabled by navigating to the Client libraries > Your client library (ex. Java) > Logging documentation, which you can access from the link below. For REST interface requests, you can enable logging via the curl command by using the -i flag. This will cause the tool to include the HTTP response headers in the output.

You may then send the requested information via the Reply privately to the author option. If this option is not available, you may send the details directly to our googleadsa...@google.com alias instead.

Links included in this email:

• Google Ads API - https://developers.google.com/google-ads/api/docs/start 
• Request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
• Response -  https://developers.google.com/google-ads/api/docs/concepts/field-service#response
• Request ID - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id

 

This message is in relation to case "ref:_00D1U1174p._5004Q2n6i1b:ref"

Thanks,
 

Google Ads API Team