CustomerSyncService (v201509) Bug, ? Service not returning added or deleted adExtensions?

118 views
Skip to first unread message

serkan remzi kucukbay

unread,
Feb 9, 2016, 3:01:15 PM2/9/16
to AdWords API Forum
Hi All,

The CustomerSyncService doesn't seem to be including addedAdExtensions or deletedAdExtensions data.
I have performed several update delete operations via CampaignExtensionSettingServiceInterface, also several same operation were performed from adwords web interface.But CustomerSyncService does not show any of these changes.
CustomerSyncService list these changes as campaign feed changes and service returns only feedId.

is this  a bug? Can someone take a look?

Thanks in advance for any help!

Serkan Kucukbay

Yin Niu

unread,
Feb 9, 2016, 3:50:45 PM2/9/16
to AdWords API Forum
Hi Serkan, 

Could you send SOAP request and response logs for the AdExtension operations and the query for CustomerSyncService? Please click Reply privately to author in the forum when including your client CustomerID.

Thanks,
Yin, AdWords API Team. 

serkan remzi kucukbay

unread,
Feb 9, 2016, 4:32:26 PM2/9/16
to AdWords API Forum

Hi Yin, 

I sent requested SOAP logs as private.

I also want to post related logs here to help who read this topic,  all private fields were deleted in logs.

Thanks.

Serkan.
req-response for campaignExtension

Nadine Sundquist (AdWords API Team)

unread,
Feb 9, 2016, 8:03:17 PM2/9/16
to AdWords API Forum
Hello Serkan,

It was very thoughtful of you to add logs to help the rest of the community in the future. Yin asked me to take a look to see if I initially saw a reason why the ad extension is missing from CampaignChangeData. On the AdWords back-end, extension settings are just feeds that have a wrapper to make them easier to use. So, you'll see that the feedId that you got back in your initial request is the same as the feedId that you got back in CustomerSyncService. What you got back is the expected response. 

As for CampaignChangeData.addedAdExtensions and CampaignChangeData.removedAdExtensions, they refer to a legacy concept that no longer exists. It's a leftover for an old service that no longer exists. Thanks for catching that! I've filed a bug to get that removed as to not confuse any other people. I have to admit I was a bit confused myself and had to do a bit of digging to find out what it was.

Cheers,
Nadine, AdWords API Team

serkan remzi kucukbay

unread,
Feb 10, 2016, 8:21:53 AM2/10/16
to AdWords API Forum
Hi Nadine,

Thank you very much for your quick respond and collaboration.

Serkan Kucukbay

Chirag

unread,
Feb 25, 2016, 1:03:45 PM2/25/16
to AdWords API Forum
Hello Nadine,

I have account for which i have changed/ created feed item but still not received response as you have mentioned above which is under changedFeeds.

Your input will be helpful.

I have also given my SOAP request privately.

Thanks,

Nadine Sundquist (AdWords API Team)

unread,
Feb 25, 2016, 2:59:45 PM2/25/16
to AdWords API Forum
Greetings!

Thanks for providing the additional information privately. It was really helpful. You probably noticed that the CustomerSyncSelector has a request for either campaignIds or feedIds. In this case, you'll need to pass in feedIds because it's the back-end feeds that were affected rather than the campaign. In order to retrieve the feeds, call the FeedService and retrieve the Id for each feed. Then, call the CustomerSyncService with those feedIds.

You'll need to change one other thing as well. By default, you're getting back the Pacific time zone since you didn't specific a timezone. You'll want to explicitly specify a timezone at the end of each of your date/times from this timezone list. For example, a min date for CustomerSyncService could be specified 20160218 080000 America/Chicago.

Cheers,
Nadine, AdWords API Team

Chirag

unread,
Feb 29, 2016, 5:38:24 AM2/29/16
to AdWords API Forum
Hello Nadine,

Thanks for clarification. Will look at same and let you know, if will not able to get same.

Thanks,

cv

unread,
Mar 30, 2017, 4:28:50 AM3/30/17
to AdWords API Forum
Hello Nadine,

It's been long since I can test this.

But I can see that feedChange Status as FIELDS_UNCHANGED but changedFeedItems as some id.

So, should I consider same as a changes made in the account?

Or any help to consider that actual changes Done!

Thanks,


Google\AdsApi\AdWords\v201702\ch\CustomerChangeData Object
(
    [changedCampaigns:protected] => 
    [changedFeeds:protected] => Array
        (
            [0] => Google\AdsApi\AdWords\v201702\ch\FeedChangeData Object
                (
                    [feedId:protected] => 238346
                    [feedChangeStatus:protected] => FIELDS_UNCHANGED
                    [changedFeedItems:protected] => Array
                        (
                            [0] => 1209xxx2338
                        )

                    [removedFeedItems:protected] => 
                )

Nadine Sundquist (AdWords API Team)

unread,
Mar 30, 2017, 2:12:23 PM3/30/17
to AdWords API Forum
Hi,

Yes, you should consider that a change in your account. In the documentation for CustomerChangeData, it mentions under FIELDS_UNCHANGED:

The fields of this entity have not changed, but there may still be changes to its children.

The FIELDS_UNCHANGED means that the fields of the Feed are unchanged, but the child objects such as the FeedItem could have changed, which is why there are those other arrays to contain the FeedItems.

Take care,
Nadine, AdWords API Team

cv

unread,
Jun 26, 2017, 12:12:10 PM6/26/17
to AdWords API Forum
Hello Nadine,

After our discussion I was getting all the changes history rights until this week.

One of my customerId has added new Adgroups and Ads and keywords within it, but from customerSyncService I was not getting whole data.

Is anything changed recently? Or how could I retrive same.


Thanks,

Nadine Sundquist (AdWords API Team)

unread,
Jun 26, 2017, 8:39:13 PM6/26/17
to AdWords API Forum
Hello,

It's nice to hear from you again! I hope you're doing well. I'm sorry to hear that things aren't working perfectly for you. Could you please start a new thread because this looks like it could be a new issue?

Thanks,
Nadine, AdWords API Team
Reply all
Reply to author
Forward
0 new messages