Starting the week of March 28, 2022, the Google Ads API will no longer throw an
AssetError.CANNOT_MODIFY_ASSET_NAMEin versions v7, v8 and v9 when uploading an asset with duplicate content but a different
Asset.name. Instead, the Google Ads API will ignore the new name and return the resource name of the existing asset.
This change affects the following asset types.
When creating a new asset using
AssetService.MutateAssets, the Google Ads API detects if the uploaded asset has the same content as an existing asset but a different name and raises an
AssetError.CANNOT_MODIFY_ASSET_NAMEin versions v7, v8 and v9. We observed that it was not easy for users to troubleshoot this error, so starting with version v10, the Google Ads API ignores the new name and returns the resource name of the existing asset if an asset with duplicate content is detected. To keep the API experience consistent, we are making the same changes to versions v7, v8 and v9 of Google Ads API.
What should you do?
Once this change goes live, the
AssetError.CANNOT_MODIFY_ASSET_NAMEerror won’t be thrown when uploading an asset with duplicate content and a different name. If your application handles this error, please review and make changes to match the new API behavior.
If you have any questions or need additional help, contact us using any of the following support options:
- Email: [email protected]
- Support forum: https://groups.google.com/forum/#!forum/adwords-api