Hello,

Thank you for your support, after collecting all the request and response 
data I realized that the missing responsive_display_ad was due a required 
long headline property that I forgot to add.

IMHO, event though I understand that from the GADS API point of view the 
object is missing because it is unable to create it with the provided data, 
the message the user does receive it is not very accurate to what's the 
real issue, which is a missing required parameter.

Thanks for your time and help!
El lunes, 27 de marzo de 2023 a las 18:18:22 UTC+2, Google Ads API Forum 
Advisor escribió:

> Hello Carlos,
>
> Thank you for responding back to us.
>
> It appears that you are encountering an error when trying to add 
> responsive display ads to your campaign. However, the shared snippet would 
> not suffice for us to determine the exact cause of the issue. Would you be 
> able to share to us the *complete* *request* 
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
>  and *response* 
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
>  logs 
> with *request ID* 
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>
>  and *request header* 
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers>
>  generated 
> on your end? This is so we can provide precise guidance to the issue at 
> hand.
>
> Note that these logs can be requested or provided to the developer 
> handling the Google Ads API transactions when logging of the API requests 
> has been enabled. You may check *here* 
> <https://developers.google.com/google-ads/api/docs/best-practices/logging#client_library_logging>
>  and 
> click your client library for the specific guideline to enable it.
>
> 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 send this privately via "*Reply to Author*" option. If that 
> option is not available to you, you may directly send it to this alias 
> googleadsa...@google.com.
>
> Regards,
> [image: Google Logo] Google Ads API Team 
>
> ref:_00D1U1174p._5004Q2VOtrw:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/da7a77d4-85a2-401f-8b64-ead7bd20abadn%40googlegroups.com.
  • Re... 'Carlos Arnau' via Google Ads API and AdWords API Forum
    • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
      • ... 'Carlos Arnau' via Google Ads API and AdWords API Forum
        • ... 'Carlos Arnau' via Google Ads API and AdWords API Forum
          • ... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum

Reply via email to