Callouts not returned using CampaignExtensionSettingService (feed is named "AdWords Express Callouts feed")

[j...@stackstorage.co]

Hi,

I am having an issue where Callout extensions are not returned from the CampaignExtensionSettingService. Every other type of extension is returned by the API. I think it has something to do with the state of this particular Feed. In the "Business data" view, this feed has a different naming convention from the other feeds. It's called "AdWords Express Callouts feed" instead of using the convention "Main callout feed". I think somebody must have created this feed in our Account using AdWords Express. I thought perhaps that I needed to migrate it per Extension Setting Services page, but this seems like a different case because the API indicates that the origin is ADWORDS and not USER. Therefore, I think it is the System Callouts feed, but it's in a special state where it's items are not returned by the API. I could try to force migrate it anyway, but I am not sure if this will work and don't want to break anything. Can somebody please advise on best course of action Thanks.

-Jon

[Peter Oliquino]

Hi Jon,

AdWords Express information is currently not 100% supported via the AdWords API. You may refer to this recent blog post on how AdWords Express campaigns can be retrieved via the AdWords API. However, as for the AdWords Express campaign's extension settings, I'm afraid there is currently no way at the moment on how to filter those out using the method discussed in the blog.

Thanks and regards,

Peter

AdWords API Team

[j...@stackstorage.co]

Hi Peter,

I think you're misunderstanding the question. We don't have any AdWords Express campaigns. I actually don't even know exactly what AdWords Express is but I assume our agency or a contract might have used this over a year ago. Our callout extension feed is permanently in a broken state where we can't retrieve the extensions in it using CampaignExtensionSettingService. How do we fix it? Do I need to delete all our callouts and delete the feed and start over? I am worry that may make the situation worse.

-Jon

[Peter Oliquino]

Hi Jon,

My apologies if I misunderstood. Moving forward, in order for me to better investigate and identify the cause why you are unable to retrieve the extensions, could you provide your clientCustomerId, the generated SOAP request and response when you attempted to retrieve the said extensions, and the AdWords UI screenshot containing them? You may reply to me privately via the Reply privately to author option.

[Nadine Sundquist (AdWords API Team)]

Greetings Jon,

Thanks for providing us with the additional information. It was really helpful in double-checking a few things. I'm posting out on the forum rather than directly replying just so both of us can help the general community in case anyone else bumps into this. Feeds are always tricky. When something is tagged with origin ADWORDS rather than USER, then it is as you noticed, a system feed. When that's the case, you usually can't make changes to it; there's a bit more about that here. I appreciate that you're being a good citizen and attempting to move things over, but there are a few feeds that our system auto-generates, and the one you discovered happened to be one of them. You can just leave it alone; no migration is necessary. I would be surprised if it would even let you mutate it. If you find that it's causing you issues, then please get back to us, and we'll see what we can do to fix up that account for you.

Cheers,

Nadine, AdWords API Team

[j...@stackstorage.co]

Hi Nadine,

Thank you very much for investigating. Unfortunately, it is causing us an actual issue. That was the reason I originally posted. Because this particular feed is in this unusual state, we can't use the CampaignExtensionSettingService API to read and update our Callout Extensions. It's as if they do not exist via the API. 

This is related to https://developers.google.com/adwords/api/docs/reference/v201710/CampaignExtensionSettingService. We are able to view and update other campaign extensions like Sitelinks and Structured Snippets, but we cannot view the Callouts.

The document regarding migration (https://developers.google.com/adwords/api/docs/guides/extension-settings#migrate_ad_extensions_to_extension_setting_services) discusses migrating User feeds. It does not discuss migrating System Feeds. For this reason, I was reluctant to attempt to migrate it because I don't want to make anything worse.

Best,

Jon

[anal...@pushgroup.co.uk]

Hi,

Just trying to understand the solution provided by API team and its not making sense to me.

Can you clarify if we can retrieve the Extensions added through AdWords Express Feed or not? Attached screenshot for the same. (Currently they are not coming through when I use or "CampaignExtensionSettingService" or "CustomerExtensionSettingService".

Thanks,

[Bharani Cherukuri (AdWords API Team)]

Hello, 

I'm Nadine's colleague assisting you on her behalf. The AdWords Express Campaigns are included only in the UI Reports. These Campaigns can only appear in the Campaign Performance Report. Please refer to this blog post for more information. It is currently not possible to use API services to pull the feed information for Express feeds. Please keep an eye on our blog for any updates or announcements related to this feature. 

Thanks,
Bharani, AdWords API Team