CustomerSyncService does not return changedFeeds in CampaignChangeData object

[Tomas Rimkus]

* When getting campaign changes with CustomerSyncService, CustomerChangeData->CampaignChangeData->changedFeeds field is never set even there were changes to the feeds. However, I can get those feed changes by setting feedIds in the Selector object and checking for changes in CustomerChangeData->FeedChangeData.

* If I set both campaignIds and feedIds in CustomerSyncSelector object, I always get an empty response. Why can't I get both campaign and feed changes at once? Why do I have to do two requests?

[Tomas Rimkus]

Also, can you tell me why are you using non-standard timezone abbreviation in lastChangeTimestamp (PST8PDT) which is not supported by standard date parsing utils?

[Josh Radcliff (AdWords API Team)]

Hi,

Could you send your account ID (xxx-xxx-xxxx) and the XML request you are sending with both feed IDs and campaign IDs only to me by clicking Reply to Author on this message? I don't see anything in the service handler that would cause an empty response if both types of IDs are specified, so having an example would be helpful.

Regarding PST8PDT, that is a valid timezone in the tz database (e.g., see here). Many libraries such as Joda Time recognize this time zone identifier.

Thanks,

Josh, AdWords API Team

[Tomas Rimkus]

Ok, another thing. Can you please confirm it or deny? changedCampaigns->changedFeeds will indicate changes to feed items only if feed items are associated with some campaign using feedItem->campaignTargeting association.

Or maybe changedCampaigns->changedFeeds only shows changes to feed fields and changes to feed items are disregarded? Can you explain how it works and why I get changes under changedFeeds->changedFeedItems but changedCampaigns->changedFeeds reports that there were no changes when same date interval is used and feeds are associated with campaign using CampaignFeedService?

[Josh Radcliff (AdWords API Team)]

Hi,

The CampaignChangeData.changedFeeds collection does not reflect changes to attributes of FeedItems. Instead, it reflects changes to the association between a Campaign and a Feed -- that's why changedFeeds is a collection of Feed IDs instead of a collection of FeedItem IDs. This association can change due to a change in CampaignFeed objects or a change in FeedItem.campaignTargeting.

For changes to individual FeedItems, you should look at the CustomerChangeData.changedFeeds returned by the sync service.

Thanks,

Josh, AdWords API Team

[Tomas Rimkus]

So, if I create a new Feed and associate it with a Campaign using CampaignFeedService, the ID of the new Feed should show up under changedCampaigns->changedFeeds when checking for campaign changes? Is that correct?

[Josh Radcliff (AdWords API Team)]

Hi,

Yes, that's correct.

Thanks,

Josh, AdWords API Team

[Tomas Rimkus]

On Friday, February 6, 2015 at 3:22:17 PM UTC+1, Tomas Rimkus wrote:

* If I set both campaignIds and feedIds in CustomerSyncSelector object, I always get an empty response. Why can't I get both campaign and feed changes at once? Why do I have to do two requests?

Any update on this issue?

[Josh Radcliff (AdWords API Team)]

Hi,

I just reached out to the engineering team for an update. I'll post back here as soon as I hear from them.

Thanks,

Josh, AdWords API Team

[Chirag]

Hello Josh,

Any update on this.

Actually i am also facing same issue, the feeds are changed but it is not reflecting as changedfeeds for customerSyncservice.

Thanks,

[Josh Radcliff (AdWords API Team)]

Hi,

Still no update, unfortunately. Since fixing this would change the behavior of CustomerSyncService, I would only expect this to be addressed in a new version of the AdWords API and announced on our blog. You can subscribe to updates to the blog by joining the AdWords API Announcements group.

In the meantime, if I get any additional information I'll be sure to post it to this discussion.

Thanks,

Josh, AdWords API Team

[Josh Radcliff (AdWords API Team)]

Hi,

Good news: this issue was recently fixed. If you find you are still running into problems when specifying both campaign and feed IDs, please let me know.

Thanks,

Josh, AdWords API Team

[Tomas Rimkus]

And it only took ~1 year to fix it...