Re: Weird OAuth2 failure to refresh access token

2014-01-07 Thread Akil Burgess
Hi Anash,

Thanks for your response and the suggestion. We are already reusing 
OAuthProvider instances do reduce refresh frequency. We had experienced 
rate limit errors from the OAuth2 servers before (see http://goo.gl/wdDEKU) 
and the error page was different - is it possible to receive different 
error pages for rate limit errors?

I've opened Issue #7 (
https://github.com/googleads/googleads-adwords-dotnet-lib/issues/7) on the 
AdWords API .NET library to make the code path more robust.

Cheers,
Akil 

On Monday, January 6, 2014 11:00:53 PM UTC, Anash P. Oommen (AdWords API 
Team) wrote:

 Hi Akil,

 My initial guess is that the page is a rate limit error from the OAuth2 
 servers (too many instances trying to refresh access token simultaneously). 
 It's a matter of chance that a particular server failed, and the error 
 would go away if the code were retried after a minute or so.

 You could reuse the OAuthProvider instance between multiple AdWordsUser 
 instances to reduce its frequency, but could you also open an issue against 
 the AdWords API .NET library to make this code path more robust?

 Cheers,
 Anash P. Oommen,
 AdWords API Advisor.

 On Monday, January 6, 2014 7:09:32 AM UTC-5, Akil Burgess wrote:

 Hi All,

 We've noticed a weird authentication error that was occurring on one of 
 our application servers over the weekend. All of our 
 *MutateJobService.mutate* API calls were failing with the error below 
 across multiple accounts. The weird thing is all other API calls were 
 unaffected and the MutateJobService.mutate API calls succeeded across our 
 other application servers (which are all using the same OAuth2 
 credentials). After restarting the failing application instance the errors 
 disappeared.

 Is there a reason why the refresh would only fail for one API call and 
 not for others? Similarly, why would the refresh only fail on one 
 application instance and not others?

 Thanks!
 Akil Burgess


 An unhandled exception occurred.
 [Google.Api.Ads.Common.Lib.AdsOAuthException]: Failed to refresh access 
 token.
 lt;!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN 
 http://www.w3.org/TR/html4/loose.dtdgt;lt;htmlgt;lt;headgt;lt;titlegt;Google
  
 Accountslt;/titlegt;lt;meta http-equiv=content-type 
 content=text/html; charset=utf-8gt;lt;meta http-equiv=X-UA-Compatible 
 content=IE=edge /gt;lt;meta name=viewport 
 content=width=device-width, initial-scale=1, minimum-scale=1, 
 maximum-scale=1, user-scalable=0 /gt;lt;link rel='stylesheet' 
 type='text/css' href='
 https://ssl.gstatic.com/accounts/o/1893590695-error_page_css_ltr.css'gt;
 lt;script type=text/javascript src=
 https://ssl.gstatic.com/accounts/o/635117462-common_lib.js
 gt;lt;/scriptgt;
 lt;stylegt;@media screen and (max-width:500px) {#robot {background: 
 none; min-height: 0; min-width: 0; padding: 0;}#stack_trace {display: 
 none;}}
 #oauth2_request_info_header {background-image: url(
 https://ssl.gstatic.com/accounts/o/blank.gif;);}lt;/stylegt;lt;/headgt;lt;body
  
 gt;lt;div id=robotgt;lt;/divgt;lt;a href=//www.google.com/ 
 id=googlelogogt;lt;img src=//www.google.com/images/logo_sm.gif 
 alt=Googlegt;lt;/agt;lt;p class=largegt;lt;bgt;403.lt;/bgt; 
 lt;insgt;That's an error.lt;/insgt;lt;/pgt;lt;p class=largegt;You 
 are not authorized to perform this request.  lt;insgt;That's all we 
 know.lt;/insgt;lt;/pgt;lt;/bodygt;lt;/htmlgt;

 Stack Trace: 
at 
 Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
at Google.Api.Ads.Common.Lib.OAuth2ProviderBase.GetAuthHeader()
at Google.Api.Ads.AdWords.Lib.AdWordsSoapClient.InitForCall(String 
 methodName, Object[] parameters)
at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String 
 methodName, Object[] parameters)
at Google.Api.Ads.AdWords.v201306.MutateJobService.mutate(Operation[] 
 operations, BulkMutateJobPolicy policy)
...



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Weird OAuth2 failure to refresh access token

2014-01-06 Thread Akil Burgess
Hi All,

We've noticed a weird authentication error that was occurring on one of our 
application servers over the weekend. All of our *MutateJobService.mutate* API 
calls were failing with the error below across multiple accounts. The weird 
thing is all other API calls were unaffected and the 
MutateJobService.mutate API calls succeeded across our other application 
servers (which are all using the same OAuth2 credentials). After restarting 
the failing application instance the errors disappeared.

Is there a reason why the refresh would only fail for one API call and not 
for others? Similarly, why would the refresh only fail on one application 
instance and not others?

Thanks!
Akil Burgess


An unhandled exception occurred.
[Google.Api.Ads.Common.Lib.AdsOAuthException]: Failed to refresh access 
token.
lt;!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN 
http://www.w3.org/TR/html4/loose.dtdgt;lt;htmlgt;lt;headgt;lt;titlegt;Google
 
Accountslt;/titlegt;lt;meta http-equiv=content-type 
content=text/html; charset=utf-8gt;lt;meta http-equiv=X-UA-Compatible 
content=IE=edge /gt;lt;meta name=viewport 
content=width=device-width, initial-scale=1, minimum-scale=1, 
maximum-scale=1, user-scalable=0 /gt;lt;link rel='stylesheet' 
type='text/css' 
href='https://ssl.gstatic.com/accounts/o/1893590695-error_page_css_ltr.css'gt;
lt;script type=text/javascript 
src=https://ssl.gstatic.com/accounts/o/635117462-common_lib.jsgt;lt;/scriptgt;
lt;stylegt;@media screen and (max-width:500px) {#robot {background: none; 
min-height: 0; min-width: 0; padding: 0;}#stack_trace {display: none;}}
#oauth2_request_info_header {background-image: 
url(https://ssl.gstatic.com/accounts/o/blank.gif;);}lt;/stylegt;lt;/headgt;lt;body
 
gt;lt;div id=robotgt;lt;/divgt;lt;a href=//www.google.com/ 
id=googlelogogt;lt;img src=//www.google.com/images/logo_sm.gif 
alt=Googlegt;lt;/agt;lt;p class=largegt;lt;bgt;403.lt;/bgt; 
lt;insgt;That's an error.lt;/insgt;lt;/pgt;lt;p class=largegt;You 
are not authorized to perform this request.  lt;insgt;That's all we 
know.lt;/insgt;lt;/pgt;lt;/bodygt;lt;/htmlgt;

Stack Trace: 
   at 
Google.Api.Ads.Common.Lib.OAuth2ProviderForApplications.RefreshAccessTokenInOfflineMode()
   at Google.Api.Ads.Common.Lib.OAuth2ProviderBase.GetAuthHeader()
   at Google.Api.Ads.AdWords.Lib.AdWordsSoapClient.InitForCall(String 
methodName, Object[] parameters)
   at Google.Api.Ads.Common.Lib.AdsSoapClient.MakeApiCall(String 
methodName, Object[] parameters)
   at Google.Api.Ads.AdWords.v201306.MutateJobService.mutate(Operation[] 
operations, BulkMutateJobPolicy policy)
   ...

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


CustomerSyncService Bug? FeedChangeData not returned when CampaignIds are specified in the CustomerSyncSelector

2013-10-25 Thread Akil Burgess
Hi All,

I am seeing an issue where the CustomerSyncService only returns 
FeedChangeData changes when the CustomerSyncSelector contains no 
CampaignIds. The attached logs shows two CustomerSyncService get operations 
over the same dateTimeRange. In the first call, only feedIds are specified 
in the CustomerSyncSelector and the response contains FeedChangeData with 
changedFeedItems. In the second call, campaignIds and feedIds are specified 
in the CustomerSyncSelector and the response contains FeedChangeData with 
no changedFeedItems.

Is this expected? This seems like a bug since it would be quite 
inconvenient to have to do separate API calls for the campaign and feed 
changes.

Thanks!
Akil

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


soap_xml.log
Description: Binary data


Re: Using CustomerSyncService for CampaignFeed and AdGroupBidModifier changes

2013-10-11 Thread Akil Burgess
Is there still more work to be done on CustomerSyncService support for 
CampaignFeed changes? As of v201309, CustomerChangeData still does not seem 
to describe when a CampaignFeed's matching function changes (i.e. feed 
items are added or removed to/from the feed items being served for a 
campaign).

Am I missing something or are there plans to add more information about 
CampaignFeed changes in the CustomerSyncService?

Thanks!
Akil

On Wednesday, July 10, 2013 7:10:42 AM UTC+1, Anash P. Oommen (AdWords API 
Team) wrote:

 Hi Akil,

 This is not supported in the current version of the API, but I'll add this 
 as a feature request for future versions of the API.

 Cheers,
 Anash P. Oommen,
 AdWords API Advisor.

 On Monday, July 8, 2013 2:22:02 PM UTC+5:30, Akil Burgess wrote:

 Hi All,

 We currently use the CustomerSyncService to keep our local database 
 up-to-date with the latest changes in our AdWords accounts. Does the 
 CustomerSyncService (or some new service) give detail information about 
 changes to CampaignFeed associations or AdGroupBidModifiers?

 Thanks,
 Akil



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: MutateJobService returns CampaignError.DUPLICATE_CAMPAIGN_NAME errors when Campaigns were actually created successfully

2013-08-19 Thread Akil Burgess
Hi Takeshi,

Thanks for looking into this issue. This has been an intermittent issue 
that we've seen on about three or four occasions in the past few months 
when we have been doing large scale campaign creation via the API.

The history for JobId -8089192796637669145 (see attached) shows that the 
job started processing Thursday August 15, 2013 15:48:28 (i.e. after the 
date you say the campaign was created). Do your logs show the JobId that 
the campaign was created in? Unfortunately we do not enable SOAP logging in 
production so I do not have the requestId for the initial MutateJobService 
call.

Thanks!
Akil

On Monday, August 19, 2013 11:33:12 AM UTC+1, Takeshi Hagikura (AdWords API 
Team) wrote:

 Hi, 

 Also is it still reproducible?
 Our log says the first MutateJobService call was made at August 16, 2013. 
 So it's most likely those campaigns were already there. 

 Best,
 - Takeshi, 

 On Monday, August 19, 2013 7:15:32 PM UTC+9, Takeshi Hagikura (AdWords API 
 Team) wrote:

 Hi,

 When was the first MutateJobService call made?
 Based on our record, the campaign whose name is AU - Concerts - Laura 
 Pausini was created at Thursday, August 15, 2013 3:47:26 PM GMT
 Is there a possibility that those campaigns were already created before 
 the MutateJobService call?

 Best,
 - Takeshi, AdWords API Team

 On Friday, August 16, 2013 7:39:14 PM UTC+9, Akil Burgess wrote:

 Hi All,

 We are seeing an issue where we are creating a set of Campaigns using 
 the MutateJobService and some of the CampaignOperations report 
 CampaignError.DUPLICATE_CAMPAIGN_NAME errors even though they are 
 definitely unique names. The campaigns are still created even though an 
 error is reported.

 I have attached a file with the request logs that show the result of 
 JobId -8089192796637669145 which contains 10 duplicate name errors. The log 
 also shows that a CampaignService.get request for campaigns with those 
 specific names still returns campaigns that have been created.

 Any ideas what is going on here?

 Thanks,
 Akil



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


soap_xml.log
Description: Binary data


MutateJobService returns CampaignError.DUPLICATE_CAMPAIGN_NAME errors when Campaigns were actually created successfully

2013-08-16 Thread Akil Burgess
Hi All,

We are seeing an issue where we are creating a set of Campaigns using the 
MutateJobService and some of the CampaignOperations report 
CampaignError.DUPLICATE_CAMPAIGN_NAME errors even though they are 
definitely unique names. The campaigns are still created even though an 
error is reported.

I have attached a file with the request logs that show the result of 
JobId -8089192796637669145 which contains 10 duplicate name errors. The log 
also shows that a CampaignService.get request for campaigns with those 
specific names still returns campaigns that have been created.

Any ideas what is going on here?

Thanks,
Akil

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


soap_xml.log
Description: Binary data


AdGroupCriterionService Bug? - EntityNotFound.INVALID_ID for CriterionId that exists

2013-07-22 Thread Akil Burgess
Hi All,

We're seeing a reproducable issue where we receive an 
EntityNotFound.INVALID_ID (trigger - CriterionId) error for a mutate 
operation on AdGroupCriterion using a valid AdGroupId and CriterionId 
(Id). The AdGroupCriterionService get call returns the AdGroupCriterion 
object with the same Ids that are being said to be invalid. 

I have attached the soap logs for the mutate operation and the get 
operation below. Is this a bug in the AdGroupCriterionService or is there 
something wrong with our AdGroupCriterionOperation?

Thanks!
Akil Burgess


-BEGIN API CALL-

Request (Mutate)
---


?xml version=1.0 encoding=utf-8?soap:Envelope 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema;!--POST 
/api/adwords/cm/v201306/AdGroupCriterionService
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client 
Protocol 4.0.30319.18051)
VsDebuggerCausalityData: 
uIDPowA6lARsOPdGukKutxnlLlgANiaXQS2+v0qF1bOWBKYRAyjTf3Fc57dJitdesMIpq6IACQAA
Content-Type: text/xml; charset=utf-8
SOAPAction: 
Host: adwords.google.com
Content-Length: 1540
Accept-Encoding: gzip
Connection: Keep-Alive
TimeStamp: Mon, 22 Jul 2013 12:02:27 GMT
--soap:HeaderRequestHeader 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;authToken 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;**/authTokendeveloperToken
 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;**/developerTokenclientCustomerId
 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;9765518125/clientCustomerIduserAgent
 
xmlns=https://adwords.google.com/api/adwords/cm/v201306; 
(AwApi-DotNet/16.1.0, Common-Dotnet/1.8.0, .NET CLR/4.0.30319.18051, 
gzip)/userAgent/RequestHeader/soap:Headersoap:Bodymutate 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;operationsoperatorSET/operatoroperand
 
xsi:type=BiddableAdGroupCriterionadGroupId3790202104/adGroupIdcriterion 
xsi:type=Keywordid37523985304/id/criterionbiddingStrategyConfigurationbids
 
xsi:type=CpcBidbidmicroAmount80/microAmount/bid/bids/biddingStrategyConfiguration/operand/operations/mutate/soap:Body/soap:Envelope

Response (Mutate)



soap:Envelope 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;!--Content-Encoding: 
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Length: 535
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=UTF-8
Date: Mon, 22 Jul 2013 11:01:16 GMT
Expires: Mon, 22 Jul 2013 11:01:16 GMT
Server: GSE
TimeStamp: Mon, 22 Jul 2013 12:02:27 GMT
--soap:HeaderResponseHeader 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;requestId0004e2179870ad280ae50e884419/requestIdserviceNameAdGroupCriterionService/serviceNamemethodNamemutate/methodNameoperations0/operationsresponseTime478/responseTime/ResponseHeader/soap:Headersoap:Bodysoap:Faultfaultcodesoap:Server/faultcodefaultstring[EntityNotFound.INVALID_ID
 
@ operations[0].operand.criterion.id; 
trigger:'CriterionId{id=37523985304}']/faultstringdetailApiExceptionFault 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;message[EntityNotFound.INVALID_ID
 
@ operations[0].operand.criterion.id; 
trigger:'CriterionId{id=37523985304}']/messageApplicationException.TypeApiException/ApplicationException.Typeerrors
 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xsi:type=EntityNotFoundfieldPathoperations[0].operand.criterion.id/fieldPathtriggerCriterionId{id=37523985304}/triggererrorStringEntityNotFound.INVALID_ID/errorStringApiError.TypeEntityNotFound/ApiError.TypereasonINVALID_ID/reason/errors/ApiExceptionFault/detail/soap:Fault/soap:Body/soap:Envelope
-END API CALL---

-BEGIN API CALL-

Request (Get)
---


?xml version=1.0 encoding=utf-8?soap:Envelope 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema;!--POST 
/api/adwords/cm/v201306/AdGroupCriterionService
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client 
Protocol 4.0.30319.18051)
VsDebuggerCausalityData: 
uIDPo3bOCEf8qJROof0bhcA1TDcAT2HD25jDzUGnU2As9HdxCUHJYPMJGZBCiWlffLMJkWEACQAA
Content-Type: text/xml; charset=utf-8
SOAPAction: 
Host: adwords.google.com
Content-Length: 2621
Accept-Encoding: gzip
Connection: Keep-Alive
TimeStamp: Mon, 22 Jul 2013 12:03:30 GMT
--soap:HeaderRequestHeader 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;authToken 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;**/authTokendeveloperToken
 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;**/developerTokenclientCustomerId
 
xmlns=https://adwords.google.com/api/adwords/cm/v201306;9765518125/clientCustomerIduserAgent
 
xmlns=https://adwords.google.com/api/adwords/cm/v201306; 
(AwApi-DotNet/16.1.0

Using CustomerSyncService for CampaignFeed and AdGroupBidModifier changes

2013-07-08 Thread Akil Burgess
Hi All,

We currently use the CustomerSyncService to keep our local database 
up-to-date with the latest changes in our AdWords accounts. Does the 
CustomerSyncService (or some new service) give detail information about 
changes to CampaignFeed associations or AdGroupBidModifiers?

Thanks,
Akil

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: CustomerSyncService Bug? Service not returning added or deleted adExtensions

2013-03-21 Thread Akil Burgess
Hi Takeshi,

Do you have any update on this issue? I am still experiencing issues with 
CampaignAdExtension changes being reflected in the CustomerSyncService 
(v201209).

Thanks,
Akil

On Monday, January 28, 2013 3:29:19 AM UTC, Takeshi Hagikura (AdWords API 
Team) wrote:

 Unfortunately, it's not possible to track the status externally.

 Best,
 - Takeshi

 On Friday, January 25, 2013 7:24:50 PM UTC+9, Akil Burgess wrote:

 Thanks Takeshi. Is there a way for me to track the status of the bug?

 --
 Akil

 On Friday, January 25, 2013 9:07:34 AM UTC, Takeshi Hagikura (AdWords API 
 Team) wrote:

 Thanks for the logs.

 Yes, it should be returned.
 I've escalated it as a bug.

 Best,
 - Takeshi, AdWords API Team

 On Thursday, January 24, 2013 9:48:19 PM UTC+9, Akil Burgess wrote:

 Hi Takeshi,

 Thank you for your response. I have attached the logs for a 
 campaignAdExtension mutate operation and then a subsequent 
 CustomerSyncService get operation to this reply. Please let me know if I 
 can provide anything else that may help.

 Thanks,
 Akil

 On Thursday, January 24, 2013 8:59:35 AM UTC, Takeshi Hagikura (AdWords 
 API Team) wrote:

 Hello Akil,

 Thanks for writing in.
 Do you also have the request/response logs for CampaignAdExtension 
 mutate?

 I'd like to confirm if that should be included in the 
 CustomerSyncService response.

 Best,
 - Takeshi, AdWords API Team

 On Tuesday, January 22, 2013 1:56:32 AM UTC+9, Akil Burgess wrote:

 Hi All,

 The CustomerSyncService doesn't seem to be including 
 addedAdExtensions or deletedAdExtensions data. I've performed several 
 CampaignAdExtension updates (via the API and the AdWords web interface) 
 in 
 our test account and the CustomerSyncService does not show any of these 
 changes. When I perform CampaignAdExtensionService get operations I can 
 see 
 the updated data so it seems like this data should have been processed 
 and 
 reflected in the CustomerChangeData.

 *All* - Is anyone else seeing this behaviour?

 *API Team* - Is this a bug? Can someone take a look?

 I have pasted my request and response logs at the end of this 
 message. As we can see other changes (adgroups) are showing in 
 CustomerChangeData but no adExtensions.

 Thanks in advance for any help!

 Akil


 *Request:*

 ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=
 http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=
 http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
 http://www.w3.org/2001/XMLSchema;!--POST 
 /api/adwords/ch/v201209/CustomerSyncService
 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client 
 Protocol 4.0.30319.18010)
 VsDebuggerCausalityData: 
 uIDPoweSfT+RGipEr2AHcUx8fKcAfOeL1Iv+IUKx5K82Sb8Y4cEEsc5nCVxBn3ybnrh+mf8ACQAA
 Content-Type: text/xml; charset=utf-8
 SOAPAction: 
 Host: adwords.google.com
 Content-Length: 1463
 Accept-Encoding: gzip
 Connection: Keep-Alive
 TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
 --soap:HeaderRequestHeader xmlns=
 https://adwords.google.com/api/adwords/ch/v201209;authToken xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;**/authTokendeveloperToken
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;**/developerTokenclientCustomerId
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;2226963136/clientCustomerIduserAgent
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;** 
 (AwApi-DotNet/15.0.0, Common-Dotnet/1.4.0, .NET CLR/4.0.30319.18010, 
 gzip)/userAgent/RequestHeader/soap:Headersoap:Bodyget xmlns=
 https://adwords.google.com/api/adwords/ch/v201209;selectordateTimeRangemin
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;20130118 
 00 UTC/minmax xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;20130121 164714 
 UTC/max/dateTimeRangecampaignIds110290473/campaignIds/selector/get/soap:Body/soap:Envelope


 *Response:*
 *
 *
 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/
 !--Content-Encoding: 
 X-Content-Type-Options: nosniff
 X-Frame-Options: SAMEORIGIN
 X-XSS-Protection: 1; mode=block
 Content-Length: 455
 Cache-Control: private, max-age=0
 Content-Type: text/xml; charset=UTF-8
 Date: Mon, 21 Jan 2013 16:47:31 GMT
 Expires: Mon, 21 Jan 2013 16:47:31 GMT
 Server: GSE
 TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
 --soap:Headerns2:ResponseHeader xmlns:ns2=
 https://adwords.google.com/api/adwords/ch/v201209; xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;requestId0004d3cf3789ea980ab1540155c5/requestIdserviceNameCustomerSyncService/serviceNamemethodNameget/methodNameoperations0/operationsresponseTime1486/responseTimeunits0/units/ns2:ResponseHeader/soap:Headersoap:Bodyns2:getResponse
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209; xmlns:ns2=
 https://adwords.google.com/api/adwords/ch/v201209;ns2:rvalns2:changedCampaignsns2:campaignId110290473/ns2:campaignIdns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatusns2:changedAdGroupsns2:adGroupId6213230793/ns2:adGroupIdns2

Re: Elevated error rates

2013-03-18 Thread Akil Burgess
I am also using v201209 and all requests to the AdWords API are either 
timing out or failing with an API_UNEXPECTED_INTERNAL_ERROR.

On Monday, March 18, 2013 2:10:09 PM UTC, j.e.frank wrote:

 This morning starting around 9:00 Eastern we are receiving a high number 
 of errors using the AdWords API.  I presume this is a temporary situation 
 and will get resolved, but I wanted to alert the team in case it hadn't 
 been brought to their attention.

 We are using v201209.


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: CustomerSyncService Bug? Service not returning added or deleted adExtensions

2013-01-25 Thread Akil Burgess
Thanks Takeshi. Is there a way for me to track the status of the bug?

--
Akil

On Friday, January 25, 2013 9:07:34 AM UTC, Takeshi Hagikura (AdWords API 
Team) wrote:

 Thanks for the logs.

 Yes, it should be returned.
 I've escalated it as a bug.

 Best,
 - Takeshi, AdWords API Team

 On Thursday, January 24, 2013 9:48:19 PM UTC+9, Akil Burgess wrote:

 Hi Takeshi,

 Thank you for your response. I have attached the logs for a 
 campaignAdExtension mutate operation and then a subsequent 
 CustomerSyncService get operation to this reply. Please let me know if I 
 can provide anything else that may help.

 Thanks,
 Akil

 On Thursday, January 24, 2013 8:59:35 AM UTC, Takeshi Hagikura (AdWords 
 API Team) wrote:

 Hello Akil,

 Thanks for writing in.
 Do you also have the request/response logs for CampaignAdExtension 
 mutate?

 I'd like to confirm if that should be included in the 
 CustomerSyncService response.

 Best,
 - Takeshi, AdWords API Team

 On Tuesday, January 22, 2013 1:56:32 AM UTC+9, Akil Burgess wrote:

 Hi All,

 The CustomerSyncService doesn't seem to be including addedAdExtensions 
 or deletedAdExtensions data. I've performed several CampaignAdExtension 
 updates (via the API and the AdWords web interface) in our test account 
 and 
 the CustomerSyncService does not show any of these changes. When I perform 
 CampaignAdExtensionService get operations I can see the updated data so it 
 seems like this data should have been processed and reflected in the 
 CustomerChangeData.

 *All* - Is anyone else seeing this behaviour?

 *API Team* - Is this a bug? Can someone take a look?

 I have pasted my request and response logs at the end of this message. 
 As we can see other changes (adgroups) are showing in CustomerChangeData 
 but no adExtensions.

 Thanks in advance for any help!

 Akil


 *Request:*

 ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=
 http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=
 http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
 http://www.w3.org/2001/XMLSchema;!--POST 
 /api/adwords/ch/v201209/CustomerSyncService
 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client 
 Protocol 4.0.30319.18010)
 VsDebuggerCausalityData: 
 uIDPoweSfT+RGipEr2AHcUx8fKcAfOeL1Iv+IUKx5K82Sb8Y4cEEsc5nCVxBn3ybnrh+mf8ACQAA
 Content-Type: text/xml; charset=utf-8
 SOAPAction: 
 Host: adwords.google.com
 Content-Length: 1463
 Accept-Encoding: gzip
 Connection: Keep-Alive
 TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
 --soap:HeaderRequestHeader xmlns=
 https://adwords.google.com/api/adwords/ch/v201209;authToken xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;**/authTokendeveloperToken
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;**/developerTokenclientCustomerId
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;2226963136/clientCustomerIduserAgent
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;** 
 (AwApi-DotNet/15.0.0, Common-Dotnet/1.4.0, .NET CLR/4.0.30319.18010, 
 gzip)/userAgent/RequestHeader/soap:Headersoap:Bodyget xmlns=
 https://adwords.google.com/api/adwords/ch/v201209;selectordateTimeRangemin
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;20130118 
 00 UTC/minmax xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;20130121 164714 
 UTC/max/dateTimeRangecampaignIds110290473/campaignIds/selector/get/soap:Body/soap:Envelope


 *Response:*
 *
 *
 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/
 !--Content-Encoding: 
 X-Content-Type-Options: nosniff
 X-Frame-Options: SAMEORIGIN
 X-XSS-Protection: 1; mode=block
 Content-Length: 455
 Cache-Control: private, max-age=0
 Content-Type: text/xml; charset=UTF-8
 Date: Mon, 21 Jan 2013 16:47:31 GMT
 Expires: Mon, 21 Jan 2013 16:47:31 GMT
 Server: GSE
 TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
 --soap:Headerns2:ResponseHeader xmlns:ns2=
 https://adwords.google.com/api/adwords/ch/v201209; xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;requestId0004d3cf3789ea980ab1540155c5/requestIdserviceNameCustomerSyncService/serviceNamemethodNameget/methodNameoperations0/operationsresponseTime1486/responseTimeunits0/units/ns2:ResponseHeader/soap:Headersoap:Bodyns2:getResponse
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209; xmlns:ns2=
 https://adwords.google.com/api/adwords/ch/v201209;ns2:rvalns2:changedCampaignsns2:campaignId110290473/ns2:campaignIdns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatusns2:changedAdGroupsns2:adGroupId6213230793/ns2:adGroupIdns2:adGroupChangeStatusFIELDS_CHANGED/ns2:adGroupChangeStatus/ns2:changedAdGroupsns2:campaignTargetingChangedfalse/ns2:campaignTargetingChanged/ns2:changedCampaignsns2:lastChangeTimestamp20130121
  
 163552 
 UTC/ns2:lastChangeTimestamp/ns2:rval/ns2:getResponse/soap:Body/soap:Envelope



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com

Re: CustomerSyncService Bug? Service not returning added or deleted adExtensions

2013-01-24 Thread Akil Burgess
Hi Takeshi,

Thank you for your response. I have attached the logs for a 
campaignAdExtension mutate operation and then a subsequent 
CustomerSyncService get operation to this reply. Please let me know if I 
can provide anything else that may help.

Thanks,
Akil

On Thursday, January 24, 2013 8:59:35 AM UTC, Takeshi Hagikura (AdWords API 
Team) wrote:

 Hello Akil,

 Thanks for writing in.
 Do you also have the request/response logs for CampaignAdExtension mutate?

 I'd like to confirm if that should be included in the CustomerSyncService 
 response.

 Best,
 - Takeshi, AdWords API Team

 On Tuesday, January 22, 2013 1:56:32 AM UTC+9, Akil Burgess wrote:

 Hi All,

 The CustomerSyncService doesn't seem to be including addedAdExtensions or 
 deletedAdExtensions data. I've performed several CampaignAdExtension 
 updates (via the API and the AdWords web interface) in our test account and 
 the CustomerSyncService does not show any of these changes. When I perform 
 CampaignAdExtensionService get operations I can see the updated data so it 
 seems like this data should have been processed and reflected in the 
 CustomerChangeData.

 *All* - Is anyone else seeing this behaviour?

 *API Team* - Is this a bug? Can someone take a look?

 I have pasted my request and response logs at the end of this message. As 
 we can see other changes (adgroups) are showing in CustomerChangeData but 
 no adExtensions.

 Thanks in advance for any help!

 Akil


 *Request:*

 ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=
 http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=
 http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
 http://www.w3.org/2001/XMLSchema;!--POST 
 /api/adwords/ch/v201209/CustomerSyncService
 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client 
 Protocol 4.0.30319.18010)
 VsDebuggerCausalityData: 
 uIDPoweSfT+RGipEr2AHcUx8fKcAfOeL1Iv+IUKx5K82Sb8Y4cEEsc5nCVxBn3ybnrh+mf8ACQAA
 Content-Type: text/xml; charset=utf-8
 SOAPAction: 
 Host: adwords.google.com
 Content-Length: 1463
 Accept-Encoding: gzip
 Connection: Keep-Alive
 TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
 --soap:HeaderRequestHeader xmlns=
 https://adwords.google.com/api/adwords/ch/v201209;authToken xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;**/authTokendeveloperToken
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;**/developerTokenclientCustomerId
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;2226963136/clientCustomerIduserAgent
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;** 
 (AwApi-DotNet/15.0.0, Common-Dotnet/1.4.0, .NET CLR/4.0.30319.18010, 
 gzip)/userAgent/RequestHeader/soap:Headersoap:Bodyget xmlns=
 https://adwords.google.com/api/adwords/ch/v201209;selectordateTimeRangemin
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209;20130118 
 00 UTC/minmax xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;20130121 164714 
 UTC/max/dateTimeRangecampaignIds110290473/campaignIds/selector/get/soap:Body/soap:Envelope


 *Response:*
 *
 *
 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/
 !--Content-Encoding: 
 X-Content-Type-Options: nosniff
 X-Frame-Options: SAMEORIGIN
 X-XSS-Protection: 1; mode=block
 Content-Length: 455
 Cache-Control: private, max-age=0
 Content-Type: text/xml; charset=UTF-8
 Date: Mon, 21 Jan 2013 16:47:31 GMT
 Expires: Mon, 21 Jan 2013 16:47:31 GMT
 Server: GSE
 TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
 --soap:Headerns2:ResponseHeader xmlns:ns2=
 https://adwords.google.com/api/adwords/ch/v201209; xmlns=
 https://adwords.google.com/api/adwords/cm/v201209;requestId0004d3cf3789ea980ab1540155c5/requestIdserviceNameCustomerSyncService/serviceNamemethodNameget/methodNameoperations0/operationsresponseTime1486/responseTimeunits0/units/ns2:ResponseHeader/soap:Headersoap:Bodyns2:getResponse
  
 xmlns=https://adwords.google.com/api/adwords/cm/v201209; xmlns:ns2=
 https://adwords.google.com/api/adwords/ch/v201209;ns2:rvalns2:changedCampaignsns2:campaignId110290473/ns2:campaignIdns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatusns2:changedAdGroupsns2:adGroupId6213230793/ns2:adGroupIdns2:adGroupChangeStatusFIELDS_CHANGED/ns2:adGroupChangeStatus/ns2:changedAdGroupsns2:campaignTargetingChangedfalse/ns2:campaignTargetingChanged/ns2:changedCampaignsns2:lastChangeTimestamp20130121
  
 163552 
 UTC/ns2:lastChangeTimestamp/ns2:rval/ns2:getResponse/soap:Body/soap:Envelope



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http

CustomerSyncService Bug? Service not returning added or deleted adExtensions

2013-01-21 Thread Akil Burgess
Hi All,

The CustomerSyncService doesn't seem to be including addedAdExtensions or 
deletedAdExtensions data. I've performed several CampaignAdExtension 
updates (via the API and the AdWords web interface) in our test account and 
the CustomerSyncService does not show any of these changes. When I perform 
CampaignAdExtensionService get operations I can see the updated data so it 
seems like this data should have been processed and reflected in the 
CustomerChangeData.

*All* - Is anyone else seeing this behaviour?

*API Team* - Is this a bug? Can someone take a look?

I have pasted my request and response logs at the end of this message. As 
we can see other changes (adgroups) are showing in CustomerChangeData but 
no adExtensions.

Thanks in advance for any help!

Akil


*Request:*

?xml version=1.0 encoding=utf-8?soap:Envelope 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema;!--POST 
/api/adwords/ch/v201209/CustomerSyncService
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client 
Protocol 4.0.30319.18010)
VsDebuggerCausalityData: 
uIDPoweSfT+RGipEr2AHcUx8fKcAfOeL1Iv+IUKx5K82Sb8Y4cEEsc5nCVxBn3ybnrh+mf8ACQAA
Content-Type: text/xml; charset=utf-8
SOAPAction: 
Host: adwords.google.com
Content-Length: 1463
Accept-Encoding: gzip
Connection: Keep-Alive
TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
--soap:HeaderRequestHeader 
xmlns=https://adwords.google.com/api/adwords/ch/v201209;authToken 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;**/authTokendeveloperToken
 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;**/developerTokenclientCustomerId
 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;2226963136/clientCustomerIduserAgent
 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;** 
(AwApi-DotNet/15.0.0, Common-Dotnet/1.4.0, .NET CLR/4.0.30319.18010, 
gzip)/userAgent/RequestHeader/soap:Headersoap:Bodyget 
xmlns=https://adwords.google.com/api/adwords/ch/v201209;selectordateTimeRangemin
 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;20130118 00 
UTC/minmax 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;20130121 164714 
UTC/max/dateTimeRangecampaignIds110290473/campaignIds/selector/get/soap:Body/soap:Envelope


*Response:*
*
*
soap:Envelope 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;!--Content-Encoding: 
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Length: 455
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=UTF-8
Date: Mon, 21 Jan 2013 16:47:31 GMT
Expires: Mon, 21 Jan 2013 16:47:31 GMT
Server: GSE
TimeStamp: Mon, 21 Jan 2013 16:47:16 GMT
--soap:Headerns2:ResponseHeader 
xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201209; 
xmlns=https://adwords.google.com/api/adwords/cm/v201209;requestId0004d3cf3789ea980ab1540155c5/requestIdserviceNameCustomerSyncService/serviceNamemethodNameget/methodNameoperations0/operationsresponseTime1486/responseTimeunits0/units/ns2:ResponseHeader/soap:Headersoap:Bodyns2:getResponse
 
xmlns=https://adwords.google.com/api/adwords/cm/v201209; 
xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201209;ns2:rvalns2:changedCampaignsns2:campaignId110290473/ns2:campaignIdns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatusns2:changedAdGroupsns2:adGroupId6213230793/ns2:adGroupIdns2:adGroupChangeStatusFIELDS_CHANGED/ns2:adGroupChangeStatus/ns2:changedAdGroupsns2:campaignTargetingChangedfalse/ns2:campaignTargetingChanged/ns2:changedCampaignsns2:lastChangeTimestamp20130121
 
163552 
UTC/ns2:lastChangeTimestamp/ns2:rval/ns2:getResponse/soap:Body/soap:Envelope

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en





AdWords Test Accounts showing in the AdWords web interface

2013-01-17 Thread Akil Burgess
Hi All,

I recently set up two API test accounts but I am unsure as to whether they 
are actually set up as test accounts. The API Getting Started docs say:

   - Test Accounts are not visible in and not accessible via AdWords User 
   Interface.
   - My Client Center (MCC) level calls, such as 
ManagedCustomerServicehttps://developers.google.com/adwords/api/docs/reference/latest/ManagedCustomerService
get and mutate cannot be used.
   
Both of the accounts are still visible in the user interface and after 
setting my clientCustomerId to the test accounts I can still use the 
ManagedCustomerService (The 'get' operation returns the single test 
account). How can I be certain that the accounts are set up as test 
accounts? Does anyone else get the same experience with test accounts?

Thanks,
Akil

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en





Re: test account query

2013-01-15 Thread Akil Burgess
Hi Danial,

I have the same problem as Chirag. We're still waiting for an email 
confirming that the test account is set up. Can you help?

Thanks,
Akil

On Thursday, 3 January 2013 08:03:07 UTC, Danial Klimkin wrote:

 Hello Chirag,


 The Test Account CId you've sent me is now set up properly, you can start 
 using it for testing.


 -Danial, AdWords API Team.



 On Thursday, January 3, 2013 9:01:03 AM UTC+4, Chirag wrote:

 Hello Danial,

 I have send you required information to your mail.
 Please guide me what i am doing wrong.



 On Friday, December 28, 2012 3:04:41 PM UTC+5:30, Danial Klimkin wrote:

 Hello Chirag,


 Please send me your MCC and test account CIDs over email.


 -Danial, AdWords API Team.


 On Friday, December 28, 2012 1:14:39 PM UTC+4, Chirag wrote:

 Hi Danial,

 I have applied for test account. I didn't received result on my email 
 id.
 The docs said (
 https://developers.google.com/adwords/api/docs/test-accounts), You 
 will receive the results from your application at the contact email 
 address.If you do not receive the results within 10 days of your 
 application write on forum. 

 Its been 15 days seen i had applied for test account.

 Please suggest me.




 On Monday, December 24, 2012 4:10:35 PM UTC+5:30, Danial Klimkin wrote:

 Hello John,


 Yes, this is normal. We are exploring the option to keep Test Accounts 
 visible in the UI as this might be helpful for developers.


 -Danial, AdWords API Team.



 On Wednesday, December 19, 2012 6:32:36 PM UTC+4, John Lister wrote:

 Hi, I registered for a test account and it looks to have been 
 approved. However prior to the approval, some updates were made to the 
 account and it was showing in the web user interface as what looked to 
 be a 
 normal account. I can see that the cost for updates is now 0, so it does 
 indeed appear to be a test account, but the account still shows in the 
 web 
 UI and I can manipulate it as normal via the UI.

 The docs imply that you cannot see test accounts in the UI, so my 
 question are: is it actually a test account and can they be seen in the 
 UI? 
 and are the updates previously done now live with new updates being 
 disabled or is it all disabled?

 Thanks

 John



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en





Re: Bug in AdGroupCriterionService? BiddableAdGroupCriterion returned with a null criterion

2012-11-19 Thread Akil Burgess
Ping?

On Thursday, 15 November 2012 12:05:41 UTC, Akil Burgess wrote:

 Hi All,
  
 I am running into an issue *in production* where the 
 AdGroupCriterionService is returning a BiddableAdGroupCriterion with a null 
 Criterion. Has anyone else seen this before? AdWords API Team - Can you 
 please investigate this issue? An example requestId is: *
 requestId0004ce872f2df7380a96b91453a7/requestId*
  
 Thanks in advance for any help.
  
 Regards,
 Akil


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en





Bug in AdGroupCriterionService? BiddableAdGroupCriterion returned with a null criterion

2012-11-15 Thread Akil Burgess
Hi All,
 
I am running into an issue *in production* where the 
AdGroupCriterionService is returning a BiddableAdGroupCriterion with a null 
Criterion. Has anyone else seen this before? AdWords API Team - Can you 
please investigate this issue? An example requestId is: *
requestId0004ce872f2df7380a96b91453a7/requestId*
 
Thanks in advance for any help.
 
Regards,
Akil

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: CustomerSyncService Bug? CustomerSyncService not returning changed criteria when AdGroupCriteron are added to two or more adgroups in one operation

2012-08-08 Thread Akil Burgess
Hi David,

I just tried this in production and I was not able to reproduce the issue.

Thanks,

Akil

On Tuesday, August 7, 2012 6:12:06 PM UTC+1, David Torres wrote:

 Hi Akil,

 Is this also reproduceable in production?

 Best,

 -David Torres - AdWords API Team

 On Friday, August 3, 2012 6:25:23 AM UTC-4, Akil Burgess wrote:

 Hi All,

 I am seeing an issue where the CustomerSyncService is not showing the 
 correct change data when I follow these steps:

1. I perform an AdGroupCriterionService.mutate operation that adds a 
keyword to two different adgroups (*
requestId 0004c65980b97b580aeddd445bee*)
2. Perform CustomerSyncService.get using a timerange that contains 
that mutate operation (*requestId 0004c659815517480a96292176e2*)

 Expected: The CustomerChangeData should contain AdGroupChangeData with 
 changedCriteria
 Actual: The CustomerChangeData contains no changes.

 I've only tested for this bug in the API sandbox but this issue occurs 
 whether I submit the operations via the AdGroupCriterionService or the 
 MutateJobService.

 For now I can work around the issue by only submitting operations on a 
 per adgroup basis but this definitely seems like a bug. Has anyone else 
 come across this issue? *API Team -* Can you please investigate this 
 issue?

 Thanks in advance!

 Akil



-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


CustomerSyncService Bug? CustomerSyncService not returning changed criteria when AdGroupCriteron are added to two or more adgroups in one operation

2012-08-03 Thread Akil Burgess
Hi All,

I am seeing an issue where the CustomerSyncService is not showing the 
correct change data when I follow these steps:

   1. I perform an AdGroupCriterionService.mutate operation that adds a 
   keyword to two different adgroups (*
   requestId 0004c65980b97b580aeddd445bee*)
   2. Perform CustomerSyncService.get using a timerange that contains that 
   mutate operation (*requestId 0004c659815517480a96292176e2*)
   
Expected: The CustomerChangeData should contain AdGroupChangeData with 
changedCriteria
Actual: The CustomerChangeData contains no changes.

I've only tested for this bug in the API sandbox but this issue occurs 
whether I submit the operations via the AdGroupCriterionService or the 
MutateJobService.

For now I can work around the issue by only submitting operations on a per 
adgroup basis but this definitely seems like a bug. Has anyone else come 
across this issue? *API Team -* Can you please investigate this issue?

Thanks in advance!

Akil

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Is it possible to have the same AdExtensionId for AdExtensions in different Accounts?

2012-07-23 Thread Akil Burgess
Hi All,

Is it possible that two accounts can have two separate AdExtensions that 
have the same *AdExtensionId*? i.e. Is AdExtensionId globablly unique in an 
MCC account?

Thanks,
Akil

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Do AdParams changes show in CustomerChangeData?

2012-07-16 Thread Akil Burgess
Ping?

On Thursday, July 12, 2012 7:05:38 AM UTC+1, Akil Burgess wrote:


 Hi All,

 Are changes made to AdParams accessible via the CustomerSyncSelector? If 
 not, any suggestions for ways to keep AdParams information up-to-date?

 Thanks,
 Akil


-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Do AdParams changes show in CustomerChangeData?

2012-07-12 Thread Akil Burgess

Hi All,

Are changes made to AdParams accessible via the CustomerSyncSelector? If 
not, any suggestions for ways to keep AdParams information up-to-date?

Thanks,
Akil

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Getting the Change History via the API

2012-06-26 Thread Akil Burgess
Hi Anash,

Is there any other service that does give the change details? If not, are 
there plans to support this in the future?

Thanks,
Akil Burgess

On Tuesday, June 26, 2012 11:12:11 AM UTC+1, Anash P. Oommen wrote:

 Hi Oliver,

 CustomerSyncService doesn't give you the kind of change details you are 
 looking for, it is mostly useful for figuring out what objects changed 
 during a time period and then sync local databases with AdWords API server 
 by downloading only the modified objects.

 Cheers,
 Anash P. Oommen,
 AdWords API Advisor.

 On Monday, 18 June 2012 21:36:50 UTC+5:30, Oliver wrote:

 Hi,

 I believe the only way to get some data about the 'Change History' is by 
 using the CustomerSyncService object. 

 Looking at this object I have 2 questions:

 1) There doesn't seem to be a timestamp given for when the change took 
 place.  This is unlike the adwords interface that tells you when and how 
 performed the change.  Correct?

 2) It doesn't tell you the nature of the change e.g. if the 'Target CPA' 
 of an adgroup changed, all the API can tell me is that there was a change 
 to the adgroup (but it can't tell me what the change is).  Again, this is 
 different from the interface. Correct?

 Many thanks.

 Oliver



-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: CustomerSyncService Bug? CustomerSyncService not returning CampaignChange as NEW

2012-05-30 Thread Akil Burgess
For anyone interested in this thread it seems like this is either an 
intermittent issue or it was fixed. For the same request I am now correctly 
receiving the campaign as NEW.

*API Team -* Any ideas what the issue may have been with my previous 
request?

Thanks,
Akil

On Friday, 25 May 2012 14:32:51 UTC+1, Akil Burgess wrote:

 Ping?

 On Wednesday, 23 May 2012 16:14:39 UTC+1, Akil Burgess wrote:

 Hi all,

 I am seeing an issue where the CustomerSyncService is returning a 
 campaign as FIELDS_UNCHANGED (but it has addedAdExtensions) in a time 
 range that definitely contains the time where the campaign was created. My 
 date range starts at the min time supported by the API so I would expect 
 the campaign to return as NEW (or that it would have no sub-changes if it 
 hadn't been created yet).

 Is this a bug in the CustomerSyncService change aggregation? I've pasted 
 the api call xml at the end of this message.

 Request ID: *0004c0b55eb53c800ada3f9149c2*

 Thanks,

 Akil



 -BEGIN API CALL-
  
 Request
 ---
  ?xml version=1.0 encoding=utf-8?soap:Envelope 
 xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; soap:Header   
 RequestHeader xmlns=https://adwords.google.com/api/adwords/ch/v201109;
authToken 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/authToken 
 developerToken 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/developerToken
clientCustomerId 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;9567252878/clientCustomerId
userAgent 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/userAgent 
 /RequestHeader/soap:Header  soap:Body get 
 xmlns=https://adwords.google.com/api/adwords/ch/v201109; 
 selector  dateTimeRange  
min 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;19700101 00 
 UTC/minmax 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;20110125 171228 
 UTC/max/dateTimeRange
 campaignIds60421525/campaignIds 
 /selector /get  /soap:Body/soap:Envelope
  
 Response
 
  soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;  
 soap:Header   ns2:ResponseHeader 
 xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201109; 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;   
  requestId0004c0b55eb53c800ada3f9149c2/requestId 
 operations0/operations  
 responseTime123/responseTimeunits0/units 
/ns2:ResponseHeader   /soap:Header  soap:Body 
 ns2:getResponse xmlns=https://adwords.google.com/api/adwords/cm/v201109; 
 xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201109;   
 ns2:rval  ns2:changedCampaigns   
ns2:campaignId60421525/ns2:campaignId 
   
 ns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatus

 ns2:addedAdExtensions92982565/ns2:addedAdExtensions  

 ns2:campaignTargetingChangedfalse/ns2:campaignTargetingChanged   
/ns2:changedCampaigns 
 ns2:lastChangeTimestamp20110125 171228 UTC/ns2:lastChangeTimestamp   
/ns2:rval /ns2:getResponse  
 /soap:Body/soap:Envelope
 -END API CALL---
  



-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: CustomerSyncService Bug? CustomerSyncService not returning CampaignChange as NEW

2012-05-25 Thread Akil Burgess
Ping?

On Wednesday, 23 May 2012 16:14:39 UTC+1, Akil Burgess wrote:

 Hi all,

 I am seeing an issue where the CustomerSyncService is returning a campaign 
 as FIELDS_UNCHANGED (but it has addedAdExtensions) in a time range that 
 definitely contains the time where the campaign was created. My date range 
 starts at the min time supported by the API so I would expect the campaign 
 to return as NEW (or that it would have no sub-changes if it hadn't been 
 created yet).

 Is this a bug in the CustomerSyncService change aggregation? I've pasted 
 the api call xml at the end of this message.

 Request ID: *0004c0b55eb53c800ada3f9149c2*

 Thanks,

 Akil



 -BEGIN API CALL-
  
 Request
 ---
  ?xml version=1.0 encoding=utf-8?soap:Envelope 
 xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema;  soap:Header   
 RequestHeader xmlns=https://adwords.google.com/api/adwords/ch/v201109; 
   authToken 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/authToken  
developerToken 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/developerToken
clientCustomerId 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;9567252878/clientCustomerId
userAgent 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/userAgent  
/RequestHeader/soap:Header  soap:Body get 
 xmlns=https://adwords.google.com/api/adwords/ch/v201109; 
 selector  dateTimeRange   
   min 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;19700101 00 
 UTC/minmax 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;20110125 171228 
 UTC/max/dateTimeRange 
campaignIds60421525/campaignIds 
 /selector /get  /soap:Body/soap:Envelope
  
 Response
 
  soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;   
 soap:Header   ns2:ResponseHeader 
 xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201109; 
 xmlns=https://adwords.google.com/api/adwords/cm/v201109;
 requestId0004c0b55eb53c800ada3f9149c2/requestId 
 operations0/operations  
 responseTime123/responseTimeunits0/units  
   /ns2:ResponseHeader   /soap:Header  soap:Body 
 ns2:getResponse xmlns=https://adwords.google.com/api/adwords/cm/v201109; 
 xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201109;
ns2:rval  ns2:changedCampaigns 
  ns2:campaignId60421525/ns2:campaignId

 ns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatus 
   
 ns2:addedAdExtensions92982565/ns2:addedAdExtensions   
   ns2:campaignTargetingChangedfalse/ns2:campaignTargetingChanged  
 /ns2:changedCampaigns 
 ns2:lastChangeTimestamp20110125 171228 UTC/ns2:lastChangeTimestamp
   /ns2:rval /ns2:getResponse  
 /soap:Body/soap:Envelope
 -END API CALL---
  



-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


CustomerSyncService Bug? CustomerSyncService not returning CampaignChange as NEW

2012-05-23 Thread Akil Burgess
Hi all,

I am seeing an issue where the CustomerSyncService is returning a campaign 
as FIELDS_UNCHANGED (but it has addedAdExtensions) in a time range that 
definitely contains the time where the campaign was created. My date range 
starts at the min time supported by the API so I would expect the campaign 
to return as NEW (or that it would have no sub-changes if it hadn't been 
created yet).

Is this a bug in the CustomerSyncService change aggregation? I've pasted 
the api call xml at the end of this message.

Request ID: *0004c0b55eb53c800ada3f9149c2*

Thanks,

Akil



-BEGIN API CALL-
 
Request
---
 ?xml version=1.0 encoding=utf-8?soap:Envelope 
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:Header   
RequestHeader xmlns=https://adwords.google.com/api/adwords/ch/v201109;   
authToken 
xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/authToken
 developerToken 
xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/developerToken
   clientCustomerId 
xmlns=https://adwords.google.com/api/adwords/cm/v201109;9567252878/clientCustomerId
   userAgent 
xmlns=https://adwords.google.com/api/adwords/cm/v201109;**/userAgent
 /RequestHeader/soap:Header  soap:Body get 
xmlns=https://adwords.google.com/api/adwords/ch/v201109; 
selector  dateTimeRange 
min xmlns=https://adwords.google.com/api/adwords/cm/v201109;19700101 
00 UTC/minmax 
xmlns=https://adwords.google.com/api/adwords/cm/v201109;20110125 171228 
UTC/max/dateTimeRange   
 campaignIds60421525/campaignIds /selector
 /get  /soap:Body/soap:Envelope
 
Response

 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; 
soap:Header   ns2:ResponseHeader 
xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201109; 
xmlns=https://adwords.google.com/api/adwords/cm/v201109;
requestId0004c0b55eb53c800ada3f9149c2/requestId 
operations0/operations  
responseTime123/responseTimeunits0/units
/ns2:ResponseHeader   /soap:Header  soap:Body 
ns2:getResponse xmlns=https://adwords.google.com/api/adwords/cm/v201109; 
xmlns:ns2=https://adwords.google.com/api/adwords/ch/v201109;  
 ns2:rval  ns2:changedCampaigns 
 ns2:campaignId60421525/ns2:campaignId  
 
ns2:campaignChangeStatusFIELDS_UNCHANGED/ns2:campaignChangeStatus   
ns2:addedAdExtensions92982565/ns2:addedAdExtensions 

ns2:campaignTargetingChangedfalse/ns2:campaignTargetingChanged  
/ns2:changedCampaigns 
ns2:lastChangeTimestamp20110125 171228 UTC/ns2:lastChangeTimestamp  
/ns2:rval /ns2:getResponse  
/soap:Body/soap:Envelope
-END API CALL---
 

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Why does Selector.DateRange include campaigns/adgroups etc from outside of the given range?

2012-02-20 Thread Akil Burgess
I think I've found the answer on my own:

http://adwordsapi.blogspot.com/2011/03/discover-v201101-generic-selectors.html

*DateRangehttp://code.google.com/apis/adwords/docs/reference/latest/CampaignService.Selector.html#dateRange
:* You can provide an optional 
DateRangehttp://code.google.com/apis/adwords/docs/reference/latest/CampaignService.DateRange.html
 to 
control the date range for which the data is retrieved. Specifying a date 
range only affects the stats returned by the server (if applicable), not 
the actual entities being returned by the server. The date format for 
minhttp://code.google.com/apis/adwords/docs/reference/latest/CampaignService.DateRange.html#min
 and 
maxhttp://code.google.com/apis/adwords/docs/reference/latest/CampaignService.DateRange.html#max
 fields 
have the format mmdd. The date range should be in the range [19700101, 
20380101]. 

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Adhoc Reports: What is the smallest custom date range supported?

2012-01-06 Thread Akil Burgess
Hi all,

What is the smallest custom date range supported by the AdHoc reports API?

I receive a 400 Bad Request error when I try to use date ranges in the 
MMDD hhmmss UTC format but the MMDD format works fine. Can 
someone confirm whether days are the smallest unit supported by the reports 
API? If so, why is this the case when the rest of the API (e.g. the 
CustomerSyncService) provides data that can be as recent as a couple of 
hours?

Thanks in advance for any help.

Cheers,

Akil Burgess

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


AdGroupChangeData.ChangedCriteria - Does this represent changes to AdGroupCriteria or actual Criteria?

2011-12-13 Thread Akil Burgess
Hi all,

Does AdGroupChangeData.changedCriteria represent changes to an 
AdGroupCriterion or to the global Criterion entities?

If I understand the threads that I have read correctly (
http://code.google.com/apis/adwords/community/?place=topic%2Fadwords-api%2F0MiWmzI1m8M%2Fdiscussion),
 
Criterion IDs are globally unique across campaigns/accounts etc.

Given that, I'm a bit confused at what exactly is represented by the 
AdGroupChangeData.changedCriteria since it's a bit strange that a globally 
unique criterion would able to change.

Thanks in advance for any help.

Akil

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en