AssetGroup create failure on PMax retail campaign

[Joshua Newman]

Hello there,

Starting yesterday (5/25/23) we started noticing API errors when attempting to create an AssetGroup for our PMax retail campaigns. The Merchant Center account is linked to the Google Ads Account and the respective MerchantId has been applied to the PMax Retail campaign. According to this documentation (https://developers.google.com/google-ads/api/docs/performance-max/retail), which has always worked for us, by linking to the Merchant Center, assets can be automatically generated for the campaign.

Has something changed for PMax retail campaigns? 

{ "StatusCode": 3, "Details": "Request contains an invalid argument.", "RequestId": "QfZIKvJKHumWkX-SWKBoWQ", "Failure": { "errors": [ { "errorCode": { "assetGroupError": "NOT_ENOUGH_HEADLINE_ASSET" }, "message": "Headline asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: headline" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": "NOT_ENOUGH_LONG_HEADLINE_ASSET" }, "message": "Long headline asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: long headline" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": "NOT_ENOUGH_DESCRIPTION_ASSET" }, "message": "Description headline asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: description" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": "NOT_ENOUGH_BUSINESS_NAME_ASSET" }, "message": "Business name asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: business name" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": "NOT_ENOUGH_MARKETING_IMAGE_ASSET" }, "message": "Marketing image asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: marketing image" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": "NOT_ENOUGH_SQUARE_MARKETING_IMAGE_ASSET" }, "message": "Square marketing image asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: square marketing image" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": "NOT_ENOUGH_LOGO_ASSET" }, "message": "Logo asset for a valid asset group is not enough.", "trigger": { "stringValue": "Asset type: logo" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } }, { "errorCode": { "assetGroupError": 13 }, "message": "Short description asset for a valid asset group is required.", "trigger": { "stringValue": "Asset type: description" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 } ] } } ], "requestId": "QfZIKvJKHumWkX-SWKBoWQ" } }

[san...@knorex.com]

 I have the same issue. It has worked well until 25/5.

[Google Ads API Forum Advisor]

Hello,

Thanks for reaching out to the Google Ads API Forum.

Upon checking the provided response logs with our team, I can see that you’ve encountered following errors on your request:

• NOT_ENOUGH_HEADLINE_ASSET
• NOT_ENOUGH_LONG_HEADLINE_ASSET
• NOT_ENOUGH_DESCRIPTION_ASSET
• NOT_ENOUGH_BUSINESS_NAME_ASSET
• NOT_ENOUGH_MARKETING_IMAGE_ASSET
• NOT_ENOUGH_SQUARE_MARKETING_IMAGE_ASSET
• NOT_ENOUGH_LOGO_ASSET

For the above errors, you may refer to this guide on why it's being thrown. Also, you may see how to link assets to asset groups using the interactive guide for Performance Max campaigns here: https://developers.google.com/google-ads/api/interactive-guides/performance-max?url=%2Fpmax%2FfullExample%2FassetGroupAssets

If you are using client library, then you may use the sample working example to create retail PMAX here: https://developers.google.com/google-ads/api/samples/add-performance-max-retail-campaign

If error persists after following the above guides, then our team requires the complete request and response logs so that we can check the sequence on how you have added operations in your API request. You may privately provide complete request, response logs with request ID and request header generated so that we can check better.

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

Thanks,
 

Google Ads API Team

[Joshua Newman]

Thank you for the response and information. I understand what the errors mean, but what I don't understand is why Assets are now required for PMax retail campaigns now. Was there an announcement about a change in requirements for PMax retail? According this documentation (https://developers.google.com/google-ads/api/docs/performance-max/assets#:~:text=As%20a%20best%20practice%2C%20we,maximize%20reach%20across%20all%20inventory.&text=30%20characters%20max%3B%20include%20at,with%2015%20characters%20or%20less.&text=90%20characters%20max%3B%20include%20at,with%2060%20characters%20or%20less.) , Assets are not required for PMax retail because by linking the Google Merchant Account to the PMax campaign assets will be automatically generated. This has worked since we migrated from Smart Shopping Campaigns to PMax Retail campaigns back in September of 2022. Can someone elaborate on this for me?

[Google Ads API Forum Advisor]

Hi,

It appears we have already addressed your concern on another thread with the subject "[Urgent] Cannot create new Asset group". For better tracking of your issue, it would be best to continue the conversation on the said thread. 

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

Thanks,
 

Google Ads API Team

[Sanchez, Ivan]

Dear all,

 

After checking the ID, we note that it’s still the right ID we are entering in the file configuration. I’m sending you the screenshots displaying the place from where I’m getting the information and where I’m placing it. I would like to know if, provided that the ID is right, other wrong configuration may be causing this error.

 

 

.

 

Thanks in advance.

[Sanchez, Ivan]

[Sanchez, Ivan]

Hi,

 

I’m still with the error:

Thanks in advance.

 

 

De: Google Ads API Direct Support <googleadsa...@google.com>
Enviada em: quinta-feira, 1 de junho de 2023 05:01
Para: Sanchez, Ivan <ivan.s...@br.experian.com>
Cc: adwor...@googlegroups.com
Assunto: [EXTERNAL] RE: python script failuinvalid customer id

 

External email: Do not click the links. Verify legitimacy before taking action.

Hello Ivan,

Thank you for the additional information.

I can see that you’ve encountered the INVALID_CUSTOMER_ID error. Can you check if the Customer ID you used in your request is valid, and you have also excluded hyphens? You may retry your API request with the correct customer ID and without hyphens (-). For more information regarding customer ID, you can refer to this guide: https://developers.google.com/google-ads/api/docs/first-call/overview#config. However, if the issue still persists even after following the guide, can you provide us with the complete request and response logs with request ID and request header generated on your end when encountering the said error? This is so we could investigate further and provide appropriate guidance.

For more information regarding Python client library, logging can be enabled by following this guide: https://developers.google.com/google-ads/api/docs/client-libs/python/logging.

Reference links included in this email:
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
request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers
 
This message is in relation to case "ref:_00D1U1174p._5004Q2ltHJk:ref"

[Google Ads API Forum Advisor]

Hi,

Thanks for getting back to us.

Upon checking, this has already been resolved on our end. Can you please try once again and let us know how it goes on your end?

[Sanchez, Ivan]

We still have an error, can you check it please