Hi Amit,
Thank you for reaching out to the Google Ads API support team.
Please find the following answers to your questions:
The FIELD_TYPE_INCOMPATIBLE_WITH_CAMPAIGN_TYPE error occurs when the asset
field types (MARKETING_IMAGE and SQUARE_MARKETING_IMAGE) doesn't align with the
search campaign type.
It's not possible to link asset fields, such as MARKETING_IMAGE or
SQUARE_MARKETING_IMAGE, directly to Search campaigns. These image assets are
only supported for App ads, App engagement ads, Local ads, and Responsive
Display ads. For Search campaigns, only text assets are supported, which can be
used for Responsive Search Ads.
For more detailed information on which asset types are linked to specific ad
types, refer to this document.
1) Is it possible to link image assets to a Search campaign at the campaign
level via the API?
Yes, you can link image assets to search campaigns. This can be achieved with
AssetFieldType called AD_IMAGE
2) If yes, what is the correct approach to do so, and which AssetFieldType
values are supported?
You need to use the asset field type called AD_IMAGE.
3) If this is not supported by the API but allowed via UI, could you explain
the limitation or recommend any alternative?
First you need to create image asset using the AssetService , try the below
sample request :
{
"operations": [
{
"create": {
"imageAsset": {
"data": "",
"fullSize": {
"heightPixels": 1200,
"url": "https://gaagl.page.link/Eit5";,
"widthPixels": 628
},
"mimeType": "IMAGE_PNG"
},
"name": "Enter name of the asset"
}
}
]
}
Once the image asset is created, you can link this asset to search campaigns
using the CampaignAssetService. To do this, follow the below sample request :
{
"operations": [
{
"create": {
"asset": "customers/{customer_id}/assets/{newly_created_asset_id}",
"campaign": "customers/{customer_id}/campaigns/{search_campaign_id}",
"fieldType": "AD_IMAGE"
}
}
]
}
If you face any issues, share the latest complete API logs (request and
response 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.
Thanks,
Google Ads API Team
Feedback
How was our support today?
[2025-07-24 12:05:27Z GMT] This message is in relation to case
"ref:!00D1U01174p.!500Ht01swd0Y:ref" (ADR-00320031)
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/adwords-api/wyTd-000000000000000000000000000000000000000000000SZWK9300eiEjwkXQSJCoGkHDWbvz8g%40sfdc.net.
