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

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

On Thursday, February 25, 2016 at 8:03:45 AM UTC-5, Chirag wrote:

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,

On Wednesday, 10 February 2016 01:33:17 UTC+5:30, Nadine Sundquist (AdWords API Team) wrote:

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

On Tuesday, February 9, 2016 at 11:32:26 AM UTC-5, serkan remzi kucukbay wrote:

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.
On Tuesday, 9 February 2016 17:50:45 UTC+2, Yin Niu wrote:

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. 

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscribe@googlegroups.com
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 "AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/96eb7a1d-effb-4ef9-ae58-a1493e8d0213%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.