Image Ads HTML5_AD_ZIP MEDIA_BUNDLE_NOT_ALLOWED

[FW API]

Hello,

I'm trying to create ImageAds. So far I successfully  created ImageAds with GIF data. Unfortunately, doing the same with HTML5 zips results in

error_code {
    media_upload_error: MEDIA_BUNDLE_NOT_ALLOWED
  }
  message: "The uploaded media bundle format is not allowed."

I checked the .zip via https://h5validator.appspot.com/adwords/asset and was able to upload it via the Ads Editor - so the file itself seems valid.

I'm currently using v14.

I tried to upload the ad in test accounts and production accounts, the latter already containing running HTML5 ads. Instead of normal HTML5 I also tried using AMP HTML Neither worked.

Do you have any insights, why I can't create those ImageAds?

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team.

I understand that you are encountering MEDIA_BUNDLE_NOT_ALLOWED error while trying to create Image Ads. This error states that uploaded media bundle format is not allowed. To analyse the issue further please provide us with complete API request
and response logs with request-id and request header generated at your end.

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.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qBxtm:ref"

Thanks,
 

Google Ads API Team

[Google Ads API Forum Advisor]

Hi,

Thank you for contacting the Google Ads API support team. Please ignore my previous mail.

I understand that you are encountering MEDIA_BUNDLE_NOT_ALLOWED error while trying to create Image Ads. This error states that uploaded media bundle format is not allowed. To analyse the issue further please provide us with complete API request
and response logs with request-id and request header generated at your end.

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.