Re: java.lang.NullPointerException: Unknown field name: null.

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Ray,

It turns out the source of your NullPointer is because in the Display Name 
of the ReportDefinitionService, there's a value of 'Policy' returned as you 
can see by our documentation for the PolicySummary 
.
 
That does not align with what is coming back in the report header right 
now, which is 'Ad policies'. The difference between the two is causing an 
issue. I've filed an issue with my team to try to get this fixed. In the 
meantime, you could possibly modify your code to catch this and continue 
since you now know what this is.  I don't have a current timeline on the 
fix, but I will keep this thread updated when it does get fixed.

Best,
Nadine, AdWords API Team

On Wednesday, April 18, 2018 at 8:54:49 PM UTC-4, Ray Chang wrote:
>
> "ReportQuery": {
>"ReportType": "AD_PERFORMANCE_REPORT",
>"Fields": 
> "ExternalCustomerId,AccountDescriptiveName,CampaignId,CampaignName,AdGroupId,AdGroupName,Id,PolicySummary,Headline"
> ,
>"Conditions": "CampaignStatus=ENABLED and AdGroupStatus=ENABLED and 
> Status=ENABLED and CombinedApprovalStatus=DISAPPROVED",
>"DateRange": "YESTERDAY"
>  }
>
>
> PolicySummary field is *Ad policies*, but fieldsMapping have no Ad 
> policies, only *Policy=PolicySummary， so *java.lang.NullPointerException: 
> Unknown field name: null.
>
> [Customer ID, Account, Campaign ID, Campaign, Ad group ID, Ad group, Ad ID
> , Ad policies, Ad]
>
>
>
> {Click Assisted Conv. Value=ClickAssistedConversionValue, CTR=Ctr, Account
> =AccountDescriptiveName, Final URL=CreativeFinalUrls, Keyword ID=
> CriterionId, Path 1=Path1, Path 2=Path2, App final URL=
> CreativeFinalAppUrls, Image Ad URL=ImageAdUrl, Image ID (responsive)=
> EnhancedDisplayCreativeMarketingImageMediaId, Long headline=LongHeadline, 
> Month=Month, Day of week=DayOfWeek, Currency=AccountCurrencyCode, Network=
> AdNetworkType1, Gmail ad marketing image headline=MarketingImageHeadline, 
> Logo ID (responsive)=EnhancedDisplayCreativeLogoImageMediaId, Impressions=
> Impressions, Active View measurable cost=ActiveViewMeasurableCost, Active 
> View viewable impr. / measurable impr.=ActiveViewViewability, Base Ad 
> group ID=BaseAdGroupId, Headline 2=HeadlinePart2, Headline 1=HeadlinePart1
> , Labels=Labels, Interaction Types=InteractionTypes, Conversions=
> Conversions, Client name=CustomerDescriptiveName, Ad state=Status, 
> Conversions (current model)=CurrentModelAttributedConversions, Auto-applied 
> ad suggestion=Automated, Week=Week, Conversion Tracker Id=
> ConversionTrackerId, Total conv. value=ConversionValue, Cost / conv.=
> CostPerConversion, Impr. Assisted Conv.=ImpressionAssistedConversions, 
> Description=Description, Ad=Headline, Engagement rate=EngagementRate, 
> Square image ID (responsive)=
> EnhancedDisplayCreativeMarketingImageSquareMediaId, Gmail ad marketing 
> image media id=GmailCreativeMarketingImageMediaId, All conv. rate=
> AllConversionRate, Label IDs=LabelIds, Gmail saves=GmailSaves, View-through 
> conv.=ViewThroughConversions, Gmail ad logo image media id=
> GmailCreativeLogoImageMediaId, Description line 2=Description2, Display 
> URL=DisplayUrl, Allow flexible color (responsive)=AllowFlexibleColor, 
> Custom parameter=CreativeUrlCustomParameters, Description line 1=
> Description1, Campaign state=CampaignStatus, Conv. value (current model)=
> CurrentModelAttributedConversionValue, Video played to 25%=
> VideoQuartile25Rate, % new sessions=PercentNewVisitors, Landscape logo ID 
> (responsive)=EnhancedDisplayCreativeLandscapeLogoImageMediaId, Avg. 
> session duration (seconds)=AverageTimeOnSite, Active View viewable CTR=
> ActiveViewCtr, Interaction Rate=InteractionRate, Bounce rate=BounceRate, 
> Image Height=ImageCreativeImageHeight, View rate=VideoViewRate, Price 
> prefix (responsive)=PricePrefix, Active View viewable impressions=
> ActiveViewImpressions, Pages / session=AveragePageviews, Avg. position=
> AveragePosition, Destination URL=CreativeDestinationUrl, Gmail forwards=
> GmailForwards, Call-only ad phone number=CallOnlyPhoneNumber, Gmail 
> clicks to website=GmailSecondaryClicks, Year=Year, Value / conv.=
> ValuePerConversion, Tracking template=CreativeTrackingUrlTemplate, 
> Conversion name=ConversionTypeName, Short headline=ShortHeadline, Business 
> name=BusinessName, Clicks=Clicks, Day=Date, Policy=PolicySummary, Quarter=
> Quarter, Ad format preference (responsive)=FormatSetting, Avg. CPV=
> AverageCpv, Call to action text (responsive)=CallToActionText, Gmail ad 
> header image media id=GmailCreativeHeaderImageMediaId, Top vs. Other=Slot, 
> Gmail ad marketing image call to action text color=
> MarketingImageCallToActionTextColor, Accent color (responsive)=AccentColor
> , Cost / conv. (current model)=CostPerCurrentModelAttributedConversion, 
> Campaign ID=CampaignId, Gmail ad description=GmailTeaserDescription, Video 
> played to 75%=VideoQuartile75Rate, Active View 

Re: Value for userInterestParentId field when adding audience

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello All,

Thank you so much for following up! That makes a lot more sense. We'll be 
updating our docs shortly. We're in the process of doing that now. Thanks 
again for being such good citizens and bringing this up!

Regards,
Nadine, AdWords API Team

On Thursday, April 19, 2018 at 1:17:52 PM UTC-4, Gary Jiang wrote:
>
> Great! Thanks a lot.
>
> On Wednesday, April 18, 2018 at 8:07:47 PM UTC-7, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Gary,
>>
>> I don't have a CSV ready to go because we have to go through the process 
>> of getting that properly published, but we do have an API service that can 
>> get you this list. You can use 
>> ConstantDataService.getUserInterestCriterion() 
>> 
>>  to 
>> get back the list of available ones already. Please get back to me if you 
>> see those old ones when you pull them down through that service. That would 
>> mean that there is a further issue. I've found that service is up-to-date, 
>> though.
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Wednesday, April 18, 2018 at 12:48:43 PM UTC-4, Gary Jiang wrote:
>>>
>>> Also can we have a list of outdated categories in the CSV file so far? 
>>> Thanks
>>>
>>> On Wednesday, April 18, 2018 at 7:00:11 AM UTC-7, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Gary,

 Thank you for providing all the amazing details privately. They were 
 really helpful in tracking this down. I'm answering out on the forum in 
 case one of your fellow developers bumps into this. I turns out that the 
 affinity 
 categories 
 
  we 
 currently have listed in our documentation are a bit out of sync with the 
 AdWords UI. We'll get them updated right away. Those categories that are 
 giving you an error don't even exist in the AdWords UI. In our back-end 
 system, they must have been recently removed, and we didn't update our 
 list 
 to reflect that. Thank you for catching this and bringing this to our 
 attention. Unfortunately, this means those categories are no longer 
 available, but at least you've helped some people by making sure our 
 documentation gets updated. Thank you!

 Best,
 Nadine, AdWords API Team

 On Tuesday, April 17, 2018 at 2:05:39 AM UTC-4, Vincent Racaza (AdWords 
 API Team) wrote:
>
> Hi Gary,
>
> You just need to set the userInterestId 
> 
>  field, 
> and not the userInterestParentid 
> 
>  field 
> as this is a read-only field when creating a CriterionUserInterest. 
> Kindly 
> edit your request and let me know how it works. If any issues occur, 
> please 
> provide the SOAP request and response logs via *Reply privately to 
> author* option so I can further check.
>
> Thanks,
> Vincent
> 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+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.
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/22708b71-4d27-4713-bfcb-13a338c7aa86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Value for userInterestParentId field when adding audience

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Matthew,

My assumption was that this was a one-off, but it sounds like you might be 
separate from Gary? It is unusual for things to just disappear like that. I 
would have to pop through our announcements. What day exactly did you start 
seeing these errors? That would help me narrow down when exactly they were 
removed.

Thanks,
Nadine, AdWords API Team

On Wednesday, April 18, 2018 at 6:06:23 PM UTC-4, Matthew Wawrin wrote:
>
> I'm assuming that this fix to the API is why I'm now seeing errors for 
> user interest categories that we've been using for months are now throwing 
> errors and are no longer documented in the list. 
>
> I see specific brands we were using are no longer available.  Is there a 
> specific reason these were removed?
>
> When these criteria lists change, are they announced anywhere?
>
> Thanks
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/2eded4c6-6e3e-44ff-90ed-bd95c294d693%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Value for userInterestParentId field when adding audience

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Gary,

I don't have a CSV ready to go because we have to go through the process of 
getting that properly published, but we do have an API service that can get 
you this list. You can use ConstantDataService.getUserInterestCriterion() 

 to 
get back the list of available ones already. Please get back to me if you 
see those old ones when you pull them down through that service. That would 
mean that there is a further issue. I've found that service is up-to-date, 
though.

Cheers,
Nadine, AdWords API Team

On Wednesday, April 18, 2018 at 12:48:43 PM UTC-4, Gary Jiang wrote:
>
> Also can we have a list of outdated categories in the CSV file so far? 
> Thanks
>
> On Wednesday, April 18, 2018 at 7:00:11 AM UTC-7, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Gary,
>>
>> Thank you for providing all the amazing details privately. They were 
>> really helpful in tracking this down. I'm answering out on the forum in 
>> case one of your fellow developers bumps into this. I turns out that the 
>> affinity 
>> categories 
>> 
>>  we 
>> currently have listed in our documentation are a bit out of sync with the 
>> AdWords UI. We'll get them updated right away. Those categories that are 
>> giving you an error don't even exist in the AdWords UI. In our back-end 
>> system, they must have been recently removed, and we didn't update our list 
>> to reflect that. Thank you for catching this and bringing this to our 
>> attention. Unfortunately, this means those categories are no longer 
>> available, but at least you've helped some people by making sure our 
>> documentation gets updated. Thank you!
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Tuesday, April 17, 2018 at 2:05:39 AM UTC-4, Vincent Racaza (AdWords 
>> API Team) wrote:
>>>
>>> Hi Gary,
>>>
>>> You just need to set the userInterestId 
>>> 
>>>  field, 
>>> and not the userInterestParentid 
>>> 
>>>  field 
>>> as this is a read-only field when creating a CriterionUserInterest. Kindly 
>>> edit your request and let me know how it works. If any issues occur, please 
>>> provide the SOAP request and response logs via *Reply privately to 
>>> author* option so I can further check.
>>>
>>> Thanks,
>>> Vincent
>>> 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+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.
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/88572d40-91aa-49ec-ae8b-b0d37680e112%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Value for userInterestParentId field when adding audience

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Gary,

Thank you for providing all the amazing details privately. They were really 
helpful in tracking this down. I'm answering out on the forum in case one 
of your fellow developers bumps into this. I turns out that the affinity 
categories 

 we 
currently have listed in our documentation are a bit out of sync with the 
AdWords UI. We'll get them updated right away. Those categories that are 
giving you an error don't even exist in the AdWords UI. In our back-end 
system, they must have been recently removed, and we didn't update our list 
to reflect that. Thank you for catching this and bringing this to our 
attention. Unfortunately, this means those categories are no longer 
available, but at least you've helped some people by making sure our 
documentation gets updated. Thank you!

Best,
Nadine, AdWords API Team

On Tuesday, April 17, 2018 at 2:05:39 AM UTC-4, Vincent Racaza (AdWords API 
Team) wrote:
>
> Hi Gary,
>
> You just need to set the userInterestId 
> 
>  field, 
> and not the userInterestParentid 
> 
>  field 
> as this is a read-only field when creating a CriterionUserInterest. Kindly 
> edit your request and let me know how it works. If any issues occur, please 
> provide the SOAP request and response logs via *Reply privately to author* 
> option 
> so I can further check.
>
> Thanks,
> Vincent
> 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+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.
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/3e44e065-783b-4287-b465-f1c01f71b3c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: I'm get error about AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED when used BudgetService

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings AdWordsians!

First of all, I would like to give a big shout-out to the amazing community 
for helping each other out through this one! I also have some good news. As 
of now, you should no longer be seeing any more errors with 
BudgetOrderService. We are currently running an an internal investigation 
and working towards putting things in place so this particular issue does 
not happen again. Thank you for taking the time to help us out.

Best,
Nadine, AdWords API Team

On Thursday, April 5, 2018 at 4:15:07 AM UTC-4, วรวุฒิ บุญตัน wrote:
>
> I'm temporary fix by following this open issue.
>
> https://github.com/googleads/googleads-dotnet-lib/issues/160
>
> IMO We both the same problem it should be related to request header.
>
>
> On Wednesday, 4 April 2018 21:56:52 UTC+7, Dhanya Sundararaju (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Could you please reply back with complete SOAP request and response of 
>> any one failed request so that we can take a closer look?
>>
>> Regards,
>> Dhanya, 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+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.
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/dbd7a34f-4190-4a3b-bdc7-0d4c4f37771a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to get account budget

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

It's me again. I was just thinking. If all you want to do is send an email 
when the budget gets close to being used, then you can also use automated 
rules . This is 
outside the API, but it allows you to set up a rule, that will alert you 
when you reach a certain point.  I figured I would mention this in case it 
helps.

Best,
Nadine, AdWords API Team

On Thursday, April 5, 2018 at 2:39:20 PM UTC-4, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hello,
>
> I totally understand how sad that is. To implement this as a feature in 
> the API would take a lot of work, which is why you have not seen any 
> progress on this. We get a lot of feature requests, and we often have to 
> choose the ones that are requested the most. It's helpful to hear from 
> people like you to know that there are other people who would want this 
> feature. 
>
> I have never met anyone who parses the web interface. I have met people 
> who download the invoices and parse that. Another things that some people 
> do is that they look at the budget on the campaign and tell people how much 
> budget remains on each of the campaigns instead of on the account. That is 
> another possible solution.
>
> Regards,
> Nadine, AdWords API Team
>
> On Thursday, April 5, 2018 at 2:17:41 AM UTC-4, kislo...@gmail.com wrote:
>>
>> Can I fine-tune how to send letters to the e-mail about the amount of the 
>> remaining balance (budget)?
>>
>> среда, 4 апреля 2018 г., 17:13:55 UTC+3 пользователь Nadine Sundquist 
>> (AdWords API Team) написал:
>>>
>>> Greetings!
>>>
>>> Thanks for taking the time to try that out. I'm sorry to hear that it 
>>> didn't match exactly what you needed. I appreciate the screenshots. That's 
>>> really helpful. In order to get what you're asking for, you would need the 
>>> BudgetOrderService 
>>> .
>>>  
>>> However, there's a catch. It's only supported in the API if you have 
>>> consolidated billing set up. Otherwise, that information can't be retrieved 
>>> through the API. I've already put in a feature request to make this 
>>> supported for all other kinds of billing in the future because I think that 
>>> would be helpful.There isn't a date as to when something like that would be 
>>> available.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Wednesday, April 4, 2018 at 4:50:06 AM UTC-4, kisl...@gmail.com 
>>> wrote:

 Hello, thanks for answer

 We tried to use the "Budget Performance Report", but this is not what 
 we need. This method returns the budget from the "Shared Budget"

 Url interface: 
 https://adwords.google.com/aw/sharedbudgets?ocid=254362058&__c=8977077242=0&__u=6415393025
 Screen: http://take.ms/yCCkQ

 But we have a task to receive a budget from the section "Billing & 
 payments" -> "Account budgets"
 Url: 
 https://adwords.google.com/aw/billing/budgets?ocid=254362058=433291332&__c=8977077242=0&__u=6415393025
 Screen: http://take.ms/BW4g9

 We want to get the "Budget ammount" field (104$ on screenshot)

 How can I get this field? 

 вторник, 13 февраля 2018 г., 1:55:36 UTC+3 пользователь Nadine 
 Sundquist (AdWords API Team) написал:
>
> Hello,
>
> Could you do me a huge favor in the future? When you notice that a 
> thread is much older, could you start a new thread and just reference the 
> old forum post with a link? That makes it much easier in case the 
> questions 
> are a little different. In your case, you do have a few different 
> questions. In order to save you a bit of time, I won't ask you to start a 
> new thread this time, but I'll just answer it here. 
>
> 1) any news about this question?
> We took this question offline and worked with the user to determine if 
> they were qualified to use the BudgetOrderSerivce. In order to even be 
> considered, your whole account structure needs to be set up for 
> consolidated 
> billing . 
>
> 2)  i see budget in adwords interface, but i have guest (not manager) 
> account. How get budget by  API  via budgetOrderService?
> The BudgetOrderService is a whitelisted service, so you would have to 
> have a manager account set up with consolidated billing. There are more 
> details about how all of this works in our Budget Order Service guide 
> . 
> It sounds like in your case that you're not set up for that.
>
> 3) it would be logical,  if i can see budget in interface (from 
> browser) , then I should be able to read it by api 
> You do have other options for getting information about your budget. 
> For example, you can use the Budget Performance Report 
> 

Re: How to get account budget

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I totally understand how sad that is. To implement this as a feature in the 
API would take a lot of work, which is why you have not seen any progress 
on this. We get a lot of feature requests, and we often have to choose the 
ones that are requested the most. It's helpful to hear from people like you 
to know that there are other people who would want this feature. 

I have never met anyone who parses the web interface. I have met people who 
download the invoices and parse that. Another things that some people do is 
that they look at the budget on the campaign and tell people how much 
budget remains on each of the campaigns instead of on the account. That is 
another possible solution.

Regards,
Nadine, AdWords API Team

On Thursday, April 5, 2018 at 2:17:41 AM UTC-4, kislo...@gmail.com wrote:
>
> Can I fine-tune how to send letters to the e-mail about the amount of the 
> remaining balance (budget)?
>
> среда, 4 апреля 2018 г., 17:13:55 UTC+3 пользователь Nadine Sundquist 
> (AdWords API Team) написал:
>>
>> Greetings!
>>
>> Thanks for taking the time to try that out. I'm sorry to hear that it 
>> didn't match exactly what you needed. I appreciate the screenshots. That's 
>> really helpful. In order to get what you're asking for, you would need the 
>> BudgetOrderService 
>> .
>>  
>> However, there's a catch. It's only supported in the API if you have 
>> consolidated billing set up. Otherwise, that information can't be retrieved 
>> through the API. I've already put in a feature request to make this 
>> supported for all other kinds of billing in the future because I think that 
>> would be helpful.There isn't a date as to when something like that would be 
>> available.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Wednesday, April 4, 2018 at 4:50:06 AM UTC-4, kisl...@gmail.com wrote:
>>>
>>> Hello, thanks for answer
>>>
>>> We tried to use the "Budget Performance Report", but this is not what we 
>>> need. This method returns the budget from the "Shared Budget"
>>>
>>> Url interface: 
>>> https://adwords.google.com/aw/sharedbudgets?ocid=254362058&__c=8977077242=0&__u=6415393025
>>> Screen: http://take.ms/yCCkQ
>>>
>>> But we have a task to receive a budget from the section "Billing & 
>>> payments" -> "Account budgets"
>>> Url: 
>>> https://adwords.google.com/aw/billing/budgets?ocid=254362058=433291332&__c=8977077242=0&__u=6415393025
>>> Screen: http://take.ms/BW4g9
>>>
>>> We want to get the "Budget ammount" field (104$ on screenshot)
>>>
>>> How can I get this field? 
>>>
>>> вторник, 13 февраля 2018 г., 1:55:36 UTC+3 пользователь Nadine Sundquist 
>>> (AdWords API Team) написал:

 Hello,

 Could you do me a huge favor in the future? When you notice that a 
 thread is much older, could you start a new thread and just reference the 
 old forum post with a link? That makes it much easier in case the 
 questions 
 are a little different. In your case, you do have a few different 
 questions. In order to save you a bit of time, I won't ask you to start a 
 new thread this time, but I'll just answer it here. 

 1) any news about this question?
 We took this question offline and worked with the user to determine if 
 they were qualified to use the BudgetOrderSerivce. In order to even be 
 considered, your whole account structure needs to be set up for 
 consolidated 
 billing . 

 2)  i see budget in adwords interface, but i have guest (not manager) 
 account. How get budget by  API  via budgetOrderService?
 The BudgetOrderService is a whitelisted service, so you would have to 
 have a manager account set up with consolidated billing. There are more 
 details about how all of this works in our Budget Order Service guide 
 . 
 It sounds like in your case that you're not set up for that.

 3) it would be logical,  if i can see budget in interface (from 
 browser) , then I should be able to read it by api 
 You do have other options for getting information about your budget. 
 For example, you can use the Budget Performance Report 
 
  to 
 retrieve most of the data that you see in the browser. 

 4)  maybe exist some other api methods to get budget or  something 
 similar  money  param, like money limit, etc?
 For your situation, I think the best place would be to look at 
 reporting 
 
  such 
 as the Budget Performance Report 
 .
  
 There are many 

Re: How to get account budget

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

Thanks for taking the time to try that out. I'm sorry to hear that it 
didn't match exactly what you needed. I appreciate the screenshots. That's 
really helpful. In order to get what you're asking for, you would need the 
BudgetOrderService 
.
 
However, there's a catch. It's only supported in the API if you have 
consolidated billing set up. Otherwise, that information can't be retrieved 
through the API. I've already put in a feature request to make this 
supported for all other kinds of billing in the future because I think that 
would be helpful.There isn't a date as to when something like that would be 
available.

Best,
Nadine, AdWords API Team

On Wednesday, April 4, 2018 at 4:50:06 AM UTC-4, kislo...@gmail.com wrote:
>
> Hello, thanks for answer
>
> We tried to use the "Budget Performance Report", but this is not what we 
> need. This method returns the budget from the "Shared Budget"
>
> Url interface: 
> https://adwords.google.com/aw/sharedbudgets?ocid=254362058&__c=8977077242=0&__u=6415393025
> Screen: http://take.ms/yCCkQ
>
> But we have a task to receive a budget from the section "Billing & 
> payments" -> "Account budgets"
> Url: 
> https://adwords.google.com/aw/billing/budgets?ocid=254362058=433291332&__c=8977077242=0&__u=6415393025
> Screen: http://take.ms/BW4g9
>
> We want to get the "Budget ammount" field (104$ on screenshot)
>
> How can I get this field? 
>
> вторник, 13 февраля 2018 г., 1:55:36 UTC+3 пользователь Nadine Sundquist 
> (AdWords API Team) написал:
>>
>> Hello,
>>
>> Could you do me a huge favor in the future? When you notice that a thread 
>> is much older, could you start a new thread and just reference the old 
>> forum post with a link? That makes it much easier in case the questions are 
>> a little different. In your case, you do have a few different questions. In 
>> order to save you a bit of time, I won't ask you to start a new thread this 
>> time, but I'll just answer it here. 
>>
>> 1) any news about this question?
>> We took this question offline and worked with the user to determine if 
>> they were qualified to use the BudgetOrderSerivce. In order to even be 
>> considered, your whole account structure needs to be set up for consolidated 
>> billing . 
>>
>> 2)  i see budget in adwords interface, but i have guest (not manager) 
>> account. How get budget by  API  via budgetOrderService?
>> The BudgetOrderService is a whitelisted service, so you would have to 
>> have a manager account set up with consolidated billing. There are more 
>> details about how all of this works in our Budget Order Service guide 
>> . It 
>> sounds like in your case that you're not set up for that.
>>
>> 3) it would be logical,  if i can see budget in interface (from browser) 
>> , then I should be able to read it by api 
>> You do have other options for getting information about your budget. For 
>> example, you can use the Budget Performance Report 
>> 
>>  to 
>> retrieve most of the data that you see in the browser. 
>>
>> 4)  maybe exist some other api methods to get budget or  something 
>> similar  money  param, like money limit, etc?
>> For your situation, I think the best place would be to look at reporting 
>> 
>>  such 
>> as the Budget Performance Report 
>> .
>>  
>> There are many different kinds of reports 
>>  that 
>> can link that to where your budget is being used.
>>
>> Please give that a try to see if that works for you.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Monday, February 12, 2018 at 3:01:31 PM UTC-5, kisl...@gmail.com 
>> wrote:
>>>
>>> UP
>>>
>>> 1) any news about this question?
>>>
>>> 2)  i see budget in adwords interface, but i have guest (not manager) 
>>> account. How get budget by  API  via budgetOrderService?
>>>
>>> 3) it would be logical,  if i can see budget in interface (from browser) 
>>> , then I should be able to read it by api 
>>>
>>> 4)  maybe exist some other api methods to get budget or  something 
>>> similar  money  param, like money limit, etc?
>>>
>>> четверг, 19 января 2017 г., 6:35:33 UTC+3 пользователь 泉正太 написал:

 Hello,

 Thank you for your reply. Then, I would like to try applying for a 
 whitelist. 
 Sorry... where can I check how to apply for a 
 budgetOrderService whitelist?
 If there is a way please tell me the link of the document.

 Best regards,
 shorta izumi

 2017年1月19日木曜日 4時13分54秒 UTC+9 Vishal Vinayak (Adwords API 

Re: Strategies for programmatically dealing with API deprecation

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Isaiah,

You're totally right that a feed makes sense. On the right-hand side of our 
blog , we have links to feeds and 
email subscriptions. It links off to FeedBurner 
 that has various options to 
link in. You can also subscribe to AdWords API Announcements 
 to get 
emails. We also publish the sunset schedule way ahead of time on our sunsets 
page . We just 
sent a reminder ahead time in case people forgot about it. I hope that 
helps!

Cheers,
Nadine, AdWords API Team 

On Monday, April 2, 2018 at 10:11:16 AM UTC-4, Isaiah Schultz wrote:
>
> I totally understand that migration between versions would still be a 
> manual process. That makes sense to me, and I would expect nothing else.
>
> But what seems odd is that there's no solution available in the spirit of 
> "fail early" and automation.
>
> Is there no one in a continuous integration/delivery environment that is 
> using an adwords library? How difficult would it be to add something 
> similar to what i mentioned in my initial question?
>
> On Monday, April 2, 2018 at 12:25:04 AM UTC-5, Peter Oliquino wrote:
>>
>> Hi Isaiah,
>>
>> I'm afraid that only this link 
>>  and our 
>> blog  are 
>> the only resources wherein you can check for announcements regarding each 
>> version's deprecation schedule. As for migrating, there is no alternative 
>> yet to have done it automatically. Migrations are currently done manually.
>>
>> Best regards,
>> Peter
>> 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+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.
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/d97940f5-bb8b-468c-a0b8-36372e61cf1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error with symfony in the PHP API

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Everyone,

Can you please file an issue on the library's GitHub page 
? That way the 
client library owners can take a look. I know they could figure this one 
out a lot faster than we could over here.

Thanks,
Nadine, AdWords API Team

On Wednesday, March 14, 2018 at 12:57:13 PM UTC-4, P Anand wrote:
>
>
> Hello,
> I am getting the same error. I have tried this on PHP v. 5.6.32 and PHP v. 
> 7.2 and still getting the same error. The googleads/googleads-php-lib 
> libaray works fine up to v201710, the moment i upgrade it ti v201802 it 
> crashes. Can you please help ?
>
> Thanks
> Pete
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/8e9de3db-71ed-4357-8962-33f44804c9de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Hans,

I just did a quick check-in on the internal thread I have going. I haven't 
gotten a reply yet, so I've bumped that thread. 

Regards,
Nadine, AdWords API Team

On Tuesday, February 13, 2018 at 4:50:54 PM UTC-5, HK wrote:
>
> Hi, Nadine
>
> Any feedback on my impression question above about the Display Network? 
> Would like to get all this sorted about before I change our production 
> code. This needs to be right.
>
> Thanks,
> Hans
>
> On Wednesday, February 7, 2018 at 1:56:26 PM UTC-8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Hans,
>>
>> I would feel the exact same way; I appreciate you being so kind through 
>> this process. I'll check on that for you because off the top of my head, 
>> I'm not sure about that. This is really helpful because I want to make sure 
>> that we have all the edge cases and caveats covered as I'm updating 
>> documentation. 
>>
>> Thanks again,
>> Nadine, AdWords API Team
>>
>> On Wednesday, February 7, 2018 at 3:47:52 PM UTC-5, HK wrote:
>>>
>>> Hi, Nadine
>>>
>>> Thanks for getting to the bottom of this. For the record, our concern 
>>> has primarily been that our system has been without PLA impressions for 3 
>>> months which is pretty bad, especially having this occur during the busiest 
>>> time of the year. We can update our system to work with the new behavior, 
>>> the important thing is that we know this behavior will stick around and not 
>>> be reverted as it requires quite a bit of work on our side to change it. 
>>> The main reason we were using impressions from the headline row in the 
>>> report was to avoid double-counting impressions for sitelinks. Please note 
>>> that we are still seeing the headline row come back with impressions for 
>>> shopping ads for the Display Networks. We only have around 10 impressions 
>>> in 3 months for this scenario, but it makes me wonder if you missed a spot 
>>> when you converted over? Here is an example:
>>>
>>> >> keywordID="384772557517" campaignID="228801421" avgPosition="1.0" 
>>> impressions="2" clicks="0" cost="0" day="2018-02-06" network="*Display 
>>> Network*" clickType="*Headline*" device="Mobile devices with full 
>>> browsers" />
>>>
>>> Please let us know when this change has been documented and whether PLAs 
>>> on the Display Network will continue to report impressions on the headline 
>>> row.
>>>
>>> Thanks,
>>> Hans
>>>
>>> On Monday, February 5, 2018 at 2:09:55 PM UTC-8, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello AdWordsians,

 There was another issue on this thread where the AdType was coming 
 back empty. That also should be resolved at this time. Please get back to 
 me if you see more issues.

 Cheers,
 Nadine, AdWords API Team

 On Monday, February 5, 2018 at 5:08:08 PM UTC-5, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hi Hans,
>
> Oh, my goodness. Time really does fly. I can't believe we are already 
> in February. 
>
> I think I've gotten to the bottom of this. At one point, the stats 
> were being reported under the *Headline* ClickType for shopping ads 
> because that's how the old shopping ads worked. When we moved to the new 
> shopping ads with more updated features, some of the new shopping ads 
> would 
> still report that old way. On that day where you saw it go to zero, we 
> changed it where we correctly moved all the stats to go into the more 
> specific category of *Shopping Ad - ...*. So, you haven't lost your 
> stats. They just moved into more specific categories as we were doing a 
> bit 
> of housekeeping. I'm working on updating some of our documentation to get 
> that confusion sorted out.
>
> If there's a specific use case in mind where you needed this, please 
> tell me. The good news is that your stats are reporting correctly, and 
> you 
> haven't lost anything. I think that's where your concern was. Your 
> accounts 
> have just been updated to report to more specific categories rather than 
> just a generic *Headline, *as it appears we will be retiring this for 
> specifically these shopping ads. 
>
> Best,
> Nadine, AdWords API Team
>
> On Monday, February 5, 2018 at 4:35:20 AM UTC-5, 
> emar...@commercehub.com wrote:
>>
>> Hi Nadine-
>> Any further updates here? It's been another week and a half. We 
>> really have to get this fixed.
>>
>> On Wednesday, January 24, 2018 at 12:13:25 PM UTC-8, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hello Hans,
>>>
>>> Thanks for checking in. I can feel your frustration. I've escalated 
>>> the issue internally as high as I can. I'm also trying on a couple of 
>>> other 
>>> avenues internally to see if we can get this resolved. I'll get back to 
>>> you 
>>> when I've seen some movement. In the meantime, please feel free to ping 

Re: How to get account budget

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

Could you do me a huge favor in the future? When you notice that a thread 
is much older, could you start a new thread and just reference the old 
forum post with a link? That makes it much easier in case the questions are 
a little different. In your case, you do have a few different questions. In 
order to save you a bit of time, I won't ask you to start a new thread this 
time, but I'll just answer it here. 

1) any news about this question?
We took this question offline and worked with the user to determine if they 
were qualified to use the BudgetOrderSerivce. In order to even be 
considered, your whole account structure needs to be set up for consolidated 
billing . 

2)  i see budget in adwords interface, but i have guest (not manager) 
account. How get budget by  API  via budgetOrderService?
The BudgetOrderService is a whitelisted service, so you would have to have 
a manager account set up with consolidated billing. There are more details 
about how all of this works in our Budget Order Service guide 
. It 
sounds like in your case that you're not set up for that.

3) it would be logical,  if i can see budget in interface (from browser) , 
then I should be able to read it by api 
You do have other options for getting information about your budget. For 
example, you can use the Budget Performance Report 

 to 
retrieve most of the data that you see in the browser. 

4)  maybe exist some other api methods to get budget or  something similar  
money  param, like money limit, etc?
For your situation, I think the best place would be to look at reporting 
 
such 
as the Budget Performance Report 
.
 
There are many different kinds of reports 
 that can 
link that to where your budget is being used.

Please give that a try to see if that works for you.

Best,
Nadine, AdWords API Team

On Monday, February 12, 2018 at 3:01:31 PM UTC-5, kislo...@gmail.com wrote:
>
> UP
>
> 1) any news about this question?
>
> 2)  i see budget in adwords interface, but i have guest (not manager) 
> account. How get budget by  API  via budgetOrderService?
>
> 3) it would be logical,  if i can see budget in interface (from browser) , 
> then I should be able to read it by api 
>
> 4)  maybe exist some other api methods to get budget or  something 
> similar  money  param, like money limit, etc?
>
> четверг, 19 января 2017 г., 6:35:33 UTC+3 пользователь 泉正太 написал:
>>
>> Hello,
>>
>> Thank you for your reply. Then, I would like to try applying for a 
>> whitelist. 
>> Sorry... where can I check how to apply for a 
>> budgetOrderService whitelist?
>> If there is a way please tell me the link of the document.
>>
>> Best regards,
>> shorta izumi
>>
>> 2017年1月19日木曜日 4時13分54秒 UTC+9 Vishal Vinayak (Adwords API Team):
>>>
>>> Hi,
>>>
>>> From AdWords API standpoint, you can use BudgetOrderService 
>>> 
>>>  to 
>>> retrieve budgets for an account. A BudgetOrder 
>>> 
>>>  is 
>>> an authorization for a particular client AdWords account to spend a certain 
>>> amount of money over a certain period of time. The 
>>> BudgetOrderService.get 
>>> 
>>>  method 
>>> can be used to fetch the spendingLimit 
>>> 
>>>  of 
>>> the client account. Please note that BudgetOrderService is available only 
>>> to white-listed AdWords manager accounts.  
>>>
>>> For questions related to AdWords Scripts, I would recommend posting your 
>>> queries on the AdWords Scripts Forum 
>>> . 
>>>
>>> Regards,
>>> Vishal, 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+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 

Re: Unable to delete ProductPartitions (PRODUCT_PARTITION_DOES_NOT_EXIST)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Christian,

Thanks for providing all those details. That really helped me figure out 
what's going on. I'm just following up on the forum, so anyone else who 
bumps into this in the future can be helped out as well. I noticed in your 
logs that the first removes were happening just fine and later it became 
more frequent. So, I looked at the path of your tree that was being 
removed. What was happening is that you were trying to remove a leaf node 
after you had already removed a higher node in the tree earlier in the same 
request. That's why the errors were happening. It was telling you that you 
had already removed an item further up in the tree, so the item you were 
trying to remove now no longer existed. Here's an example. Let's say you 
have:

1234   * / product type = "haus & garten" / product type = 
"heimtextilien" / product type = "frottierwaren" / product type = 
"duschtuch" / brand = "vossen" /
5678   * / product type = "haus & garten" / product type = 
"heimtextilien" / product type = "frottierwaren" / product type = 
"duschtuch" / brand = "vossen" / item id = *

You remove the first one 1234. Then, you try to remove the second one 5678. 
The second one would error because the the first remove call would have 
wiped out the second one already. Trees are a tricky business. Many of our 
client libraries have utilities 

 to 
handle these trees because of odd situations like this one.

Cheers,
Nadine, AdWords API Team

On Wednesday, February 7, 2018 at 1:00:38 PM UTC-5, Sreelakshmi Sasidharan 
(AdWords API Team) wrote:
>
> Hi Christian, 
>
> What you have explained is the correct approach to identify the product 
> partition. To take a closer look at the issue, could you please enable 
> logging and share the SOAP request and response logs? You can use reply 
> privately to author while sharing the details. 
>
> Thanks,
> Sreelakshmi, 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+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.
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/53558156-c20a-4931-8e7c-d7ceef0dd584%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Hans,

I would feel the exact same way; I appreciate you being so kind through 
this process. I'll check on that for you because off the top of my head, 
I'm not sure about that. This is really helpful because I want to make sure 
that we have all the edge cases and caveats covered as I'm updating 
documentation. 

Thanks again,
Nadine, AdWords API Team

On Wednesday, February 7, 2018 at 3:47:52 PM UTC-5, HK wrote:
>
> Hi, Nadine
>
> Thanks for getting to the bottom of this. For the record, our concern has 
> primarily been that our system has been without PLA impressions for 3 
> months which is pretty bad, especially having this occur during the busiest 
> time of the year. We can update our system to work with the new behavior, 
> the important thing is that we know this behavior will stick around and not 
> be reverted as it requires quite a bit of work on our side to change it. 
> The main reason we were using impressions from the headline row in the 
> report was to avoid double-counting impressions for sitelinks. Please note 
> that we are still seeing the headline row come back with impressions for 
> shopping ads for the Display Networks. We only have around 10 impressions 
> in 3 months for this scenario, but it makes me wonder if you missed a spot 
> when you converted over? Here is an example:
>
>  campaignID="228801421" avgPosition="1.0" impressions="2" clicks="0" 
> cost="0" day="2018-02-06" network="*Display Network*" clickType="
> *Headline*" device="Mobile devices with full browsers" />
>
> Please let us know when this change has been documented and whether PLAs 
> on the Display Network will continue to report impressions on the headline 
> row.
>
> Thanks,
> Hans
>
> On Monday, February 5, 2018 at 2:09:55 PM UTC-8, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello AdWordsians,
>>
>> There was another issue on this thread where the AdType was coming back 
>> empty. That also should be resolved at this time. Please get back to me if 
>> you see more issues.
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Monday, February 5, 2018 at 5:08:08 PM UTC-5, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hi Hans,
>>>
>>> Oh, my goodness. Time really does fly. I can't believe we are already in 
>>> February. 
>>>
>>> I think I've gotten to the bottom of this. At one point, the stats were 
>>> being reported under the *Headline* ClickType for shopping ads because 
>>> that's how the old shopping ads worked. When we moved to the new shopping 
>>> ads with more updated features, some of the new shopping ads would still 
>>> report that old way. On that day where you saw it go to zero, we changed it 
>>> where we correctly moved all the stats to go into the more specific 
>>> category of *Shopping Ad - ...*. So, you haven't lost your stats. They 
>>> just moved into more specific categories as we were doing a bit of 
>>> housekeeping. I'm working on updating some of our documentation to get that 
>>> confusion sorted out.
>>>
>>> If there's a specific use case in mind where you needed this, please 
>>> tell me. The good news is that your stats are reporting correctly, and you 
>>> haven't lost anything. I think that's where your concern was. Your accounts 
>>> have just been updated to report to more specific categories rather than 
>>> just a generic *Headline, *as it appears we will be retiring this for 
>>> specifically these shopping ads. 
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Monday, February 5, 2018 at 4:35:20 AM UTC-5, emar...@commercehub.com 
>>> wrote:

 Hi Nadine-
 Any further updates here? It's been another week and a half. We really 
 have to get this fixed.

 On Wednesday, January 24, 2018 at 12:13:25 PM UTC-8, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hello Hans,
>
> Thanks for checking in. I can feel your frustration. I've escalated 
> the issue internally as high as I can. I'm also trying on a couple of 
> other 
> avenues internally to see if we can get this resolved. I'll get back to 
> you 
> when I've seen some movement. In the meantime, please feel free to ping 
> this thread if you don't hear back soon. 
>
> Thanks,
> Nadine, AdWords API Team
>
> On Wednesday, January 24, 2018 at 11:42:45 AM UTC-5, HK wrote:
>>
>> Hi, Nadine
>>
>> This issue is becoming more and more urgent. Nothing personal, but I 
>> find it very surprising that no one can explain what is going on after 
>> 20 
>> days. The AdWords APIs is not just a tool we are using for fun, we have 
>> an 
>> enterprise solution built around it and it's affecting around 30 
>> important 
>> customers of ours and ~20 million impressions per days. Please let us 
>> know 
>> how we can get some traction on this now over 2 month old problem.
>>
>> Thanks for all your help,
>> Hans
>>
>> On Tuesday, January 16, 2018 at 2:10:23 

Re: Cannot get all managed customers with java library: 在文件元素內容中找到無效的 XML 字元 (Unicode: 0x8)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi,

Thank you for getting in contact with me. I was of the understanding that 
this was more of an occasional issue, and that it didn't happen that often. 
Now that you're reaching out again, I can see that it is a bit more 
serious. There currently is no timeline for this. However, since you've 
raised this as a concern that continues to be a problem, I have raised the 
issue's priority. May I ask how often this issue happens? Is it something 
that happens every day, or is it something that happens once a week? The 
reason I ask is because I ran a query on our logs over the last couple of 
weeks, and I haven't seen it happening, so I'm wondering if I may be 
missing it. If you do have a recent example of it, please send me the 
*requestId* of an example request that recently failed. If you don't have 
the *requestId*, then an example of the request like you did before will 
work as well.

Thanks,
Nadine, AdWords API Team

On Wednesday, February 7, 2018 at 4:04:29 AM UTC-5, w...@urad.com.tw wrote:
>
> Hi Nadine Sundquist,
>
> I'm curious that is there any update about this issue? We encountered this 
> issue again and again...
> Does AdWords API Team have any schedule for solving this issue? (Our 
> manager has been caring about this issue for a while, and we are asked to 
> propose some alternative solutions for this...)
> Thanks for your reading.
>
>
>
> Nadine Sundquist (AdWords API Team)於 2017年9月27日星期三 UTC+8上午12時11分28秒寫道：
>>
>> Hello,
>>
>> I found the issue, and it's a tricky one. The good thing is that the 
>> request you are making to the API is successful, so there is nothing wrong 
>> with your request. The issue is what is being returned. You are 
>> successfully getting a response. However, that response has hidden 
>> characters in it. When Java tries to parse it, it considers those hidden 
>> characters as invalid XML characters, and that is where you are getting the 
>> errors. I found one of the reasons, but there may be more than one reason. 
>> I'll send you the account with the hidden character issue in a separate, 
>> private email. I just wanted to make sure that people reading the forum in 
>> the future know to look for hidden characters when this happens.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Monday, September 25, 2017 at 11:46:07 PM UTC-4, 郭文豪 wrote:
>>>
>>> Request
>>> 
>>>
>>>
>>> 11:21:04.739 [main] INFO 
>>> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger - 
>>> SOAP request:
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd="
>>> http://www.w3.org/2001/XMLSchema; xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance;>
>>> 
>>> https://adwords.google.com/api/adwords/mcm/v201708; 
>>> soapenv:mustUnderstand="0">
>>> https://adwords.google.com/api/adwords/cm/v201708
>>> ">client-customer-id
>>> https://adwords.google.com/api/adwords/cm/v201708
>>> ">REDACTED
>>> https://adwords.google.com/api/adwords/cm/v201708;>unknown (AwApi-Java, 
>>> AdWords-Axis/3.8.0, Common-Java/3.8.0, Axis/1.4, Java/1.8.0_101, maven, 
>>> SelectorBuilder)
>>> https://adwords.google.com/api/adwords/cm/v201708
>>> ">false
>>> https://adwords.google.com/api/adwords/cm/v201708
>>> ">false
>>> 
>>> 
>>> 
>>> https://adwords.google.com/api/adwords/mcm/v201708;>
>>> 
>>> https://adwords.google.com/api/adwords/cm/v201708
>>> ">CustomerId
>>> https://adwords.google.com/api/adwords/cm/v201708;>Name
>>> https://adwords.google.com/api/adwords/cm/v201708;>
>>> 1040
>>> 20
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> Response
>>> 
>>>
>>> 11:21:04.739 [main] INFO 
>>> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger - 
>>> SOAP response:
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd="
>>> http://www.w3.org/2001/XMLSchema; xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance;>
>>> 
>>> 
>>> soapenv:Server.userException
>>> org.xml.sax.SAXParseException; lineNumber: 1; 
>>> columnNumber: 816; 在文件元素內容中找到無效的 XML 字元 (Unicode: 0x8)。
>>> 
>>> >> xmlns:ns1="http://xml.apache.org/axis/;>org.xml.sax.SAXParseException; 
>>> lineNumber: 1; columnNumber: 816; 在文件元素內容中找到無效的 XML 字元 (Unicode: 0x8)。
>>> at 
>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
>>> at 
>>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
>>> at 
>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
>>> at 
>>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
>>> at 
>>> 

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello AdWordsians,

There was another issue on this thread where the AdType was coming back 
empty. That also should be resolved at this time. Please get back to me if 
you see more issues.

Cheers,
Nadine, AdWords API Team

On Monday, February 5, 2018 at 5:08:08 PM UTC-5, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hi Hans,
>
> Oh, my goodness. Time really does fly. I can't believe we are already in 
> February. 
>
> I think I've gotten to the bottom of this. At one point, the stats were 
> being reported under the *Headline* ClickType for shopping ads because 
> that's how the old shopping ads worked. When we moved to the new shopping 
> ads with more updated features, some of the new shopping ads would still 
> report that old way. On that day where you saw it go to zero, we changed it 
> where we correctly moved all the stats to go into the more specific 
> category of *Shopping Ad - ...*. So, you haven't lost your stats. They 
> just moved into more specific categories as we were doing a bit of 
> housekeeping. I'm working on updating some of our documentation to get that 
> confusion sorted out.
>
> If there's a specific use case in mind where you needed this, please tell 
> me. The good news is that your stats are reporting correctly, and you 
> haven't lost anything. I think that's where your concern was. Your accounts 
> have just been updated to report to more specific categories rather than 
> just a generic *Headline, *as it appears we will be retiring this for 
> specifically these shopping ads. 
>
> Best,
> Nadine, AdWords API Team
>
> On Monday, February 5, 2018 at 4:35:20 AM UTC-5, emars...@commercehub.com 
> wrote:
>>
>> Hi Nadine-
>> Any further updates here? It's been another week and a half. We really 
>> have to get this fixed.
>>
>> On Wednesday, January 24, 2018 at 12:13:25 PM UTC-8, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hello Hans,
>>>
>>> Thanks for checking in. I can feel your frustration. I've escalated the 
>>> issue internally as high as I can. I'm also trying on a couple of other 
>>> avenues internally to see if we can get this resolved. I'll get back to you 
>>> when I've seen some movement. In the meantime, please feel free to ping 
>>> this thread if you don't hear back soon. 
>>>
>>> Thanks,
>>> Nadine, AdWords API Team
>>>
>>> On Wednesday, January 24, 2018 at 11:42:45 AM UTC-5, HK wrote:

 Hi, Nadine

 This issue is becoming more and more urgent. Nothing personal, but I 
 find it very surprising that no one can explain what is going on after 20 
 days. The AdWords APIs is not just a tool we are using for fun, we have an 
 enterprise solution built around it and it's affecting around 30 important 
 customers of ours and ~20 million impressions per days. Please let us know 
 how we can get some traction on this now over 2 month old problem.

 Thanks for all your help,
 Hans

 On Tuesday, January 16, 2018 at 2:10:23 PM UTC-8, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hello Hans,
>
> No worries! It gets pretty busy around here, so it's fine to bump a 
> thread. It's good to know the scale of how it's affecting you. I'm 
> checking 
> in on the internal thread I have going for this. Hopefully, we'll have an 
> answer soon. This does seem to be an odd one.
>
> Regards,
> Nadine, AdWords API Team
>
> On Tuesday, January 16, 2018 at 2:16:50 PM UTC-5, HK wrote:
>>
>> Hi, Nadina
>>
>> Hate nag you about this, but is there any way to escalate this? It's 
>> a pretty big unexplained/undocumented change that is affecting ~30 
>> merchant 
>> accounts we manage.
>>
>> Hans
>>
>> On Wednesday, January 10, 2018 at 12:00:23 PM UTC-8, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hello Hans,
>>>
>>> At this point, I'm not sure why that's happening. We're still 
>>> investigating. I'll get back to you when we have more information. I'm 
>>> glad 
>>> you brought it to light with your analysis.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Wednesday, January 10, 2018 at 12:54:31 PM UTC-5, HK wrote:

 Hi, Nadine

 As for issue 2, any indication as to what is going on? This is 
 having a pretty big impact on a number of large accounts we manage and 
 has 
 been occurring for two months soon. Appreciate your help!

 Hans

 On Monday, January 8, 2018 at 9:42:13 AM UTC-8, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hello Everyone,
>
> I would like to follow up publicly on the thread since I have 
> multiple threads going on privately in case someone bumps into this. 
> There 
> are two issues that are happening on this thread:
>
>- *Issue 1: *The AdType 
>

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Hans,

Oh, my goodness. Time really does fly. I can't believe we are already in 
February. 

I think I've gotten to the bottom of this. At one point, the stats were 
being reported under the *Headline* ClickType for shopping ads because 
that's how the old shopping ads worked. When we moved to the new shopping 
ads with more updated features, some of the new shopping ads would still 
report that old way. On that day where you saw it go to zero, we changed it 
where we correctly moved all the stats to go into the more specific 
category of *Shopping Ad - ...*. So, you haven't lost your stats. They just 
moved into more specific categories as we were doing a bit of housekeeping. 
I'm working on updating some of our documentation to get that confusion 
sorted out.

If there's a specific use case in mind where you needed this, please tell 
me. The good news is that your stats are reporting correctly, and you 
haven't lost anything. I think that's where your concern was. Your accounts 
have just been updated to report to more specific categories rather than 
just a generic *Headline, *as it appears we will be retiring this for 
specifically these shopping ads. 

Best,
Nadine, AdWords API Team

On Monday, February 5, 2018 at 4:35:20 AM UTC-5, emars...@commercehub.com 
wrote:
>
> Hi Nadine-
> Any further updates here? It's been another week and a half. We really 
> have to get this fixed.
>
> On Wednesday, January 24, 2018 at 12:13:25 PM UTC-8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Hans,
>>
>> Thanks for checking in. I can feel your frustration. I've escalated the 
>> issue internally as high as I can. I'm also trying on a couple of other 
>> avenues internally to see if we can get this resolved. I'll get back to you 
>> when I've seen some movement. In the meantime, please feel free to ping 
>> this thread if you don't hear back soon. 
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Wednesday, January 24, 2018 at 11:42:45 AM UTC-5, HK wrote:
>>>
>>> Hi, Nadine
>>>
>>> This issue is becoming more and more urgent. Nothing personal, but I 
>>> find it very surprising that no one can explain what is going on after 20 
>>> days. The AdWords APIs is not just a tool we are using for fun, we have an 
>>> enterprise solution built around it and it's affecting around 30 important 
>>> customers of ours and ~20 million impressions per days. Please let us know 
>>> how we can get some traction on this now over 2 month old problem.
>>>
>>> Thanks for all your help,
>>> Hans
>>>
>>> On Tuesday, January 16, 2018 at 2:10:23 PM UTC-8, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Hans,

 No worries! It gets pretty busy around here, so it's fine to bump a 
 thread. It's good to know the scale of how it's affecting you. I'm 
 checking 
 in on the internal thread I have going for this. Hopefully, we'll have an 
 answer soon. This does seem to be an odd one.

 Regards,
 Nadine, AdWords API Team

 On Tuesday, January 16, 2018 at 2:16:50 PM UTC-5, HK wrote:
>
> Hi, Nadina
>
> Hate nag you about this, but is there any way to escalate this? It's a 
> pretty big unexplained/undocumented change that is affecting ~30 merchant 
> accounts we manage.
>
> Hans
>
> On Wednesday, January 10, 2018 at 12:00:23 PM UTC-8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Hans,
>>
>> At this point, I'm not sure why that's happening. We're still 
>> investigating. I'll get back to you when we have more information. I'm 
>> glad 
>> you brought it to light with your analysis.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Wednesday, January 10, 2018 at 12:54:31 PM UTC-5, HK wrote:
>>>
>>> Hi, Nadine
>>>
>>> As for issue 2, any indication as to what is going on? This is 
>>> having a pretty big impact on a number of large accounts we manage and 
>>> has 
>>> been occurring for two months soon. Appreciate your help!
>>>
>>> Hans
>>>
>>> On Monday, January 8, 2018 at 9:42:13 AM UTC-8, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Everyone,

 I would like to follow up publicly on the thread since I have 
 multiple threads going on privately in case someone bumps into this. 
 There 
 are two issues that are happening on this thread:

- *Issue 1: *The AdType 

 
  
is at times coming back empty. There are some ad types that are 
 only 
available in the UI and are not yet supported in the API. That is 
 the case 
here with some of these Gmail ads. In this case, the proper 
 response should 
be *UNKNOWN* rather than an empty response as AdType. I've 

Re: Some keywords get no results from TargetingIdeaService

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings AdWordsians,

I have wonderful news! Things should now be working as expected where the 
results from the UI should now match the results from the API. If you 
experience any more issue with this, please get back to me.

Thanks,
Nadine, AdWords API Team

On Thursday, January 11, 2018 at 9:37:17 AM UTC-5, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello AdWordsians,
>
> My apologies for not posting back here on the progress. This is a general 
> ongoing issue where there are words or phrases that are returning stats in 
> the UI, but not through the API. There appears to be a stricter filter that 
> causes certain phrases to not show up in the API. I am actively working 
> with the rest of my team in trying to find the exact source of the issue 
> that is causing this. I'll post back here when we have more information. 
>
> Regards,
> Nadine, AdWords API Team
>
> On Thursday, January 11, 2018 at 2:41:51 AM UTC-5, Aviv Oron wrote:
>>
>> Nope :(
>> Im still waiting for an update from adwords API team, i was told the 
>> issue was passed to engineering...
>>
>> On Thursday, January 11, 2018 at 12:55:25 AM UTC+2, Andres Tobar wrote:
>>>
>>> Hi Aviv,
>>>
>>> Were you able to get this issue resolved? I'm having the same exact 
>>> issue with my setup at the moment.
>>>
>>> Thanks,
>>> Andres
>>>
>>> On Thursday, December 28, 2017 at 12:32:19 PM UTC-5, Aviv Oron wrote:

 Hey, 

 Im trying to get keyword stats data using TargetingIdeaService.
 For some keywords, the response is empty! (totalNumEntries=0)
 For example, for the keyword "bullfight" ill get an empty page, and for 
 keyword "catfight" ill get proper results.
 Those keywords I'm failing to get results for, DO have data when I'm 
 querying the web client!

 This is how i build the selector:

 selector = {
 'searchParameters': [
 {
 'xsi_type': 'RelatedToQuerySearchParameter',
 'queries': ['bullfight']
 },
 {
 'xsi_type': 'NetworkSearchParameter',
 'networkSetting': {
 'targetGoogleSearch': True,
 'targetSearchNetwork': False,
 'targetContentNetwork': False,
 'targetPartnerSearchNetwork': False
 }
 }
 ],
 'ideaType': 'KEYWORD',
 'requestType': 'STATS',
 'requestedAttributeTypes': [
 'COMPETITION', 'AVERAGE_CPC', 'KEYWORD_TEXT', 'SEARCH_VOLUME'
 ],
 'paging': {
 'startIndex': '0',
 'numberResults': '100'
 }
 }



 Hope someone can help with this issue :)
 Thanks!
 Aviv

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/6cac3475-e1af-4ae2-abdc-51cd6ea93d67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: error code : UNEXPECTED_INTERNAL_API_ERROR

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I've tried running your same request against your account with my code, and 
everything seems to work fine, so I'm wondering if there's something in 
your header that may be causing this. I've been able to narrow down what 
may be causing this, but it's not clear at this point what the root cause 
may be. Thanks for providing the request ID as I was at least able to pull 
the stack trace to get this investigation started. I'm pulling in someone 
else to also take a look. I'll get back to you when we have more 
information.

Best,
Nadine, AdWords API Team

On Wednesday, January 24, 2018 at 11:45:52 PM UTC-5, vii step wrote:
>
> Hi  Milind Sankeshware (AdWords API Team)
> *   I had try two days. It still the same error. Can you please check : 
> *000563926dc623310a623d8301086ee5 
> .
>
> Thanks
> vii step
>
> On Wednesday, January 24, 2018 at 5:15:43 PM UTC+8, vii step wrote:
>>
>>  I recevied the error code : UNEXPECTED_INTERNAL_API_ERROR , when I 
>> request API : CampaignServiceInterface.
>>
>> SOAP data like :
>>
>> [24 一月 2018 16:55:04,065-soapXmlLogger:INFO:main] SOAP request:
>> 
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd="
>> http://www.w3.org/2001/XMLSchema; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance;>
>> 
>> https://adwords.google.com/api/adwords/cm/v201710
>> " soapenv:mustUnderstand="0">
>> 916-654-2244
>> REDACTED
>>
>> unknown (AwApi-Java, AdWords-Axis/3.10.0, 
>> Common-Java/3.10.0, Axis/1.4, Java/1.7.0_71, maven, SelectorBuilder, 
>> SelectorField)
>> false
>> false
>> 
>> 
>> 
>> https://adwords.google.com/api/adwords/cm/v201710;>
>> 
>> Id
>> Name
>> 
>> Name
>> ASCENDING
>> 
>> 
>> 0
>> 100
>> 
>> 
>> 
>> 
>> 
>>
>> [24 一月 2018 16:55:04,066-soapXmlLogger:INFO:main] SOAP response:
>> 
>> http://schemas.xmlsoap.org/soap/envelope/;>
>> 
>> https://adwords.google.com/api/adwords/cm/v201710;>
>> 00056381d194eb500a62e40868091f9e
>> CampaignService
>> get
>> 1
>> 499
>> 
>> 
>> 
>> 
>> soap:Server
>>
>> [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.init(InternalApiErro]
>> 
>> https://adwords.google.com/api/adwords/cm/v201710;>
>>
>> [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR 
>> @ 
>> com.google.ads.api.services.common.error.InternalApiError.init(InternalApiErro]
>>
>> 
>> ApiException
>> http://www.w3.org/2001/XMLSchema-instance; xsi:type="InternalApiError">
>> 
>> 
>>
>> 
>> InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>> InternalApiError
>> UNEXPECTED_INTERNAL_API_ERROR
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> Exception in thread "main" AxisFault
>>  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
>>  faultSubcode: 
>>
>>  faultString: [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.init(InternalApiErro]
>>  faultActor: 
>>  faultNode: 
>>  faultDetail: 
>> {https://adwords.google.com/api/adwords/cm/v201710}ApiExceptionFault
>> :[InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.init(InternalApiErro]ApiException>  xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance
>> " 
>> xsi:type="InternalApiError">InternalApiError.UNEXPECTED_INTERNAL_API_ERRORInternalApiErrorUNEXPECTED_INTERNAL_API_ERROR
>>  
>>
>> I don`t have any idea for that.
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 

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

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

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

On Monday, January 22, 2018 at 10:28:10 PM UTC-5, Peter Oliquino wrote:
>
> 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.
>
> Thanks and regards,
> Peter
> 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+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.
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/50fc8423-4405-4a1d-b611-caf8d718bf28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Hans,

Thanks for checking in. I can feel your frustration. I've escalated the 
issue internally as high as I can. I'm also trying on a couple of other 
avenues internally to see if we can get this resolved. I'll get back to you 
when I've seen some movement. In the meantime, please feel free to ping 
this thread if you don't hear back soon. 

Thanks,
Nadine, AdWords API Team

On Wednesday, January 24, 2018 at 11:42:45 AM UTC-5, HK wrote:
>
> Hi, Nadine
>
> This issue is becoming more and more urgent. Nothing personal, but I find 
> it very surprising that no one can explain what is going on after 20 days. 
> The AdWords APIs is not just a tool we are using for fun, we have an 
> enterprise solution built around it and it's affecting around 30 important 
> customers of ours and ~20 million impressions per days. Please let us know 
> how we can get some traction on this now over 2 month old problem.
>
> Thanks for all your help,
> Hans
>
> On Tuesday, January 16, 2018 at 2:10:23 PM UTC-8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Hans,
>>
>> No worries! It gets pretty busy around here, so it's fine to bump a 
>> thread. It's good to know the scale of how it's affecting you. I'm checking 
>> in on the internal thread I have going for this. Hopefully, we'll have an 
>> answer soon. This does seem to be an odd one.
>>
>> Regards,
>> Nadine, AdWords API Team
>>
>> On Tuesday, January 16, 2018 at 2:16:50 PM UTC-5, HK wrote:
>>>
>>> Hi, Nadina
>>>
>>> Hate nag you about this, but is there any way to escalate this? It's a 
>>> pretty big unexplained/undocumented change that is affecting ~30 merchant 
>>> accounts we manage.
>>>
>>> Hans
>>>
>>> On Wednesday, January 10, 2018 at 12:00:23 PM UTC-8, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Hans,

 At this point, I'm not sure why that's happening. We're still 
 investigating. I'll get back to you when we have more information. I'm 
 glad 
 you brought it to light with your analysis.

 Best,
 Nadine, AdWords API Team

 On Wednesday, January 10, 2018 at 12:54:31 PM UTC-5, HK wrote:
>
> Hi, Nadine
>
> As for issue 2, any indication as to what is going on? This is having 
> a pretty big impact on a number of large accounts we manage and has been 
> occurring for two months soon. Appreciate your help!
>
> Hans
>
> On Monday, January 8, 2018 at 9:42:13 AM UTC-8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Everyone,
>>
>> I would like to follow up publicly on the thread since I have 
>> multiple threads going on privately in case someone bumps into this. 
>> There 
>> are two issues that are happening on this thread:
>>
>>- *Issue 1: *The AdType 
>>
>> 
>>  
>>is at times coming back empty. There are some ad types that are only 
>>available in the UI and are not yet supported in the API. That is the 
>> case 
>>here with some of these Gmail ads. In this case, the proper response 
>> should 
>>be *UNKNOWN* rather than an empty response as AdType. I've filed 
>>an issue for this, and I'll report back when the issue has been fixed.
>>- *Issue 2:* The secondary issues is that PLA ads have stopped 
>>showing *Headline* as a ClikType 
>>
>> 
>>  as 
>>of November 18th. I've seen that in a number of places, but I don't 
>> see an 
>>exact reason. I'm asking around about it now. I personally noticed 
>> that 
>>shopping ads did change recently (while I was doing my holiday 
>> shopping), 
>>and I'm wondering if that that's had an impact on how clicks are 
>> reported.
>>
>> I'll report back here when I hear more.
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Thursday, January 4, 2018 at 6:50:13 PM UTC-5, HK wrote:
>>>
>>> I have replied privately to Bharani with further details.
>>>
>>> On Thursday, January 4, 2018 at 12:30:53 PM UTC-8, Bharani Cherukuri 
>>> (AdWords API Team) wrote:

 Hello Hans, 

 We can definitely take a look at this issue. From what I 
 understand, you're experiencing a discrepancy with the clickType field 
 in 
 your Ad Performance Report. If that's the case, could you share us the 
 complete report definition 
 
  along 
 with the clientCustomerId, so I can take a look? Please use *Reply 
 privately to author* option to share the details. 

 Regards,
 Bharani, AdWords API Team

Re: BatchJob getting cancelled (Internal Error)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

I know it's been awhile, but I just wanted to touch base. We were able to 
find the root cause of your issue, and we put a number of fixes in place. 
If you're still experiencing issues, please get back to me.

Thanks,
Nadine, AdWords API Team

On Thursday, September 28, 2017 at 3:01:23 PM UTC-4, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello,
>
> I don't see anything obvious at first glance with your request. I'm 
> pulling someone in on my team to get a second set of eyes on this. I'll get 
> back to you when we figure out what's going on.
>
> Best,
> Nadine, AdWords API Team 
>
> On Thursday, September 28, 2017 at 5:39:05 AM UTC-4, 
> aanchal.khandel...@go-mmt.com wrote:
>>
>> All my batch jobs are failing. I have tried with mere 5k operations as 
>> well as some 11k operations. Every time the batch job gets cancelled 
>> stating BatchJobProcessingError.INTERNAL_ERROR. Batch job is 572804866. 
>>
>> Please help. 
>>
>> ::DISCLAIMER::
>>
>>
>> 
>>
>>
>> This message is intended only for the use of the addressee and may 
>> contain information that is privileged, confidential and exempt from 
>> disclosure under applicable law. If the reader of this message is not the 
>> intended recipient, or the employee or agent responsible for delivering the 
>> message to the intended recipient, you are hereby notified that any 
>> dissemination, distribution or copying of this communication is strictly 
>> prohibited. If you have received this e-mail in error, please notify us 
>> immediately by return e-mail and delete this e-mail and all attachments 
>> from your system.
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/2b524c19-de38-4ab6-8f56-6fb50a2c70ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BatchJobProcessingError.INTERNAL_ERROR and other batchjob issues

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Everyone,

I realize this is an older thread, but I wanted to make sure to close this 
out rather than leave it hanging for our readers. The issues that were 
causing this to happen should be fixed now. If you experience any further 
issues with this, please get back to me.

Thanks,
Nadine, AdWords API Team

On Wednesday, January 25, 2017 at 12:31:02 PM UTC-5, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hi Mario,
>
> Thanks for checking in! We're still working on it. I'm hoping to get back 
> to you soon on this.
>
> Best,
> Nadine, AdWords API Team
>
> On Wednesday, January 25, 2017 at 6:59:30 AM UTC-5, adshopit@gmail.com 
> wrote:
>>
>> Hi Nadine,
>>
>> any news on this?
>>
>> Thanks,
>> Mario
>>
>>
>> Il giorno venerdì 20 gennaio 2017 00:26:11 UTC+1, Nadine Sundquist 
>> (AdWords API Team) ha scritto:
>>>
>>> Hi Mario,
>>>
>>> We found the root cause of the issue. It is something on our side. 
>>> Please stop submitting jobs that are similar to the ones you are currently 
>>> submitting that are failing. We're actively working on a fix, and I'll 
>>> update you as soon as it is available.
>>>
>>> Thanks,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, January 19, 2017 at 6:08:23 PM UTC-5, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Mario,

 It'll take me a bit of time to dig into why this is happening. Thanks 
 for providing all this information. I'll get back to you as soon as I've 
 figured out what's going on.

 Cheers,
 Nadine, AdWords API Team

 On Thursday, January 19, 2017 at 3:08:52 PM UTC-5, adshop...@gmail.com 
 wrote:
>
> Hello,
>
> I keep getting the error: BatchJobProcessingError.INTERNAL_ERROR
> when sending sitelink/callout extensions.
> The batch job stays ACTIVE for a while (from a minute to up to twenty 
> minutes) and then becomes CANCELED with that processing error.
>
> Some example batch job IDs affected by this error: 436401237, 
>  436397916, 436229020.
>
>
> Also, recently, many (but not all) batch jobs take a long time to 
> finish (possibly related to another thread here 
> https://groups.google.com/forum/#!topic/adwords-api/Cigj68QDPM8)
>
> Regards,
> Mario
>


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/9f9c2fa6-9835-4739-9c18-b642a41a5d30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Victorian Postcodes not listed on the AdWords API Location Criteria 2017-11-02

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Kristian,

I've worked quite a bit with geo-locations, so I'm taking a look at this 
for you. I think I might have found the source of the confusion here. In 
our latest tables 
,
 
those postal codes exist, but not with the states that you have associated 
with them. Here's an example:

   - Your lookup failed for "2484,Queensland,Australia".
   - So, I decided to look up postal code 2484 in Australia in Google 
   Search. It turns out that postal code is located in New South Wales.
   - I took a look at our tables 
   
,
 
   and it is listed as "2484,New South Wales,Australia".

The good news is that the postal codes themselves aren't missing. The 
unfortunate news is that for all the postal codes that aren't working, the 
states associated with them that you are passing in don't match the postal 
code. Are these coming from one of Google's ads systems, or are they coming 
from somewhere else and need to be updated? If they are from one of 
Google's products, please get back to me, and we can figure out the next 
steps on how we can get that fixed. If not, then mystery solved, and you 
can hunt the culprit down elsewhere. 

Best,
Nadine, AdWords API Team

On Monday, January 22, 2018 at 9:03:57 PM UTC-5, Kristian Thompson wrote:
>
> Hi Luis,
>
> Those answers can be found by cross-referencing my attached spreadsheet 
> with your AdWords API Location Criteria 2017-11-02 
> 
>
> Thanks,
> Kristian
>
>
>
> On Monday, January 22, 2018 at 8:04:24 PM UTC+11, Luis Xander Talag 
> (AdWords API Team) wrote:
>>
>> Hi Kristian,
>>
>> Could you confirm if the location criteria you are referring to are the 
>> ones listed in our geo targeting spreadsheet 
>> ?
>>  
>> If yes, could you then provide the 134 postal codes which you said are not 
>> included in the list?
>>
>> Thanks and regards,
>> Luis
>> 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+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.
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/bacbec79-dfd4-44ff-8644-017807d4d344%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to get Tracking status, Repeat rate, Tracking event by using ConversionTrackerService ?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

That is my understanding as well. Thanks for putting it in such a clear way 
for people in the future.

Best,
Nadine, AdWords API Team

On Tuesday, January 23, 2018 at 1:13:29 AM UTC-5, cv wrote:
>
> Hi Nadine,
>
> Thanks for your reply.
>
> *On Adwords website, tracking status has  5 values, *
>
> *I am using ConversionTrackerService to get Conversion actions.*
> *'Unverified*' = lastReceivedRequestTime value is empty.
>
> *'No recent conversions'* = mostRecentConversionDate date value is not 
> within last 7 days.
>
> *'Recording conversions'* =  status is ENABLED.
>
> *'Tag inactive'* = lastReceivedRequestTime value is empty and 
> mostRecentConversionDate date value is not within last 7 days.
> OR 
>status is HIDDEN.
>   
> *'Removed'* = status is DISABLED
> *.*
> On Monday, 22 January 2018 20:57:32 UTC+5:30, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Greetings!
>>
>> Thanks for doing your due diligence in looking through our forum first. 
>> In the future, if the forum post looks old, just start a new forum post and 
>> reference the old one. That way, people on the old one don't get bumped. 
>> Just to save time, I won't have you start a new one this time. For 
>> something to be *Unverified*, it *this conversion type has never had any 
>> conversions.* That can be checked in another place other than status. I 
>> double-checked our code base to be sure, but you can also look at the 
>> lastReceivedRequestTime 
>> 
>>  
>> field to see if there is a value there. If you don't see a value, then 
>> there haven't been any conversion, and it is unverified. 
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Monday, January 22, 2018 at 6:52:55 AM UTC-5, cv wrote:
>>>
>>> Hello Nadine,
>>>
>>> I am also looking at for conversion tracking status like mention on 
>>> below point
>>>
>>> 1. Tracking Status
>>>
>>> On API, status field has 3 values (*Enable*, *Disable* and *Hidden*)
>>>
>>> On Adwords website, tracking status has  5 values ("Unverified", "No 
>>> recent conversions", "Recording conversions", "Tag inactive  and "
>>> *Removed*")
>>>
>>> I want to inform our internal user about tag Unverified if by 
>>> mistakenly conversion tracker code removed from website. 
>>>  
>>>
>>>
>>>
>>> On Friday, 12 June 2015 19:09:43 UTC+5:30, Nadine Sundquist (AdWords API 
>>> Team) wrote:

 Hi,

 Could you please click *Reply privately to author *and send me your 
 customer ID with the conversions that you're trying to retrieve? I want to 
 verify what I've found actually works before sending you the answer.

 Thanks,
 Nadine, AdWords API Team

 On Thursday, May 28, 2015 at 9:59:05 PM UTC-4, Le Le wrote:
>
> Hi Nadine,
>
> I need build a desktop application to manage Conversion tracker. I've 
> taken the most of infomation from *ConversionTrackerService *except 
> "Tracking status", "Repeat rate" and "Tracking event".
>
> Thanks for your support!
>  
>
> On Friday, May 29, 2015 at 7:53:17 AM UTC+7, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello,
>>
>> To get this all this information from the *ConversionTrackerService* 
>> requires combining multiple fields in the API. What are you trying to 
>> build, or what is your goal? Perhaps, there's another service I can 
>> recommend to get this kind of data that doesn't require doing 
>> calculations 
>> or combining fields.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, May 28, 2015 at 12:24:04 AM UTC-7, Le Le wrote:
>>>
>>> Hi Nadine!
>>>
>>> I don't understand about information below:
>>>
>>> 1. Tracking Status
>>>
>>> On API, status field has 3 values (*Enable*, *Disable* and *Hidden*)
>>>
>>> On Adwords website, tracking status has  5 values ("Unverified", "No 
>>> recent conversions", "Recording conversions", "Tag inactive  and "
>>> *Removed*")
>>>
>>> So, how to mapping ?
>>>
>>> 2. Repeat rate
>>>
>>> Can you detail explain for me?
>>>
>>> 3. Tracking event
>>>
>>> I try to switch 2 options *Click *and *Page load, *but when using 
>>> API to get data. I don't identity what field matching with *Click *and 
>>> *Page *load options.
>>>
>>> 4. Conversion value option
>>>
>>> *This problem is resolved.*
>>>
>>>
>>> Thanks for your support again.
>>>
>>>  
>>>
>>>
>>> On Thursday, May 28, 2015 at 1:53:36 AM UTC+7, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello,

 Thanks for clarifying what you need. There isn't always an exact 
 one to one mapping for what you're asking, but you can still 

Re: How to get Tracking status, Repeat rate, Tracking event by using ConversionTrackerService ?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

Thanks for doing your due diligence in looking through our forum first. In 
the future, if the forum post looks old, just start a new forum post and 
reference the old one. That way, people on the old one don't get bumped. 
Just to save time, I won't have you start a new one this time. For 
something to be *Unverified*, it *this conversion type has never had any 
conversions.* That can be checked in another place other than status. I 
double-checked our code base to be sure, but you can also look at the 
lastReceivedRequestTime 

 
field to see if there is a value there. If you don't see a value, then 
there haven't been any conversion, and it is unverified. 

Cheers,
Nadine, AdWords API Team

On Monday, January 22, 2018 at 6:52:55 AM UTC-5, cv wrote:
>
> Hello Nadine,
>
> I am also looking at for conversion tracking status like mention on below 
> point
>
> 1. Tracking Status
>
> On API, status field has 3 values (*Enable*, *Disable* and *Hidden*)
>
> On Adwords website, tracking status has  5 values ("Unverified", "No 
> recent conversions", "Recording conversions", "Tag inactive  and "
> *Removed*")
>
> I want to inform our internal user about tag Unverified if by mistakenly 
> conversion tracker code removed from website. 
>  
>
>
>
> On Friday, 12 June 2015 19:09:43 UTC+5:30, Nadine Sundquist (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Could you please click *Reply privately to author *and send me your 
>> customer ID with the conversions that you're trying to retrieve? I want to 
>> verify what I've found actually works before sending you the answer.
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Thursday, May 28, 2015 at 9:59:05 PM UTC-4, Le Le wrote:
>>>
>>> Hi Nadine,
>>>
>>> I need build a desktop application to manage Conversion tracker. I've 
>>> taken the most of infomation from *ConversionTrackerService *except 
>>> "Tracking status", "Repeat rate" and "Tracking event".
>>>
>>> Thanks for your support!
>>>  
>>>
>>> On Friday, May 29, 2015 at 7:53:17 AM UTC+7, Nadine Sundquist (AdWords 
>>> API Team) wrote:

 Hello,

 To get this all this information from the *ConversionTrackerService* 
 requires combining multiple fields in the API. What are you trying to 
 build, or what is your goal? Perhaps, there's another service I can 
 recommend to get this kind of data that doesn't require doing calculations 
 or combining fields.

 Best,
 Nadine, AdWords API Team

 On Thursday, May 28, 2015 at 12:24:04 AM UTC-7, Le Le wrote:
>
> Hi Nadine!
>
> I don't understand about information below:
>
> 1. Tracking Status
>
> On API, status field has 3 values (*Enable*, *Disable* and *Hidden*)
>
> On Adwords website, tracking status has  5 values ("Unverified", "No 
> recent conversions", "Recording conversions", "Tag inactive  and "
> *Removed*")
>
> So, how to mapping ?
>
> 2. Repeat rate
>
> Can you detail explain for me?
>
> 3. Tracking event
>
> I try to switch 2 options *Click *and *Page load, *but when using API 
> to get data. I don't identity what field matching with *Click *and *Page 
> *load options.
>
> 4. Conversion value option
>
> *This problem is resolved.*
>
>
> Thanks for your support again.
>
>  
>
>
> On Thursday, May 28, 2015 at 1:53:36 AM UTC+7, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello,
>>
>> Thanks for clarifying what you need. There isn't always an exact one 
>> to one mapping for what you're asking, but you can still gather the same 
>> information. 
>>
>> 1. Tracking Status
>> => In ConversionTracker 
>> ,
>>  
>> the status 
>> 
>>  field 
>> has descriptions that match each of the values you mentioned. For 
>> example, *ENABLED 
>> *means *Recording conversions*.
>> 2. Repeat Rate
>> => It looks like this value can be calculated based on the data in 
>> ConversionTrackerStats 
>> 
>> .
>> 3. Tracking event
>> => It looks like category 
>> 
>>  in 
>> ConversionTracker 
>> 
>>  
>> has *Page Load* matching to *PAGE_VIEW*. 
>> 4. Conversion value 

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Hans,

No worries! It gets pretty busy around here, so it's fine to bump a thread. 
It's good to know the scale of how it's affecting you. I'm checking in on 
the internal thread I have going for this. Hopefully, we'll have an answer 
soon. This does seem to be an odd one.

Regards,
Nadine, AdWords API Team

On Tuesday, January 16, 2018 at 2:16:50 PM UTC-5, HK wrote:
>
> Hi, Nadina
>
> Hate nag you about this, but is there any way to escalate this? It's a 
> pretty big unexplained/undocumented change that is affecting ~30 merchant 
> accounts we manage.
>
> Hans
>
> On Wednesday, January 10, 2018 at 12:00:23 PM UTC-8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Hans,
>>
>> At this point, I'm not sure why that's happening. We're still 
>> investigating. I'll get back to you when we have more information. I'm glad 
>> you brought it to light with your analysis.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Wednesday, January 10, 2018 at 12:54:31 PM UTC-5, HK wrote:
>>>
>>> Hi, Nadine
>>>
>>> As for issue 2, any indication as to what is going on? This is having a 
>>> pretty big impact on a number of large accounts we manage and has been 
>>> occurring for two months soon. Appreciate your help!
>>>
>>> Hans
>>>
>>> On Monday, January 8, 2018 at 9:42:13 AM UTC-8, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Everyone,

 I would like to follow up publicly on the thread since I have multiple 
 threads going on privately in case someone bumps into this. There are two 
 issues that are happening on this thread:

- *Issue 1: *The AdType 

 
  
is at times coming back empty. There are some ad types that are only 
available in the UI and are not yet supported in the API. That is the 
 case 
here with some of these Gmail ads. In this case, the proper response 
 should 
be *UNKNOWN* rather than an empty response as AdType. I've filed an 
issue for this, and I'll report back when the issue has been fixed.
- *Issue 2:* The secondary issues is that PLA ads have stopped 
showing *Headline* as a ClikType 

 
  as 
of November 18th. I've seen that in a number of places, but I don't see 
 an 
exact reason. I'm asking around about it now. I personally noticed that 
shopping ads did change recently (while I was doing my holiday 
 shopping), 
and I'm wondering if that that's had an impact on how clicks are 
 reported.

 I'll report back here when I hear more.

 Cheers,
 Nadine, AdWords API Team

 On Thursday, January 4, 2018 at 6:50:13 PM UTC-5, HK wrote:
>
> I have replied privately to Bharani with further details.
>
> On Thursday, January 4, 2018 at 12:30:53 PM UTC-8, Bharani Cherukuri 
> (AdWords API Team) wrote:
>>
>> Hello Hans, 
>>
>> We can definitely take a look at this issue. From what I understand, 
>> you're experiencing a discrepancy with the clickType field in your Ad 
>> Performance Report. If that's the case, could you share us the complete 
>> report 
>> definition 
>> 
>>  along 
>> with the clientCustomerId, so I can take a look? Please use *Reply 
>> privately to author* option to share the details. 
>>
>> Regards,
>> Bharani, AdWords API Team
>>
>> On Monday, December 25, 2017 at 9:46:07 PM UTC-5, Thao wrote:
>>>
>>> Hi all, 
>>>
>>> current, in my download data AdWords API return empty for fields 
>>> "AdType" and "Headline", any change on API or error, give me a hand, 
>>> thank 
>>> you.
>>>
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 

Re: Some keywords get no results from TargetingIdeaService

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello AdWordsians,

My apologies for not posting back here on the progress. This is a general 
ongoing issue where there are words or phrases that are returning stats in 
the UI, but not through the API. There appears to be a stricter filter that 
causes certain phrases to not show up in the API. I am actively working 
with the rest of my team in trying to find the exact source of the issue 
that is causing this. I'll post back here when we have more information. 

Regards,
Nadine, AdWords API Team

On Thursday, January 11, 2018 at 2:41:51 AM UTC-5, Aviv Oron wrote:
>
> Nope :(
> Im still waiting for an update from adwords API team, i was told the issue 
> was passed to engineering...
>
> On Thursday, January 11, 2018 at 12:55:25 AM UTC+2, Andres Tobar wrote:
>>
>> Hi Aviv,
>>
>> Were you able to get this issue resolved? I'm having the same exact issue 
>> with my setup at the moment.
>>
>> Thanks,
>> Andres
>>
>> On Thursday, December 28, 2017 at 12:32:19 PM UTC-5, Aviv Oron wrote:
>>>
>>> Hey, 
>>>
>>> Im trying to get keyword stats data using TargetingIdeaService.
>>> For some keywords, the response is empty! (totalNumEntries=0)
>>> For example, for the keyword "bullfight" ill get an empty page, and for 
>>> keyword "catfight" ill get proper results.
>>> Those keywords I'm failing to get results for, DO have data when I'm 
>>> querying the web client!
>>>
>>> This is how i build the selector:
>>>
>>> selector = {
>>> 'searchParameters': [
>>> {
>>> 'xsi_type': 'RelatedToQuerySearchParameter',
>>> 'queries': ['bullfight']
>>> },
>>> {
>>> 'xsi_type': 'NetworkSearchParameter',
>>> 'networkSetting': {
>>> 'targetGoogleSearch': True,
>>> 'targetSearchNetwork': False,
>>> 'targetContentNetwork': False,
>>> 'targetPartnerSearchNetwork': False
>>> }
>>> }
>>> ],
>>> 'ideaType': 'KEYWORD',
>>> 'requestType': 'STATS',
>>> 'requestedAttributeTypes': [
>>> 'COMPETITION', 'AVERAGE_CPC', 'KEYWORD_TEXT', 'SEARCH_VOLUME'
>>> ],
>>> 'paging': {
>>> 'startIndex': '0',
>>> 'numberResults': '100'
>>> }
>>> }
>>>
>>>
>>>
>>> Hope someone can help with this issue :)
>>> Thanks!
>>> Aviv
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/677338ed-e74a-4324-b2da-a7f4e33a48cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Hans,

At this point, I'm not sure why that's happening. We're still 
investigating. I'll get back to you when we have more information. I'm glad 
you brought it to light with your analysis.

Best,
Nadine, AdWords API Team

On Wednesday, January 10, 2018 at 12:54:31 PM UTC-5, HK wrote:
>
> Hi, Nadine
>
> As for issue 2, any indication as to what is going on? This is having a 
> pretty big impact on a number of large accounts we manage and has been 
> occurring for two months soon. Appreciate your help!
>
> Hans
>
> On Monday, January 8, 2018 at 9:42:13 AM UTC-8, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello Everyone,
>>
>> I would like to follow up publicly on the thread since I have multiple 
>> threads going on privately in case someone bumps into this. There are two 
>> issues that are happening on this thread:
>>
>>- *Issue 1: *The AdType 
>>
>> 
>>  
>>is at times coming back empty. There are some ad types that are only 
>>available in the UI and are not yet supported in the API. That is the 
>> case 
>>here with some of these Gmail ads. In this case, the proper response 
>> should 
>>be *UNKNOWN* rather than an empty response as AdType. I've filed an 
>>issue for this, and I'll report back when the issue has been fixed.
>>- *Issue 2:* The secondary issues is that PLA ads have stopped 
>>showing *Headline* as a ClikType 
>>
>> 
>>  as 
>>of November 18th. I've seen that in a number of places, but I don't see 
>> an 
>>exact reason. I'm asking around about it now. I personally noticed that 
>>shopping ads did change recently (while I was doing my holiday shopping), 
>>and I'm wondering if that that's had an impact on how clicks are reported.
>>
>> I'll report back here when I hear more.
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Thursday, January 4, 2018 at 6:50:13 PM UTC-5, HK wrote:
>>>
>>> I have replied privately to Bharani with further details.
>>>
>>> On Thursday, January 4, 2018 at 12:30:53 PM UTC-8, Bharani Cherukuri 
>>> (AdWords API Team) wrote:

 Hello Hans, 

 We can definitely take a look at this issue. From what I understand, 
 you're experiencing a discrepancy with the clickType field in your Ad 
 Performance Report. If that's the case, could you share us the complete 
 report 
 definition 
 
  along 
 with the clientCustomerId, so I can take a look? Please use *Reply 
 privately to author* option to share the details. 

 Regards,
 Bharani, AdWords API Team

 On Monday, December 25, 2017 at 9:46:07 PM UTC-5, Thao wrote:
>
> Hi all, 
>
> current, in my download data AdWords API return empty for fields 
> "AdType" and "Headline", any change on API or error, give me a hand, 
> thank 
> you.
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/97384d90-6592-4898-934b-0cc24e3ceec4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Urgent. ReportDownloadError.

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello David,

Could you do me a big favor? Could you please start a separate forum thread 
for this? It looks like you're having a slightly different issue, and I 
don't want to drag everyone on this thread into this new issue. Thank you 
for taking the time to search through our forum for a similar issue. I 
really do appreciate that. Once you start a new thread, someone on my team 
will start digging into it.

Thanks,
Nadine, AdWords API Team

On Tuesday, January 9, 2018 at 1:00:10 PM UTC-5, davidrben...@gmail.com 
wrote:
>
> Hi,
> I am having the same problem now
>
> Content:
> REDACTED REPORT DATA
> 11:46:40 
> 01/09/18|ERROR|a.vendor.google.adwords.GoogleAdwordsArchiver|Failed to 
> execute request. HTTP Response Code: 500, Trigger: Unable to create report, 
> Type: ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE
> HTTP Response Code: 500, Trigger: Unable to create report, Type: 
> ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE
> at com.google.api.ads.adwords.lib.utils.*v201710*
> .DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>
> and this is with the latest version: *v201710.*
> Are you guy going to fix it?
> Thanks,
>
> -David
>
> On Monday, April 3, 2017 at 4:39:40 PM UTC-4, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello Everyone!
>>
>> We've resolved the issue. You should no longer be seeing this error. If 
>> you see it again, please get back to me. We're currently working on putting 
>> measures in place to ensure that this particular issue does not pop up 
>> again.
>>
>> Take care,
>> Nadine, AdWords API Team
>>
>>
>> On Monday, April 3, 2017 at 1:44:08 PM UTC-4, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Greetings AdWordsians,
>>>
>>> This error is a current high priority issue in the AdWords API. We're 
>>> currently working on a solution. I'll send you an update when the issue has 
>>> been resolved. You can also follow updates on this forum post 
>>> 
>>>  as 
>>> this started on March 31st.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Monday, April 3, 2017 at 10:36:27 AM UTC-4, Kenneth wrote:

 If it helps you.

 I'm using the example from 
 https://github.com/googleads/googleads-dotnet-lib/releases/download/v20.0.0/adwords_dotnet_lib_src_v20.0.0.zip
 Into class ParallelReportDownload.cs into method ProcessCustomer, into 
 catch exception, i add again the account to queue. XXX.TryAdd (XXX of type 
 IProducerConsumerCollection) and just 3 times. If fail 4 times, i report 
 an 
 error.

 Regards.

 El lunes, 3 de abril de 2017, 16:19:58 (UTC+2), Kamil Rajkowski 
 escribió:
>
> I have exactly the same. It started from friday 31.03.2017, and today 
> most of queries gave that error.
> I also sent about this problem to our guy from google, he will keep me 
> in touch if he has some update.
>
> W dniu poniedziałek, 3 kwietnia 2017 15:28:08 UTC+2 użytkownik Kenneth 
> napisał:
>>
>> Edit: I'm publishing 3 post but i don't see anything in the list :(
>>
>> Hi,
>>
>> I've seen a post with a similar error, but is of the 2013, therefore 
>> i've thought i should to open this new post.
>>
>> I'm downloading many reports using google.adwords v.20.0.0.0 and 
>> google.ads.common v5.0.0.0 and just with some reports i have to 
>> problems. 
>> The accounts aren't always the same.
>> I'm having this error several days.
>>
>> I'm receiving this error in exception message:
>>
>> AdWordsReportsException: One or more AdWords Report download errors 
>> have occurred.
>>
>> ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE. (Error: 
>> ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE, FieldPath: , Trigger: 
>> Unable to create report)
>>
>> And this error in inner exception message:
>>
>> Error on remote server: (500) Internal server error.
>>
>> May someone help me, please?
>>
>> Thank you.
>>
>> Regards.
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
Visit this 

Re: Empty fields "AdType" and "Headline" in Ad Performance Report (v201705)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Everyone,

I would like to follow up publicly on the thread since I have multiple 
threads going on privately in case someone bumps into this. There are two 
issues that are happening on this thread:

   - *Issue 1: *The AdType 
   

 
   is at times coming back empty. There are some ad types that are only 
   available in the UI and are not yet supported in the API. That is the case 
   here with some of these Gmail ads. In this case, the proper response should 
   be *UNKNOWN* rather than an empty response as AdType. I've filed an 
   issue for this, and I'll report back when the issue has been fixed.
   - *Issue 2:* The secondary issues is that PLA ads have stopped showing 
   *Headline* as a ClikType 
   

 as 
   of November 18th. I've seen that in a number of places, but I don't see an 
   exact reason. I'm asking around about it now. I personally noticed that 
   shopping ads did change recently (while I was doing my holiday shopping), 
   and I'm wondering if that that's had an impact on how clicks are reported.

I'll report back here when I hear more.

Cheers,
Nadine, AdWords API Team

On Thursday, January 4, 2018 at 6:50:13 PM UTC-5, HK wrote:
>
> I have replied privately to Bharani with further details.
>
> On Thursday, January 4, 2018 at 12:30:53 PM UTC-8, Bharani Cherukuri 
> (AdWords API Team) wrote:
>>
>> Hello Hans, 
>>
>> We can definitely take a look at this issue. From what I understand, 
>> you're experiencing a discrepancy with the clickType field in your Ad 
>> Performance Report. If that's the case, could you share us the complete 
>> report 
>> definition 
>> 
>>  along 
>> with the clientCustomerId, so I can take a look? Please use *Reply 
>> privately to author* option to share the details. 
>>
>> Regards,
>> Bharani, AdWords API Team
>>
>> On Monday, December 25, 2017 at 9:46:07 PM UTC-5, Thao wrote:
>>>
>>> Hi all, 
>>>
>>> current, in my download data AdWords API return empty for fields 
>>> "AdType" and "Headline", any change on API or error, give me a hand, thank 
>>> you.
>>>
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/b651485a-f272-4878-819f-85cdff7e6241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AxisFault/Server.userException/org.xml.sax.SAXParseException/An invalid XML character (Unicode: 0x8) was found in the element content of the document.

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Zedd,

Thanks for getting back to me. I'm so happy to hear that you got it 
resolved!

Take care,
Nadine, AdWords API Team

On Friday, December 1, 2017 at 12:51:12 AM UTC-5, Virtual Digital wrote:
>
>
> Hello Nadine.
>
> This is really helpful to me.
> After removing the label, the problem was solved.
>
> Thank you so much.
> Zedd
>
> 在 2017年12月1日星期五 UTC+8上午10:41:19，Nadine Sundquist (AdWords API Team)写道：
>>
>> Hello Zedd.
>>
>> This can be tricky to bug, but I think I found some of the culprits. You 
>> are completely correct that it is a backspace that is found in the 
>> response. i found that it is specifically in some of the labels that are 
>> coming back. For example, the following label name coming back has a 
>> backspace in it before the word Tina:
>>
>> 4933659 
>> Tina
>>
>>
>> When the parsing is happening you should be getting back errors as to 
>> specifically where in the response the parsing error is happening. You can 
>> then use that information to fix the labels through the UI. I usually take 
>> the entire SOAP response and put it into an editor that can see all 
>> characters when trying to debug an issue like this. 
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Thursday, November 30, 2017 at 7:53:24 AM UTC-5, Virtual Digital wrote:
>>>
>>> Hi,
>>> I was trying to request the AdWords API to synchronize the 
>>> accountPerformanceReport.But there was such an error.
>>>
>>>
>>> 
>>> The specific request as shown below.
>>>
>>>
>>> 
>>> Does this mean that there's an embedded backspace (Unicode 0x8) in the 
>>> request or response?
>>> response:
>>>
>>>
>>> 
>>>
>>> How should I solve this problem?Any idea?Thx
>>> Zedd
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/2c6ba5f8-ec2c-4947-9a47-9bc9b1aa205a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Oksana,

I just received word that the issue is fixed. Please take a look when you 
get a chance. If you experience any other issues around this, please get 
back to me.

Thanks,
Nadine, AdWords API Team

On Friday, November 17, 2017 at 4:14:32 PM UTC-5, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hello Oksana,
>
> I just wanted to give you a heads-up that we found the root cause. Yay! We 
> are currently working on a solution, but I don't have a date for when a fix 
> would be available. I'll keep you updated in the coming weeks as I hear 
> more.
>
> Cheers,
> Nadine, AdWords API Team
>
> On Tuesday, November 14, 2017 at 12:35:57 PM UTC-5, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Oksana,
>>
>> I'm disappointed to tell you that we have not resolved it, yet. I do have 
>> an active conversation going on internally on this, but we haven't found 
>> the source of the issue. Thanks for checking in on this!
>>
>> Regards,
>> Nadine, AdWords API Team
>>
>> On Tuesday, November 14, 2017 at 6:41:11 AM UTC-5, Oksana Sulyma wrote:
>>>
>>> Hi Nadine! 
>>> How is it going with the solution of this issue? Any updates?
>>> Looking forward to hear good news from you!
>>> Thanks,
>>> Oksana
>>>
>>> On Tuesday, September 12, 2017 at 5:52:28 PM UTC+3, Oksana Sulyma wrote:

 Hi guys,
 I'm requesting 
 https://adwords.google.com/api/adwords/mcm/v201702/CustomerService and 
 getting the next error:

 soap:ServerInternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
 com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroInternalApiError.UNEXPECTED_INTERNAL_API_ERROR
  
 @ 
 com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroApiExceptionInternalApiError.UNEXPECTED_INTERNAL_API_ERRORInternalApiErrorUNEXPECTED_INTERNAL_API_ERROR


 curl_info is next:
 ( [url] => 
 https://adwords.google.com/api/adwords/mcm/v201702/CustomerService 
 [content_type] => text/xml; charset=UTF-8 [http_code] => 500 [header_size] 
 => 420 [request_size] => 858 [filetime] => -1 [ssl_verify_result] => 0 
 [redirect_count] => 0 [total_time] => 121.246653 [namelookup_time] => 
 0.004202 [connect_time] => 0.287567 [pretransfer_time] => 0.87369 
 [size_upload] => 536 [size_download] => 1103 [speed_download] => 9 
 [speed_upload] => 4 [download_content_length] => -1 
 [upload_content_length] 
 => 536 [starttransfer_time] => 121.246455 [redirect_time] => 0 
 [redirect_url] => [primary_ip] => 173.194.222.100 [certinfo] => Array ( ) 
 [primary_port] => 443 [local_ip] => 10.99.99.22 [local_port] => 37912 )

 my xml looks next:
 http://schemas.xmlsoap.org/soap/envelope/; xmlns:v20="
 https://adwords.google.com/api/adwords/mcm/v201702; xmlns:v201="
 https://adwords.google.com/api/adwords/cm/v201702;>

   
  mytoken
  myagent
   


   

 

 This code works for lots of different Adwords accounts, getting SOAP 
 error just for one - can send details on it.

 Repeating the request doesn't help. Really need any input which can 
 help to troubleshoot. Thanks!  

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/ae2402ea-17e1-4582-b627-06f9946dd736%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AxisFault/Server.userException/org.xml.sax.SAXParseException/An invalid XML character (Unicode: 0x8) was found in the element content of the document.

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Zedd.

This can be tricky to bug, but I think I found some of the culprits. You 
are completely correct that it is a backspace that is found in the 
response. i found that it is specifically in some of the labels that are 
coming back. For example, the following label name coming back has a 
backspace in it before the word Tina:

4933659 
Tina


When the parsing is happening you should be getting back errors as to 
specifically where in the response the parsing error is happening. You can 
then use that information to fix the labels through the UI. I usually take 
the entire SOAP response and put it into an editor that can see all 
characters when trying to debug an issue like this. 

Cheers,
Nadine, AdWords API Team

On Thursday, November 30, 2017 at 7:53:24 AM UTC-5, Virtual Digital wrote:
>
> Hi,
> I was trying to request the AdWords API to synchronize the 
> accountPerformanceReport.But there was such an error.
>
>
> 
> The specific request as shown below.
>
>
> 
> Does this mean that there's an embedded backspace (Unicode 0x8) in the 
> request or response?
> response:
>
>
> 
>
> How should I solve this problem?Any idea?Thx
> Zedd
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/a5bb912f-55dc-48df-80bd-ceb16b75dcf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

I just wanted to give you a heads-up that we found the root cause. Yay! We 
are currently working on a solution, but I don't have a date for when a fix 
would be available. I'll keep you updated in the coming weeks as I hear 
more.

Cheers,
Nadine, AdWords API Team

On Tuesday, November 14, 2017 at 12:35:57 PM UTC-5, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Oksana,
>
> I'm disappointed to tell you that we have not resolved it, yet. I do have 
> an active conversation going on internally on this, but we haven't found 
> the source of the issue. Thanks for checking in on this!
>
> Regards,
> Nadine, AdWords API Team
>
> On Tuesday, November 14, 2017 at 6:41:11 AM UTC-5, Oksana Sulyma wrote:
>>
>> Hi Nadine! 
>> How is it going with the solution of this issue? Any updates?
>> Looking forward to hear good news from you!
>> Thanks,
>> Oksana
>>
>> On Tuesday, September 12, 2017 at 5:52:28 PM UTC+3, Oksana Sulyma wrote:
>>>
>>> Hi guys,
>>> I'm requesting 
>>> https://adwords.google.com/api/adwords/mcm/v201702/CustomerService and 
>>> getting the next error:
>>>
>>> soap:ServerInternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroInternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>>>  
>>> @ 
>>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroApiExceptionInternalApiError.UNEXPECTED_INTERNAL_API_ERRORInternalApiErrorUNEXPECTED_INTERNAL_API_ERROR
>>>
>>>
>>> curl_info is next:
>>> ( [url] => 
>>> https://adwords.google.com/api/adwords/mcm/v201702/CustomerService 
>>> [content_type] => text/xml; charset=UTF-8 [http_code] => 500 [header_size] 
>>> => 420 [request_size] => 858 [filetime] => -1 [ssl_verify_result] => 0 
>>> [redirect_count] => 0 [total_time] => 121.246653 [namelookup_time] => 
>>> 0.004202 [connect_time] => 0.287567 [pretransfer_time] => 0.87369 
>>> [size_upload] => 536 [size_download] => 1103 [speed_download] => 9 
>>> [speed_upload] => 4 [download_content_length] => -1 [upload_content_length] 
>>> => 536 [starttransfer_time] => 121.246455 [redirect_time] => 0 
>>> [redirect_url] => [primary_ip] => 173.194.222.100 [certinfo] => Array ( ) 
>>> [primary_port] => 443 [local_ip] => 10.99.99.22 [local_port] => 37912 )
>>>
>>> my xml looks next:
>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:v20="
>>> https://adwords.google.com/api/adwords/mcm/v201702; xmlns:v201="
>>> https://adwords.google.com/api/adwords/cm/v201702;>
>>>
>>>   
>>>  mytoken
>>>  myagent
>>>   
>>>
>>>
>>>   
>>>
>>> 
>>>
>>> This code works for lots of different Adwords accounts, getting SOAP 
>>> error just for one - can send details on it.
>>>
>>> Repeating the request doesn't help. Really need any input which can help 
>>> to troubleshoot. Thanks!  
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/c3785cc4-16c8-480f-b6a1-391d464ceac6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API not responding

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Anton,

On occasion, there are issues either on the client side or the server side 
with serving WSDLs especially when they have to be pulled so frequently. I 
have good news for you! Due to this being a general issue, we released a 
new PHP client library version 
 yesterday 
that has all the WSDLs included in the library so it doesn't need to go to 
the server for them. If you're still using an older version of the PHP 
client library, then you can change the wsdlCache 

 option 
to cache all the WSDLs. If you have any further issues after making one of 
those changes, then please get back to me.

Happy coding,
Nadine, AdWords API Team

On Wednesday, November 15, 2017 at 1:04:37 AM UTC-5, Vincent Racaza 
(AdWords API Team) wrote:
>
> Hi Anton,
>
> Could you provide your SOAP request and response logs with your actual 
> clientCustomerId via *Reply privately to author* so we can further 
> investigate?
>
> Thanks,
> Vincent
> 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+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.
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/9a7f4bc3-18e2-4172-8520-2103f1e9d9df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to clear a targetRoasOverride value?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Al,

Our resident expert over here says that you should be able to set it to 0 
to turn off the override. Could you please give that a try? In the 
meantime, we need to update our documentation.

Take care,
Nadine, AdWords API Team

On Friday, November 10, 2017 at 4:47:19 PM UTC-5, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hello Al,
>
> Unfortunately, I don't have the answer on this one, yet. I'm pulling in 
> another person on an internal thread who may know the answer. I'm hoping 
> she may know the answer. Thanks for checking in!
>
> Cheers,
> Nadine, AdWords API Team
>
> On Friday, November 10, 2017 at 4:42:15 PM UTC-5, wrote:
>>
>> Hello Nadine,
>>
>> Have you been able to find out how to clear a "targetRoasOverride" field 
>> from an Ad Group once it has been set?
>>
>> Thanks!
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/71c3d242-8108-4871-afc5-a4984ac63c75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

I'm disappointed to tell you that we have not resolved it, yet. I do have 
an active conversation going on internally on this, but we haven't found 
the source of the issue. Thanks for checking in on this!

Regards,
Nadine, AdWords API Team

On Tuesday, November 14, 2017 at 6:41:11 AM UTC-5, Oksana Sulyma wrote:
>
> Hi Nadine! 
> How is it going with the solution of this issue? Any updates?
> Looking forward to hear good news from you!
> Thanks,
> Oksana
>
> On Tuesday, September 12, 2017 at 5:52:28 PM UTC+3, Oksana Sulyma wrote:
>>
>> Hi guys,
>> I'm requesting 
>> https://adwords.google.com/api/adwords/mcm/v201702/CustomerService and 
>> getting the next error:
>>
>> soap:ServerInternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroInternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>>  
>> @ 
>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroApiExceptionInternalApiError.UNEXPECTED_INTERNAL_API_ERRORInternalApiErrorUNEXPECTED_INTERNAL_API_ERROR
>>
>>
>> curl_info is next:
>> ( [url] => 
>> https://adwords.google.com/api/adwords/mcm/v201702/CustomerService 
>> [content_type] => text/xml; charset=UTF-8 [http_code] => 500 [header_size] 
>> => 420 [request_size] => 858 [filetime] => -1 [ssl_verify_result] => 0 
>> [redirect_count] => 0 [total_time] => 121.246653 [namelookup_time] => 
>> 0.004202 [connect_time] => 0.287567 [pretransfer_time] => 0.87369 
>> [size_upload] => 536 [size_download] => 1103 [speed_download] => 9 
>> [speed_upload] => 4 [download_content_length] => -1 [upload_content_length] 
>> => 536 [starttransfer_time] => 121.246455 [redirect_time] => 0 
>> [redirect_url] => [primary_ip] => 173.194.222.100 [certinfo] => Array ( ) 
>> [primary_port] => 443 [local_ip] => 10.99.99.22 [local_port] => 37912 )
>>
>> my xml looks next:
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:v20="
>> https://adwords.google.com/api/adwords/mcm/v201702; xmlns:v201="
>> https://adwords.google.com/api/adwords/cm/v201702;>
>>
>>   
>>  mytoken
>>  myagent
>>   
>>
>>
>>   
>>
>> 
>>
>> This code works for lots of different Adwords accounts, getting SOAP 
>> error just for one - can send details on it.
>>
>> Repeating the request doesn't help. Really need any input which can help 
>> to troubleshoot. Thanks!  
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/b167fdb6-f259-4cf6-92a1-6c80ba07cfdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to clear a targetRoasOverride value?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Al,

Unfortunately, I don't have the answer on this one, yet. I'm pulling in 
another person on an internal thread who may know the answer. I'm hoping 
she may know the answer. Thanks for checking in!

Cheers,
Nadine, AdWords API Team

On Friday, November 10, 2017 at 4:42:15 PM UTC-5, wrote:
>
> Hello Nadine,
>
> Have you been able to find out how to clear a "targetRoasOverride" field 
> from an Ad Group once it has been set?
>
> Thanks!
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/3f612a4b-f245-45d0-a5a7-80227d103038%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to clear a targetRoasOverride value?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Al,

That is a good question. I'll have to check on that and get back to you 
because I haven't tried that before, and I double-checked our documentation 
as well.

Best,
Nadine, AdWords API Team

On Friday, November 3, 2017 at 2:12:07 PM UTC-4, wrote:
>
> The "targetRoasOverride" field that has been available since v201705 of 
> the AdWords API is described in the API's Bidding Guide 
>  as:
>>
>>
>> "The TargetRoasBiddingScheme 
>> 
>>  set 
>> at the campaign level can be overriden at the ad group level by setting the 
>> bidding configuration's targetRoasOverride 
>> 
>>  at 
>> the ad group level. The other fields cannot be overriden."
>
>
> However, the description of this field in the  latest AdGroupService API 
> documentation 
> 
>  does 
> not indicate how the "targetRoasOverride" can be cleared from an Ad Group 
> once it has been set.
>
> Can you advise me how to do that?
>
> Thank you
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/0d43f09c-e0ee-4e6a-b3ef-873c42632ec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding a list of Audience to some Campaign/AdGroups

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

In the future, could you please start a new thread with a link over to the 
thread that you're referencing? This really helps both our forum users and 
us. Since this is such a short question, I'll just answer it here.

We don't have an EXACT example for adding a user list as ad group 
criterion, but we do have a very close one. If you look at the example in 
Python for Add demographic targeting criteria to an ad group 
,
 
you can change out the gender criterion for a user list criterion instead. 
The rest of the code would stay the same.

Best,
Nadine, AdWords API Team

On Thursday, November 2, 2017 at 6:00:28 AM UTC-4, 
praj...@lifecycledigitalmarketing.com wrote:
>
> Hey is there a link to a python version of this snippet?
>
> On Friday, January 27, 2017 at 1:20:29 PM UTC-6, Shwetha Vastrad (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> To add an Audience to your AdGroups or Campaigns, you need to add a 
>> criterion of type CriterionUserList 
>> 
>>  using AdGroupCriterionService 
>> 
>>  or CampaignCriterionService 
>> 
>>  respectively. 
>> You need to pass the ID of your user list in the userListId 
>> 
>>  field. 
>> I'm afraid the library doesn't have an example to demonstrate this. The 
>> following code snippet adds an Audience to an AdGroup. 
>>
>> CriterionUserList userList = new CriterionUserList();
>> userList.setUserListId(userListId);
>>
>> BiddableAdGroupCriterion criterion = new BiddableAdGroupCriterion();
>> criterion.setAdGroupId(adGroupId);
>> criterion.setCriterion(userList);
>>
>> AdGroupCriterionOperation operation = new AdGroupCriterionOperation
>> ();
>> operation.setOperand(criterion);
>> operation.setOperator(Operator.ADD);
>>
>> AdGroupCriterionOperation[] operations = new 
>> AdGroupCriterionOperation[] {operation};
>> AdGroupCriterionReturnValue result = adGroupCriterionService.mutate(
>> operations);
>>
>> Regards,
>> Shwetha, 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+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.
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/3b36b97d-4337-4573-997a-9ff3f7624ffd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

I'm glad you checked in! I was able to reach the engineer who was assigned 
to be working on this on my team. On October 27th, he said he would be able 
to look at it by next week.

Cheers,
Nadine, AdWords API Team

On Wednesday, November 1, 2017 at 9:34:08 AM UTC-4, Oksana Sulyma wrote:
>
> Hi Nadine! It's now more then 2 weeks since I asked you about progress 
> with this issue last time. Do you have any news on this? Thank you!!!
> Oksana
>
> On Wednesday, October 11, 2017 at 2:04:26 AM UTC+3, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Oksana,
>>
>> In case you missed my private message, we don't have a solution for this, 
>> yet. I'll see if I can get someone else to look at it on my team.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Tuesday, October 10, 2017 at 10:28:39 AM UTC-4, Oksana Sulyma wrote:
>>>
>>> Hi guys,
>>> Any progress on this issue? Any idea will be helpful.
>>> Thanks!
>>> Oksana
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/47c6f141-2621-4b3e-b326-f5cc6bb05a42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch jobs stay in state processing for several hours and finally get cancelled

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Christian,

You've been so helpful in providing updates; now I get to provide the 
update. Yay! I just got notice from the engineer on my team working on this 
that the issue should be resolved now. Please get back to me if you have 
any further issues with this.

Thanks,
Nadine, AdWords API Team

On Tuesday, October 10, 2017 at 11:25:48 AM UTC-4, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Christian,
>
> I'm pleased to hear that. Thanks for providing an update!
>
> Cheers,
> Nadine, AdWords API Team
>
> On Tuesday, October 10, 2017 at 4:22:53 AM UTC-4, Christian wrote:
>>
>> Hi Nadine,
>>
>> just want to give an update from our side. We incrementally increased our 
>> set-bid-operations-per-day limit again up to 400 000. At the same time we 
>> reduced our batch jobs to have at most 10 000 operations (25 000) before. 
>> So far everything looks good. Jobs usually complete in less than an hour 
>> for large accounts, which is good enough for us.
>>
>> Best,
>> Christian
>>
>> On Monday, September 18, 2017 at 11:24:18 PM UTC+2, Christian wrote:
>>>
>>> Hi Nadine,
>>>
>>> thanks for the update and for looking into this. For now we'll stay with 
>>> our limit of not more than 100 000 set-bid operations per day as this seems 
>>> to be a working scale. Still, I really appreciate it when you report some 
>>> news here once you have them. Thanks again!
>>>
>>> Best,
>>> Christian
>>>
>>> On Monday, September 18, 2017 at 6:54:52 PM UTC+2, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Greetings Christian!

 Here's an update on where we are on this. It turns out that the batch 
 job service attempts to send all the requests, but is internally getting 
 back a REQUEST_SIZE_LIMIT_EXCEEDED 
  
 error. 
 That happens when there are more than 2000 operations in a normal service. 
 What batch job service is doing in the background is that it's breaking up 
 the request when that happens and then sends fewer requests. This is 
 happening so often that the batch job finally cancels itself. That does 
 appear to be an issue on our side because of this. We're exploring 
 solutions, but there isn't a solution, yet. I'll update you when we have 
 more information. At least we now know the root cause of your issue.

 Best,
 Nadine, AdWords API Team

 On Friday, September 15, 2017 at 6:16:13 PM UTC-4, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hello Christian,
>
> Thanks for the update. I don't know of any code fixes that went in 
> within the last day.
>
> Batch job service can theoretically handle quite a few operations, but 
> even 1 000 000 is a lot when you think of all the updates that have to 
> happen on the back end. Some changes are more expensive than others and 
> take a bit longer because even though it looks like you're updating maybe 
> one field, there is logic that needs to check on things like if something 
> can be overridden at specific levels or if other objects in the account 
> will be affected by the change. That's why some things do take a bit 
> longer.
>
> Regards,
> Nadine, AdWords API Team 
>
> On Friday, September 15, 2017 at 2:38:51 PM UTC-4, Christian wrote:
>>
>> Hi Nadine,
>>
>> thanks for looking into that.
>>
>> Today we reduced the total number of set-max-cpc operations to be 
>> below 100 000 and all 4 jobs (each at most 25 000 operations) completed 
>> successfully within a few minutes. Is there already a fix live? Let me 
>> know 
>> if we should have a try again with a larger number of operations.
>>
>> In case it is helpful for debugging, here are the IDs of the jobs 
>> successfully completed today: 565656811, 565639265, 565650926, 565663576.
>>
>> By the way: we also submit more than 1 000 000 bid modifier 
>> operations each day. The corresponding jobs do not get cancelled but 
>> still 
>> require several hours to complete. Do we have to limit our daily number 
>> of 
>> operations here or is that something the batch job service should be 
>> able 
>> to handle faster in theory? An example job ID would be 565684901.
>>
>> Best regards,
>> Christian
>>
>> On Friday, September 15, 2017 at 3:48:31 PM UTC+2, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hello Christian,
>>>
>>> I've taken a look into what's happening, and initially I don't see a 
>>> root cause. My team will dig further into it, and I'll get back to you 
>>> when 
>>> I have the reason as to why these jobs are not successful.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, September 14, 2017 at 4:31:01 PM UTC-4, Christian wrote:

 Hi Shwetha,

 > If the 

Re: BatchJobProcessingError.INTERNAL_ERROR

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings Vlad,

I have an answer to what's going on here. It appears a temporary ID was 
incorrectly reused. In on of your *ADD* BudgetOperations, you are using a 
*budgetId* of *-59*. Then later on in the same job, you are using the *budgetId 
*of *-59* again for another *ADD* BudgetOperation. Each temporary ID needs 
to be unique within the same batch job. Once that's fixed, you should be 
good to go again! 

Happy coding,
Nadine, AdWords API Team

On Thursday, October 12, 2017 at 4:29:44 PM UTC-4, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Vlad,
>
> I do see on our servers that the job did cancel, but I also see results 
> returned in the download URL. It's a little strange to have both. I need to 
> check further into a few things before getting back to you. Hopefully, I'll 
> get this mystery solved soon.
>
> Best,
> Nadine, AdWords API Team
>
> On Thursday, October 12, 2017 at 10:33:33 AM UTC-4, Vlad Gukasov wrote:
>>
>> Hi,
>> I'm just getting BatchJobProcessingError.INTERNAL_ERROR. Please help to 
>> understand reason of it. BatchJob id = 581404827
>> Thanks
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/65966793-06f7-4d1a-a64f-0ce08986c64c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practice for joining AdWords API placement data with AdWords ValueTrack placement data?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Jonathan,

Thank you for being so understanding and for phrasing your questions so 
well. I've added this forum thread to the bug so that if any further 
questions come up around your use case, that you can be contacted.

Cheers,
Nadine, AdWords API Team

On Thursday, October 12, 2017 at 4:43:15 PM UTC-4, Jonathan Clarke wrote:
>
> OK, that makes sense. The values in ValueTrack are often at odds with the 
> API.
>
> Let me know if you'd like more info from us. A bug report perhaps? We've 
> spent a lot of time on this and my partner and I would happily share 
> account info examples with your team if you want. Just let me know…
>
> On Thursday, October 12, 2017 at 4:21:00 PM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Jonathan,
>>
>> I saw that you asked this question on Stack Overflow as well, and the 
>> person there gave the best answer possible. There isn't a one to one 
>> mapping.
>>
>> As for your question, was the API designed to support the ValueTrack 
>> system? I don't believe so because the API existed before ValueTrack was 
>> introduced. The current version of ValueTrack is fairly new. Even people 
>> using the UI have a disconnect from ValueTrack as I've tried to help people 
>> tie together ValueTrack and reporting values before with the same 
>> disconnect. I don't have insight into the design decisions or the 
>> development process for this particular feature, so I can't speak to the 
>> exact history of how this came to be. 
>>
>> I've talked to some people who have ended up turning to Google Analytics 
>> and its API to tie their data together. That's why I recommend at least 
>> taking a look at that route to see if it matches your use case. I really, 
>> really wish I had a better, cleaner answer. I have a feature request open 
>> already for mobile app reporting and ValueTrack to have an easier way of 
>> matching because there are other ValueTrack parameters with the same issue. 
>> I've added this particular use case to the issue. Having one more voice and 
>> one more use case tends to help in trying to find an overall solution to 
>> mind-bending issues like this one.
>>
>> Take care,
>> Nadine, AdWords API Team
>>
>> On Thursday, October 12, 2017 at 1:36:24 PM UTC-4, Jonathan Clarke wrote:
>>>
>>> OK, you've confirmed your API supports the UI, which is great. But is 
>>> your API also designed to support the ValueTrack system?
>>>
>>> On Thursday, October 12, 2017 at 12:43:39 PM UTC-4, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hi Jonathan,

 I probably should have explained a little further. The fields that you 
 see in the API also exist in the UI, which is why you can get help from 
 general AdWords support as well. For example, the Placement report also 
 maps to the UI. Our documentation has a section 
 
  in 
 our Mapping Report to the AdWords UI guide 
 
  
 on how that mapping works. That means it's not just an API issue. It's 
 more 
 of a product issue because people would be struggling with the same kind 
 of 
 issue in the UI as well. 

 Unfortunately, I don't have the answer to your focused question because 
 there are so many caveats that aren't API specific. That's why I'm trying 
 to direct you to other avenues that most likely would have the answer.

 Best,
 Nadine, AdWords API Team

 On Thursday, October 12, 2017 at 8:42:34 AM UTC-4, Jonathan Clarke 
 wrote:
>
> Hi Nadine,
>
> Thanks for looking into this. I do feel our question is directly 
> relevant to the AdWords API. We only want to map API data to ValueTrack 
> data. Please allow me to re-phrase and focus the question:
>
> How do we map AdWords mobile app placement data from the API to 
> ValueTrack?
>
> Best Regards,
> Jonathan Clarke
>
> On Wednesday, October 11, 2017 at 5:21:35 PM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Jonathan,
>>
>> I have a feeling that part of the differences are appearing because 
>> of this:
>>
>>- The content site where your ad was clicked (for 
>>keyword-targeted campaigns), or the matching placement targeting 
>> criteria 
>>for the site where your ad was clicked (for placement-targeted 
>> campaigns).
>>
>> I've searched around for a clear-cut answer for your particular 
>> situation, since I haven't bumped into this particular issue before, but 
>> I 
>> can't seem to find the perfect solution. I'm looking at the problem 
>> you're 
>> trying to solve, and I'm wondering if Google Analytics 
>>  might be a good fit for 
>> you because 

Re: BatchJobProcessingError.INTERNAL_ERROR

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Vlad,

I do see on our servers that the job did cancel, but I also see results 
returned in the download URL. It's a little strange to have both. I need to 
check further into a few things before getting back to you. Hopefully, I'll 
get this mystery solved soon.

Best,
Nadine, AdWords API Team

On Thursday, October 12, 2017 at 10:33:33 AM UTC-4, Vlad Gukasov wrote:
>
> Hi,
> I'm just getting BatchJobProcessingError.INTERNAL_ERROR. Please help to 
> understand reason of it. BatchJob id = 581404827
> Thanks
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/5d54d15e-1cb8-4ab0-a0e1-79966ed1a328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practice for joining AdWords API placement data with AdWords ValueTrack placement data?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Jonathan,

I saw that you asked this question on Stack Overflow as well, and the 
person there gave the best answer possible. There isn't a one to one 
mapping.

As for your question, was the API designed to support the ValueTrack 
system? I don't believe so because the API existed before ValueTrack was 
introduced. The current version of ValueTrack is fairly new. Even people 
using the UI have a disconnect from ValueTrack as I've tried to help people 
tie together ValueTrack and reporting values before with the same 
disconnect. I don't have insight into the design decisions or the 
development process for this particular feature, so I can't speak to the 
exact history of how this came to be. 

I've talked to some people who have ended up turning to Google Analytics 
and its API to tie their data together. That's why I recommend at least 
taking a look at that route to see if it matches your use case. I really, 
really wish I had a better, cleaner answer. I have a feature request open 
already for mobile app reporting and ValueTrack to have an easier way of 
matching because there are other ValueTrack parameters with the same issue. 
I've added this particular use case to the issue. Having one more voice and 
one more use case tends to help in trying to find an overall solution to 
mind-bending issues like this one.

Take care,
Nadine, AdWords API Team

On Thursday, October 12, 2017 at 1:36:24 PM UTC-4, Jonathan Clarke wrote:
>
> OK, you've confirmed your API supports the UI, which is great. But is your 
> API also designed to support the ValueTrack system?
>
> On Thursday, October 12, 2017 at 12:43:39 PM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hi Jonathan,
>>
>> I probably should have explained a little further. The fields that you 
>> see in the API also exist in the UI, which is why you can get help from 
>> general AdWords support as well. For example, the Placement report also 
>> maps to the UI. Our documentation has a section 
>> 
>>  in 
>> our Mapping Report to the AdWords UI guide 
>> 
>>  
>> on how that mapping works. That means it's not just an API issue. It's more 
>> of a product issue because people would be struggling with the same kind of 
>> issue in the UI as well. 
>>
>> Unfortunately, I don't have the answer to your focused question because 
>> there are so many caveats that aren't API specific. That's why I'm trying 
>> to direct you to other avenues that most likely would have the answer.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, October 12, 2017 at 8:42:34 AM UTC-4, Jonathan Clarke wrote:
>>>
>>> Hi Nadine,
>>>
>>> Thanks for looking into this. I do feel our question is directly 
>>> relevant to the AdWords API. We only want to map API data to ValueTrack 
>>> data. Please allow me to re-phrase and focus the question:
>>>
>>> How do we map AdWords mobile app placement data from the API to 
>>> ValueTrack?
>>>
>>> Best Regards,
>>> Jonathan Clarke
>>>
>>> On Wednesday, October 11, 2017 at 5:21:35 PM UTC-4, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Jonathan,

 I have a feeling that part of the differences are appearing because of 
 this:

- The content site where your ad was clicked (for keyword-targeted 
campaigns), or the matching placement targeting criteria for the site 
 where 
your ad was clicked (for placement-targeted campaigns).

 I've searched around for a clear-cut answer for your particular 
 situation, since I haven't bumped into this particular issue before, but I 
 can't seem to find the perfect solution. I'm looking at the problem you're 
 trying to solve, and I'm wondering if Google Analytics 
  might be a good fit for you 
 because it can tie a lot of this kind of information together. Have you 
 looked into that?

 Another avenue you could try is posting on the general AdWords 
 Community forum 
 .
  
 This same issue would also show up in reporting in the UI, so they may 
 already have an answer for you. Could you also give that a try? At this 
 point, it's more of a general AdWords problem to solve than intrinsic to 
 the API, so at least there are other support channels you can try like 
 that 
 one.

 Regards, 
 Nadine, AdWords API Team

 On Wednesday, October 11, 2017 at 11:11:03 AM UTC-4, Jonathan Clarke 
 wrote:
>
> Hi Nadine!
>
> Sorry for the delay, I didn't get a notification about your reply.
>
> To illustrate further:
>
> We have an example where ValueTrack {placement} reported the following 
> value: 

Re: Best practice for joining AdWords API placement data with AdWords ValueTrack placement data?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Jonathan,

I probably should have explained a little further. The fields that you see 
in the API also exist in the UI, which is why you can get help from general 
AdWords support as well. For example, the Placement report also maps to the 
UI. Our documentation has a section 

 in 
our Mapping Report to the AdWords UI guide 

 
on how that mapping works. That means it's not just an API issue. It's more 
of a product issue because people would be struggling with the same kind of 
issue in the UI as well. 

Unfortunately, I don't have the answer to your focused question because 
there are so many caveats that aren't API specific. That's why I'm trying 
to direct you to other avenues that most likely would have the answer.

Best,
Nadine, AdWords API Team

On Thursday, October 12, 2017 at 8:42:34 AM UTC-4, Jonathan Clarke wrote:
>
> Hi Nadine,
>
> Thanks for looking into this. I do feel our question is directly relevant 
> to the AdWords API. We only want to map API data to ValueTrack data. Please 
> allow me to re-phrase and focus the question:
>
> How do we map AdWords mobile app placement data from the API to ValueTrack?
>
> Best Regards,
> Jonathan Clarke
>
> On Wednesday, October 11, 2017 at 5:21:35 PM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Jonathan,
>>
>> I have a feeling that part of the differences are appearing because of 
>> this:
>>
>>- The content site where your ad was clicked (for keyword-targeted 
>>campaigns), or the matching placement targeting criteria for the site 
>> where 
>>your ad was clicked (for placement-targeted campaigns).
>>
>> I've searched around for a clear-cut answer for your particular 
>> situation, since I haven't bumped into this particular issue before, but I 
>> can't seem to find the perfect solution. I'm looking at the problem you're 
>> trying to solve, and I'm wondering if Google Analytics 
>>  might be a good fit for you 
>> because it can tie a lot of this kind of information together. Have you 
>> looked into that?
>>
>> Another avenue you could try is posting on the general AdWords Community 
>> forum 
>> .
>>  
>> This same issue would also show up in reporting in the UI, so they may 
>> already have an answer for you. Could you also give that a try? At this 
>> point, it's more of a general AdWords problem to solve than intrinsic to 
>> the API, so at least there are other support channels you can try like that 
>> one.
>>
>> Regards, 
>> Nadine, AdWords API Team
>>
>> On Wednesday, October 11, 2017 at 11:11:03 AM UTC-4, Jonathan Clarke 
>> wrote:
>>>
>>> Hi Nadine!
>>>
>>> Sorry for the delay, I didn't get a notification about your reply.
>>>
>>> To illustrate further:
>>>
>>> We have an example where ValueTrack {placement} reported the following 
>>> value: *411092.iphone.com.weather.twcipadmax.adsenseformobileapps.com 
>>> *.
>>>  
>>> But the AdWords API reports fields (PlacementPerformanceReport.Criteria, 
>>> CriteriaPerformanceReport.Criteria, 
>>> AutomaticPlacementsPerformanceReport.DisplayName and 
>>> UrlPerformanceReport.domain or url) all returned it as 
>>> *mobileapp::1-364252504*.
>>>  
>>> The only way we were able to figure out the relationship between the two 
>>> was because they happened to be our two biggest unmatched fields from each 
>>> data set, but we have many other fields that we can't figure out like that.
>>>
>>> How can we consistently map *.adsenseformobileapps.com 
>>> * from ValueTrack to *mobileapp::* 
>>> from AdWords reports?
>>>
>>> And just to make things a little more interesting...
>>>
>>> Sometimes ValueTrack gives us *xxx.adsenseformobileapps.com 
>>> * format placements but other 
>>> times it gives us in the *mobileapp::* format we can actually match to 
>>> the AdWords reports.  So some placements can be mapped and others can't.
>>>
>>> On Tuesday, October 10, 2017 at 11:14:39 AM UTC-4, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Jonathan,

 Unfortunately, I don't know of a set workflow, but I do have a couple 
 of resources to help you out.

 It looks like you may have found our Mapping ValueTrack Parameters to 
 Report Fields 
  
 guide 
 as you were mapping the ValueTrack parameter to our report fields. 

 What you're seeing are criteria prefixes. We have a list of them here 
 .
  
 Please try 

Re: Best practice for joining AdWords API placement data with AdWords ValueTrack placement data?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Jonathan,

I have a feeling that part of the differences are appearing because of this:

   - The content site where your ad was clicked (for keyword-targeted 
   campaigns), or the matching placement targeting criteria for the site where 
   your ad was clicked (for placement-targeted campaigns).
   
I've searched around for a clear-cut answer for your particular situation, 
since I haven't bumped into this particular issue before, but I can't seem 
to find the perfect solution. I'm looking at the problem you're trying to 
solve, and I'm wondering if Google Analytics 
 might be a good fit for you 
because it can tie a lot of this kind of information together. Have you 
looked into that?

Another avenue you could try is posting on the general AdWords Community 
forum 
. 
This same issue would also show up in reporting in the UI, so they may 
already have an answer for you. Could you also give that a try? At this 
point, it's more of a general AdWords problem to solve than intrinsic to 
the API, so at least there are other support channels you can try like that 
one.

Regards, 
Nadine, AdWords API Team

On Wednesday, October 11, 2017 at 11:11:03 AM UTC-4, Jonathan Clarke wrote:
>
> Hi Nadine!
>
> Sorry for the delay, I didn't get a notification about your reply.
>
> To illustrate further:
>
> We have an example where ValueTrack {placement} reported the following 
> value: *411092.iphone.com.weather.twcipadmax.adsenseformobileapps.com 
> *.
>  
> But the AdWords API reports fields (PlacementPerformanceReport.Criteria, 
> CriteriaPerformanceReport.Criteria, 
> AutomaticPlacementsPerformanceReport.DisplayName and 
> UrlPerformanceReport.domain or url) all returned it as 
> *mobileapp::1-364252504*.
>  
> The only way we were able to figure out the relationship between the two 
> was because they happened to be our two biggest unmatched fields from each 
> data set, but we have many other fields that we can't figure out like that.
>
> How can we consistently map *.adsenseformobileapps.com 
> * from ValueTrack to *mobileapp::* 
> from AdWords reports?
>
> And just to make things a little more interesting...
>
> Sometimes ValueTrack gives us *xxx.adsenseformobileapps.com 
> * format placements but other times 
> it gives us in the *mobileapp::* format we can actually match to the 
> AdWords reports.  So some placements can be mapped and others can't.
>
> On Tuesday, October 10, 2017 at 11:14:39 AM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Jonathan,
>>
>> Unfortunately, I don't know of a set workflow, but I do have a couple of 
>> resources to help you out.
>>
>> It looks like you may have found our Mapping ValueTrack Parameters to 
>> Report Fields 
>>  
>> guide 
>> as you were mapping the ValueTrack parameter to our report fields. 
>>
>> What you're seeing are criteria prefixes. We have a list of them here 
>> .
>>  
>> Please try taking a look at those to see if they match what you're seeing. 
>> If you need further help, feel free to reach out.
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Monday, October 9, 2017 at 5:59:07 PM UTC-4, Jonathan Clarke wrote:
>>>
>>> We've been working successfully with the AdWords API (Google Ads Python 
>>> Client Library: https://github.com/googleads/googleads-python-lib) for 
>>> a good while building internal reports for our application. Until, that is, 
>>> we hit placements…
>>>
>>> I define placements as anywhere an AdWords ad is shown. The placement 
>>> might be a domain, page, ad unit, app you name it! Placements are a very 
>>> broad definition.
>>>
>>> For our app to work for placements we need to join API spend data with 
>>> activity on our website.
>>>
>>> To do this we are running AdWords API reports and then collecting 
>>> session data using AdWords ValueTrack parameters.
>>>
>>> The ValueTrack parameters are easy enough, as there seems to be only 1 
>>> option: `{placement}`.
>>>
>>> However, it's on the API where things get interesting, the API has 
>>> numerous options for getting placement data. For example:
>>>
>>>- 
>>>
>>> https://developers.google.com/adwords/api/docs/reference/v201708/AdGroupCriterionService.MobileApplication
>>>   
>>>
>>>- 
>>>
>>> https://developers.google.com/adwords/api/docs/appendix/reports/url-performance-report
>>>- 
>>>
>>> https://developers.google.com/adwords/api/docs/appendix/reports/placement-performance-report#criteria
>>>- 
>>>
>>> 

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

In case you missed my private message, we don't have a solution for this, 
yet. I'll see if I can get someone else to look at it on my team.

Best,
Nadine, AdWords API Team

On Tuesday, October 10, 2017 at 10:28:39 AM UTC-4, Oksana Sulyma wrote:
>
> Hi guys,
> Any progress on this issue? Any idea will be helpful.
> Thanks!
> Oksana
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/a815f456-999f-4582-b638-341d8a83888c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch jobs stay in state processing for several hours and finally get cancelled

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Christian,

I'm pleased to hear that. Thanks for providing an update!

Cheers,
Nadine, AdWords API Team

On Tuesday, October 10, 2017 at 4:22:53 AM UTC-4, Christian wrote:
>
> Hi Nadine,
>
> just want to give an update from our side. We incrementally increased our 
> set-bid-operations-per-day limit again up to 400 000. At the same time we 
> reduced our batch jobs to have at most 10 000 operations (25 000) before. 
> So far everything looks good. Jobs usually complete in less than an hour 
> for large accounts, which is good enough for us.
>
> Best,
> Christian
>
> On Monday, September 18, 2017 at 11:24:18 PM UTC+2, Christian wrote:
>>
>> Hi Nadine,
>>
>> thanks for the update and for looking into this. For now we'll stay with 
>> our limit of not more than 100 000 set-bid operations per day as this seems 
>> to be a working scale. Still, I really appreciate it when you report some 
>> news here once you have them. Thanks again!
>>
>> Best,
>> Christian
>>
>> On Monday, September 18, 2017 at 6:54:52 PM UTC+2, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Greetings Christian!
>>>
>>> Here's an update on where we are on this. It turns out that the batch 
>>> job service attempts to send all the requests, but is internally getting 
>>> back a REQUEST_SIZE_LIMIT_EXCEEDED 
>>>  
>>> error. 
>>> That happens when there are more than 2000 operations in a normal service. 
>>> What batch job service is doing in the background is that it's breaking up 
>>> the request when that happens and then sends fewer requests. This is 
>>> happening so often that the batch job finally cancels itself. That does 
>>> appear to be an issue on our side because of this. We're exploring 
>>> solutions, but there isn't a solution, yet. I'll update you when we have 
>>> more information. At least we now know the root cause of your issue.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Friday, September 15, 2017 at 6:16:13 PM UTC-4, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Christian,

 Thanks for the update. I don't know of any code fixes that went in 
 within the last day.

 Batch job service can theoretically handle quite a few operations, but 
 even 1 000 000 is a lot when you think of all the updates that have to 
 happen on the back end. Some changes are more expensive than others and 
 take a bit longer because even though it looks like you're updating maybe 
 one field, there is logic that needs to check on things like if something 
 can be overridden at specific levels or if other objects in the account 
 will be affected by the change. That's why some things do take a bit 
 longer.

 Regards,
 Nadine, AdWords API Team 

 On Friday, September 15, 2017 at 2:38:51 PM UTC-4, Christian wrote:
>
> Hi Nadine,
>
> thanks for looking into that.
>
> Today we reduced the total number of set-max-cpc operations to be 
> below 100 000 and all 4 jobs (each at most 25 000 operations) completed 
> successfully within a few minutes. Is there already a fix live? Let me 
> know 
> if we should have a try again with a larger number of operations.
>
> In case it is helpful for debugging, here are the IDs of the jobs 
> successfully completed today: 565656811, 565639265, 565650926, 565663576.
>
> By the way: we also submit more than 1 000 000 bid modifier operations 
> each day. The corresponding jobs do not get cancelled but still require 
> several hours to complete. Do we have to limit our daily number of 
> operations here or is that something the batch job service should be able 
> to handle faster in theory? An example job ID would be 565684901.
>
> Best regards,
> Christian
>
> On Friday, September 15, 2017 at 3:48:31 PM UTC+2, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Christian,
>>
>> I've taken a look into what's happening, and initially I don't see a 
>> root cause. My team will dig further into it, and I'll get back to you 
>> when 
>> I have the reason as to why these jobs are not successful.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, September 14, 2017 at 4:31:01 PM UTC-4, Christian wrote:
>>>
>>> Hi Shwetha,
>>>
>>> > If the submitted operations encounter an error during execution, 
>>> the results in the downloadUrl 
>>> 
>>>  should 
>>> contain the list of processingErrors 
>>> 
>>>  on 
>>> the batch job
>>>
>>> The problem here is that most of the cancelled jobs have no error 
>>> information -- neither in the 

Re: Best practice for joining AdWords API placement data with AdWords ValueTrack placement data?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Jonathan,

Unfortunately, I don't know of a set workflow, but I do have a couple of 
resources to help you out.

It looks like you may have found our Mapping ValueTrack Parameters to 
Report Fields 
 
guide 
as you were mapping the ValueTrack parameter to our report fields. 

What you're seeing are criteria prefixes. We have a list of them here 
.
 
Please try taking a look at those to see if they match what you're seeing. 
If you need further help, feel free to reach out.

Cheers,
Nadine, AdWords API Team

On Monday, October 9, 2017 at 5:59:07 PM UTC-4, Jonathan Clarke wrote:
>
> We've been working successfully with the AdWords API (Google Ads Python 
> Client Library: https://github.com/googleads/googleads-python-lib) for a 
> good while building internal reports for our application. Until, that is, 
> we hit placements…
>
> I define placements as anywhere an AdWords ad is shown. The placement 
> might be a domain, page, ad unit, app you name it! Placements are a very 
> broad definition.
>
> For our app to work for placements we need to join API spend data with 
> activity on our website.
>
> To do this we are running AdWords API reports and then collecting session 
> data using AdWords ValueTrack parameters.
>
> The ValueTrack parameters are easy enough, as there seems to be only 1 
> option: `{placement}`.
>
> However, it's on the API where things get interesting, the API has 
> numerous options for getting placement data. For example:
>
>- 
>
> https://developers.google.com/adwords/api/docs/reference/v201708/AdGroupCriterionService.MobileApplication
>   
>
>- 
>
> https://developers.google.com/adwords/api/docs/appendix/reports/url-performance-report
>- 
>
> https://developers.google.com/adwords/api/docs/appendix/reports/placement-performance-report#criteria
>- 
>
> https://developers.google.com/adwords/api/docs/appendix/reports/automatic-placements-performance-report#domain
>- 
>
> https://developers.google.com/adwords/api/docs/reference/v201708/AdGroupCriterionService
>
> After spending some time going back and forth on the various options, and 
> burning lots of dev time, we've come to the conclusion that there must be 
> some best practice advice out there for joining placement data from the API 
> and ValueTrack. One that works for all types of placements, including:
>
>  - Websites
>  - Apps
>  - AdSense
>  - Blogspot
>  - AMP
>
> An example of where we are running into a matching problem is "
> 10060.android.com.nytimes.android.adsenseformobileapps.com"... this is a 
> placement we see coming in from ValueTrack but has no match in any of our 
> spend reports. (In fact there are many many adsenseformobileapps.com 
> traffic sources for which there are no spend items).
>
> Also seeing strings like "mobileapp::2-com.mobilesrepublic.appy".  These 
> show up on our spend side but only appear in our ValueTrack around 10% of 
> the time.  Some match.  The vast majority don't.
>
> A definitive workflow on this would be SO useful for ourselves and no 
> doubt other users…
>
> Thanks!
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/a06b909b-b665-42da-9909-e3b98a89a963%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issues with BatchJobService - jobs remain stuck

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Roger,

Could you please open a new forum thread for this? This one is pretty old, 
and it really helps to have a new forum thread for a new issue.

Thanks,
Nadine, AdWords API Team

On Tuesday, October 3, 2017 at 9:29:57 AM UTC-4, ro...@growth-rocket.com 
wrote:
>
> Hi Nadine,
>
> Can you check this Batch Job Id:575510402
>
> My first batch job, its been 4 hrs and status did not change. 
>
> On Tuesday, February 21, 2017 at 11:20:12 PM UTC+8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hi Stefan,
>>
>> Thanks for the update! I'm keeping an eye on this as well.
>>
>> Take care,
>> Nadine, AdWords API Team
>>
>> On Saturday, February 18, 2017 at 1:43:38 AM UTC-5, Stefan Kleine 
>> Stegemann wrote:
>>>
>>>
>>> Hi Nadine,
>>>
>>> good news on our side as well. Today, we did not have stuck jobs any 
>>> more and all jobs have been processed in time as they have before this 
>>> issue. We did decrease the batch job size to 20k though, I don't know 
>>> whether this relevant or not. Furthermore, I've checked a couple of jobs 
>>> from the past days and they all are canceled now.
>>>
>>> At the moment, it looks like the issue is solved. We'll keep an I on it 
>>> and let you know if it happens again. Thanks for taking care of this and 
>>> your constant updates on this issue.
>>>
>>> Best,
>>> Stefan
>>>
>>> Am Freitag, 17. Februar 2017 23:28:11 UTC+1 schrieb Nadine Sundquist 
>>> (AdWords API Team):

 Hello Stefan,

 I have good news! We've been working through processing through the 
 queue of hanging jobs. You should be seeing an improvement in that these 
 hanging jobs should be reaching a final state e.g. canceling should now be 
 canceled. You may still see a few hanging, but the majority should have 
 reached a final state. We're still working on fixing the root cause.

 Take care,
 Nadine, AdWords API Team

 On Friday, February 17, 2017 at 1:47:04 PM UTC-5, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hi Stefan,
>
> We're actively working on clearing the queue, which includes those 
> jobs in the canceling state, as we're searching for a fix for this. 
> Unfortunately, it won't make a difference whether or not it's a small job 
> versus a larger job. One of my teammates put it quite well when he said 
> that a larger job may have a higher chance of getting stuck, but on the 
> other hand when it does go through, it gets through more operations. Just 
> so you know, when a job is in a canceling state, it will not execute any 
> more operations, so you can submit the rest of the operations that did 
> not 
> execute in that canceling job. It might take awhile for the job to reach 
> a 
> canceled state, but at least it won't execute any more operations. I 
> realize this isn't optimal, but I do want you to know that is of higher 
> priority to us. It's just really tricky trying to find a solution for 
> what 
> you're seeing. I'll get back to you as we make more progress. Thanks 
> again 
> for providing so much helpful information!
>
> Cheers,
> Nadine, AdWords API Team
>
> On Friday, February 17, 2017 at 3:29:54 AM UTC-5, Stefan Kleine 
> Stegemann wrote:
>>
>>
>> Hi Nadine,
>>
>> still no improvement, today we have 28 stuck batch jobs across seven 
>> adwords accounts. I also checked a sample of 10 batch jobs out of the 
>> ones 
>> we have canceled over the past days and 2 jobs are actually canceled but 
>> 8 
>> are still in state canceling. As this issue is present for four days 
>> now, 
>> it becomes more critical for us because we are unable to deliver the 
>> full 
>> service to some of our customers. Thus, any advise for how the deal with 
>> the "broken" batch jobs is appreciated. Does it, for example, make sense 
>> to 
>> try smaller or larger jobs?
>>
>> Best,
>> Stefan
>>
>> Am Donnerstag, 16. Februar 2017 23:23:22 UTC+1
>>  schrieb Nadine Sundquist (AdWords API Team):
>>>
>>> Greetings Stefan,
>>>
>>> This is useful information when we're trying to figure out how to 
>>> find a solution for this one. Thanks for passing it along. If jobs have 
>>> been finishing for you normally by a certain time, then I would expect 
>>> it 
>>> to continue to do so. If it doesn't, then it's probably fallen into the 
>>> issue that we're working on. I'll continue to track this so we can find 
>>> a 
>>> solution.
>>>
>>> Regards,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, February 16, 2017 at 4:52:15 PM UTC-5, Stefan Kleine 
>>> Stegemann wrote:


 Hi Nadine,

 Thanks for the update, we canceled the jobs from this morning as 
 well. While doing so, we observed that for some jobs, it was not 
 possible 

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

This really is a tough one to figure out. I'm working on pulling in some 
more people to try to help on this. Thank you for bumping the thread; it 
helps me explain the priority of this.

Best,
Nadine, AdWords API Team

On Monday, October 2, 2017 at 5:54:53 AM UTC-4, Oksana Sulyma wrote:
>
> Hi guys,
> Any news on this? We really need any ideas on how to get this working as 
> clients get anxious. Thanks you for any help!
>
> On Tuesday, September 12, 2017 at 5:52:28 PM UTC+3, Oksana Sulyma wrote:
>>
>> Hi guys,
>> I'm requesting 
>> https://adwords.google.com/api/adwords/mcm/v201702/CustomerService and 
>> getting the next error:
>>
>> soap:ServerInternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroInternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>>  
>> @ 
>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErroApiExceptionInternalApiError.UNEXPECTED_INTERNAL_API_ERRORInternalApiErrorUNEXPECTED_INTERNAL_API_ERROR
>>
>>
>> curl_info is next:
>> ( [url] => 
>> https://adwords.google.com/api/adwords/mcm/v201702/CustomerService 
>> [content_type] => text/xml; charset=UTF-8 [http_code] => 500 [header_size] 
>> => 420 [request_size] => 858 [filetime] => -1 [ssl_verify_result] => 0 
>> [redirect_count] => 0 [total_time] => 121.246653 [namelookup_time] => 
>> 0.004202 [connect_time] => 0.287567 [pretransfer_time] => 0.87369 
>> [size_upload] => 536 [size_download] => 1103 [speed_download] => 9 
>> [speed_upload] => 4 [download_content_length] => -1 [upload_content_length] 
>> => 536 [starttransfer_time] => 121.246455 [redirect_time] => 0 
>> [redirect_url] => [primary_ip] => 173.194.222.100 [certinfo] => Array ( ) 
>> [primary_port] => 443 [local_ip] => 10.99.99.22 [local_port] => 37912 )
>>
>> my xml looks next:
>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:v20="
>> https://adwords.google.com/api/adwords/mcm/v201702; xmlns:v201="
>> https://adwords.google.com/api/adwords/cm/v201702;>
>>
>>   
>>  mytoken
>>  myagent
>>   
>>
>>
>>   
>>
>> 
>>
>> This code works for lots of different Adwords accounts, getting SOAP 
>> error just for one - can send details on it.
>>
>> Repeating the request doesn't help. Really need any input which can help 
>> to troubleshoot. Thanks!  
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/8370f581-c739-41f5-b789-cf4c7472f58f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Misspelling of new city name.

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings André,

I would be glad to clarify! I can see how it would be confusing. The ç 
characters is considered an extended ASCII character already. It's just not 
a part of the original printable set. I first wanted to clarify that when I 
was talking about ASCII characters earlier in the thread. You're lucky that 
I'm interested in linguistics and travel because I happen to know the 
answer to this one. Yes, you are very likely correct in that it is trying 
to preserve phonetics. Many English speakers would not recognize the sound 
that this character would make, so I've observed it changes to an 's' or a 
'ss' to help someone pronounce it correctly. That may not always be the 
case for every location in the world, but it definitely appears to be the 
case for this location.

Take care,
Nadine, AdWords API Team

On Friday, September 29, 2017 at 11:59:35 AM UTC-4, Andre Tannus wrote:
>
> I can't say I understand. Wouldn't 'Acu' be the ASCII version of 'Açu'? Or 
> is there an effort to preserve phonetics?
>
>
> On Fri, Sep 29, 2017 at 10:49 AM, 'Nadine Sundquist (AdWords API Team)' 
> via AdWords API Forum <adwords-api@googlegroups.com> wrote:
>
>> Hello André,
>>
>> I have good news! It's not conflicting with Google Maps. I've attached a 
>> screenshot of the place in Google Maps. The place may have Açu, but if you 
>> look underneath it, you'll see that the official name that Google Maps is 
>> keying off of is the same as what you're seeing in API geotargets. You're 
>> probably wondering why this happens. If you look through the geotargets 
>> list, you'll see that everything is using ASCII. For example, you don't see 
>> Moscow in the Russian language, and you don't see Beijing in the Chinese 
>> language. The Açu spelling is considered to be in the local language with 
>> the 'ç' character in there. For geotargets, all the names are changed to 
>> match an ASCII standard for that location. I hope that clears that up for 
>> you!
>>
>> Best,
>> Nadine Sundquist, AdWords API Team
>>
>> P.S. I totally love that you cited Google Trends. Very cool!
>>
>> On Thursday, September 28, 2017 at 4:30:49 PM UTC-4, Andre Tannus wrote:
>>>
>>>
>>> Hi everyone.
>>>
>>> I've just updated my list of API Geotargets with the file available here:
>>>
>>> https://developers.google.com/adwords/api/docs/appendix/geotargeting
>>>
>>> It contains a new city record:
>>>
>>> 9047706,Assu,"Assu,State of Rio Grande do 
>>> Norte,Brazil",20103,BR,City,Active
>>>
>>> with the city is misspelled.
>>>
>>> The correct spelling according to current portuguese spelling rules 
>>> <https://pt.wikipedia.org/wiki/Assu#Topon.C3.ADmia>, IBGE 
>>> <https://cidades.ibge.gov.br/brasil/rn/acu/panorama>, Wikipedia 
>>> <https://pt.wikipedia.org/wiki/Assu> (despite the title) and even Google 
>>> Maps 
>>> <https://www.google.com.br/maps/place/A%C3%A7u,+Assu+-+State+of+Rio+Grande+do+Norte,+59650-000/@-5.5791717,-36.9236919,15.25z/data=!4m5!3m4!1s0x7b0f2592da58feb:0x78da3ff6e4016c42!8m2!3d-5.5774536!4d-36.9147407?hl=en>
>>>  
>>> is "Açu".
>>>
>>> Perhaps there is a good reason (profuse use of the wrong spelling 
>>> <https://trends.google.com/trends/explore?date=all=BR=Assu,A%C3%A7u>) 
>>> for this decision, or perhaps it is a bug.
>>>
>>> Is this the proper place to report such a thing?
>>>
>>> Thanks in advance,
>>> André.
>>>
>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> 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+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 a topic in the 
>> Google Groups "AdWords API Forum" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/adwords-api/vbDzHzss7Xo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> adwords-api+unsubscr...@googlegroups.com.
&g

Re: BatchJob getting cancelled (Internal Error)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I don't see anything obvious at first glance with your request. I'm pulling 
someone in on my team to get a second set of eyes on this. I'll get back to 
you when we figure out what's going on.

Best,
Nadine, AdWords API Team 

On Thursday, September 28, 2017 at 5:39:05 AM UTC-4, 
aanchal.khandel...@go-mmt.com wrote:
>
> All my batch jobs are failing. I have tried with mere 5k operations as 
> well as some 11k operations. Every time the batch job gets cancelled 
> stating BatchJobProcessingError.INTERNAL_ERROR. Batch job is 572804866. 
>
> Please help. 
>
> ::DISCLAIMER::
>
>
> 
>
>
> This message is intended only for the use of the addressee and may contain 
> information that is privileged, confidential and exempt from disclosure 
> under applicable law. If the reader of this message is not the intended 
> recipient, or the employee or agent responsible for delivering the message 
> to the intended recipient, you are hereby notified that any dissemination, 
> distribution or copying of this communication is strictly prohibited. If 
> you have received this e-mail in error, please notify us immediately by 
> return e-mail and delete this e-mail and all attachments from your system.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/b3df117f-cad1-4124-abb7-b24e79c48df4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot get all managed customers with java library: 在文件元素內容中找到無效的 XML 字元 (Unicode: 0x8)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I found the issue, and it's a tricky one. The good thing is that the 
request you are making to the API is successful, so there is nothing wrong 
with your request. The issue is what is being returned. You are 
successfully getting a response. However, that response has hidden 
characters in it. When Java tries to parse it, it considers those hidden 
characters as invalid XML characters, and that is where you are getting the 
errors. I found one of the reasons, but there may be more than one reason. 
I'll send you the account with the hidden character issue in a separate, 
private email. I just wanted to make sure that people reading the forum in 
the future know to look for hidden characters when this happens.

Best,
Nadine, AdWords API Team

On Monday, September 25, 2017 at 11:46:07 PM UTC-4, 郭文豪 wrote:
>
> Request
> 
>
>
> 11:21:04.739 [main] INFO 
> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger - 
> SOAP request:
> 
> http://schemas.xmlsoap.org/soap/envelope/; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance;>
> 
> https://adwords.google.com/api/adwords/mcm/v201708; 
> soapenv:mustUnderstand="0">
> https://adwords.google.com/api/adwords/cm/v201708
> ">client-customer-id
> https://adwords.google.com/api/adwords/cm/v201708
> ">REDACTED
> https://adwords.google.com/api/adwords/cm/v201708;>unknown (AwApi-Java, 
> AdWords-Axis/3.8.0, Common-Java/3.8.0, Axis/1.4, Java/1.8.0_101, maven, 
> SelectorBuilder)
> https://adwords.google.com/api/adwords/cm/v201708
> ">false
> https://adwords.google.com/api/adwords/cm/v201708
> ">false
> 
> 
> 
> https://adwords.google.com/api/adwords/mcm/v201708;>
> 
> https://adwords.google.com/api/adwords/cm/v201708;>CustomerId
> https://adwords.google.com/api/adwords/cm/v201708;>Name
> https://adwords.google.com/api/adwords/cm/v201708;>
> 1040
> 20
> 
> 
> 
> 
> 
>
>
> Response
> 
>
> 11:21:04.739 [main] INFO 
> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger - 
> SOAP response:
> 
> http://schemas.xmlsoap.org/soap/envelope/; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance;>
> 
> 
> soapenv:Server.userException
> org.xml.sax.SAXParseException; lineNumber: 1; 
> columnNumber: 816; 在文件元素內容中找到無效的 XML 字元 (Unicode: 0x8)。
> 
>  xmlns:ns1="http://xml.apache.org/axis/;>org.xml.sax.SAXParseException; 
> lineNumber: 1; columnNumber: 816; 在文件元素內容中找到無效的 XML 字元 (Unicode: 0x8)。
> at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> at 
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1465)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2920)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118)
> at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:504)
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
> at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
> at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at 
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
> at 
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327)
> at 
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
> at 
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
> at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
> at 
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
> at 

Re: Cannot process batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Stefano,

Thanks for reporting this with such great detail. Thanks to people like 
you, we were able to find a more systemic issue. Many of the batch jobs 
were not processing properly. They should be functioning fine now. Please 
get back to me if you're still experiencing issues with your batch jobs.

Best,
Nadine, AdWords API Team

On Friday, September 22, 2017 at 3:48:25 PM UTC-4, Stefano Fontana wrote:
>
> Since 1 hour I am not able to complete any batch jobs
> Example id: 570369758, 570737388
>
> I only have few operations:
> ADD: AdGroupAd: 4 - AdGroupCriterion: 23 - AdGroup: 1
> SET: AdGroup: 1
> REMOVE: AdGroupAd: 2
>
>
> Can you please have a look?  Usually cancelling and retrying was working 
> but now even that doesn't work anymore
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/ff8d3662-305f-48d1-a897-966fe8cfe0e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Universal App Campaigns Reporting

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Yuval,

I just did a check to see if there is anything in the works, and I don't 
currently see any plans to add UACs to these reports. I've put in a feature 
request for these reports to include UACs. Please keep an eye on our blog 
 for any updates. Thanks for 
bringing this up!

Best,
Nadine, AdWords API Team

On Thursday, September 21, 2017 at 3:53:30 PM UTC-4, yu...@singular.net 
wrote:
>
> Hey Adwords API team,
> I recently encountered the following blog post: 
> http://googleadsdeveloper.blogspot.co.il/2017/09/upgrade-to-adwords-universal-app.html
>
> Since you're changing all mobile app campaigns to UAC, most of the 
> campaign reporting capabilities won't work (at least not with the current 
> reporting API version).
> According to your documentation, UAC campaigns aren't available in the 
> following ad hoc reports:
>
> 1. GEO_PERFORMANCE_REPORT
> 2. KEYWORD_PERFORMANCE_REPORT
> 3. PALCEMENT_PERFORMANCE_REPORT
> 4. AD_PERFORMANCE_REPORT
>
> These reports provide us (and our customers) vital information about the 
> progress of their campaigns in several segmentations.
>
> Along with the upcoming change in the campaign types in November, are you 
> planning on improving the measurement reporting on UAC campaigns? 
> Will it be possible to pull country / keyword / placement / adgroup / ad 
> level statistics on UAC campaigns in the next API release? 
> Please shed some light if possible on these issues, since it is extremely 
> important to us.
>
> Thanks,
> Yuval
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/d6e26de4-1937-46cf-b429-a1ac285f6e81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

I accidentally set my net a little too wide when checking what's associated 
with that email. It's associated with only a few AdWords accounts as you 
pointed out, and it's associated with a lot of other non-AdWords accounts. 
That's where the confusion came in. You pointing that out has helped me 
narrow it down a bit. I'm working with one of my teammates to figure out 
who has an expertise in this area. This one is tough to figure out, so I'll 
get back to you as soon as we've gotten further in tracking this down.

Cheers,
Nadine, AdWords API Team

On Thursday, September 21, 2017 at 2:11:17 PM UTC-4, Oksana Sulyma wrote:
>
> Hi guys!
>
>
> You write on my problem:
>
> " That email is associated with over 200 AdWords accounts. Usually, the 
> max that we see is 5 AdWords accounts. I traced down the error on our end, 
> and and it looks like it's timing out as it's trying to retrieve all the 
> accounts associated with that email address." 
>
>
> Client had a clarification question:
>
> "By accounts—can you confirm that it not child accounts being referenced? 
> Google only allows 5 accounts under an email and I have like 3 total. I do 
> have a lot of child accounts but the problem never occurred until recently 
> and I have added anything that new. Let me know and I can try and 
> troubleshoot."
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/11951dbe-abbc-444b-a7fb-8c9fac953287%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Abnormally high number of cancelled/failed batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Jordan,

So, I now have a reason for why the most recent jobs are failing. In short, 
you've found a limitation of batch job service and brought it to its 
limits. Product partition operations for the same ad group must be 
submitted together and can't be broken up. The problem is that on the 
back-end, while we are processing them, we're getting back a 
REQUEST_SIZE_LIMIT_EXCEEDED error meaning they can't be submitted as a 
block. Usually, when batch job service gets this kind of error, it silently 
retries with fewer operations, but that is not possible for product 
partitions. So, the job fails. Thanks for bringing this to light, and we're 
exploring a few ways to solve this. In the meantime, please try submitting 
fewer product partition operations at a time. I'll update you when I have 
more, but this looks like it could be a tough one to solve, so it's not one 
of those issues that can be solved overnight.

Best,
Nadine, AdWords API Team

On Tuesday, September 19, 2017 at 4:14:29 PM UTC-4, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Jordan,
>
> This issue looks a bit different. Usually no results back means there was 
> an unrecoverable error. At this point, I'm not sure what that is. I'll hunt 
> that down for you to figure out what's going on. I'll get back to you when 
> I have the reason.
>
> Regards,
> Nadine, AdWords API Team
>
> On Tuesday, September 19, 2017 at 6:11:24 AM UTC-4, jor...@jcrocker.uk 
> wrote:
>>
>> Hi Nadine,
>>
>> Sorry to open this thread again but we are experiencing the same problem 
>> again.
>>
>> Example Job ID's:
>>
>> 567961108
>> 568327521
>>
>> I believe the number of partition operations is under the prescribed 
>> limit, but the jobs are going straight to cancelled and not providing any 
>> error messages.
>>
>> Please can you advise urgently.
>>
>> Kind regards,
>> Jordan
>>
>> On Wednesday, August 16, 2017 at 8:16:56 AM UTC+1, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Greetings All,
>>>
>>> I've filed an issue on this so we can dive deeper into why this is 
>>> happening. I'll get back to you when we've made more progress on why this 
>>> is happening again.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Wednesday, August 16, 2017 at 12:15:08 AM UTC+8, GregT wrote:

 We also are. Here are a few sample job ids from us, in case it helps:

 546629438
 546628553
 546690922
 546964719
 546610328
 546608684
 546962208
 546611558
 546606977
 546961335
 546605693
 546959982
 546959979
 546958008
 546956727
 546676590
 546676494
 546676485
 546676170
 546354463
 546353035
 546338374
 546338884
 546338836

 Thanks,
 Greg

 On Tuesday, August 15, 2017 at 3:57:05 AM UTC-5, jor...@jcrocker.uk 
 wrote:
>
> Hello Nadine,
>
> We are experiencing this problem again, with the following sample jobs 
> IDs:
>
> 546679208
> 546680861
> 546680843
> 546739639
> 546680837
> 546740809
> 546740803
> 546738088
> 546740836
> 546679832
> 546680852
> 546739642
> 546738997
> 547027008
> 546680846
> 546680882
> 546738103
> 546740464
> 546740800
> 546679220
> 546740467
> 546740839
> 547027005
> 546679214
> 546740797
> 546740812
> 546680849
> 546679205
> 546679217
> 546679835
>
>
> Thanks for your help.
>
> Kind regards,
> Jordan
>
> On Thursday, July 6, 2017 at 2:45:53 PM UTC+1, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Simon,
>>
>> The fix is now on our production servers. Please give it another try. 
>> If you're still experiencing issues, please get back to me.
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Wednesday, July 5, 2017 at 8:23:27 AM UTC-4, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hello Simon,
>>>
>>> It looks like we have found the root cause. Now that the holidays 
>>> are winding down here in the US, we can look at trying to find a 
>>> solution. 
>>> I'll keep you in the loop.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Wednesday, July 5, 2017 at 5:32:44 AM UTC-4, si...@hotsnapper.com 
>>> wrote:

 Hello Nadine, 

 I am working alongside Jordan do we have an update?

 Regards

 Simon



 On Tuesday, June 27, 2017 at 10:18:31 PM UTC+1, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hello Jordan,
>
> I took a look on our servers, and at first glance it does look 
> like it could be the same issue. I've sent on the job IDs to my 
> teammate 
> who's assigned to this. I'll get back to you when I hear back. This 
> looks 
> like a 

Re: isExemptable does not become false

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi,

I was able to confirm that you are totally correct. The example does only 
go through the first exemption request. You'll have to modify the code to 
include every exemption request. Right now, there is a line that says:

$operation->setExemptionRequests(
> [new ExemptionRequest($error->getKey())]);
>

That line of code only sets one exemption request per operation. In your 
case, you need to pass multiple exemption requests by iterating over all 
the exemption requests for that ad. In the meantime, we're looking at 
fixing the example. It may take time to push a fix, so I would suggest 
modifying your code. Thanks for pointing out the issue with our example!

Regards,
Nadine, AdWords API Team

On Tuesday, September 19, 2017 at 6:47:46 PM UTC-4, Hideichi Saito wrote:
>
> Thank you for your reply.
> Thank you for your attentive response.
>
> I will also test it repeatedly.
>
>
> 2017年9月20日水曜日 4時22分57秒 UTC+9 Nadine Sundquist (AdWords API Team):
>>
>> Greetings!
>>
>> Thanks for clarifying all of this. That does make sense. I'm not a PHP 
>> expert, but it does look like the code is only including the first 
>> exemption request for each ad. I'm getting in touch with our PHP client 
>> library owner to verify that this is the case. I'll get back to you when I 
>> get an answer.
>>
>> Regards,
>> Nadine, AdWords API Team
>>
>> On Monday, September 18, 2017 at 8:34:34 PM UTC-4, Hideichi Saito wrote:
>>>
>>> thank you for your reply.
>>>
>>> Yes. Only one exception request is sent.
>>>
>>> As shown in var_dump ($ error);
>>> PolicyViolationError.isExemptable, is true.
>>>
>>> I will attach the contents of $ operations.
>>>
>>> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201705/ErrorHandling/HandlePolicyViolationError.php
>>> line:129. Set up and get var_dump ($operations);
>>>
>>> array(1) {
>>>   [0]=>
>>>   object(Google\AdsApi\AdWords\v201705\cm\AdGroupAdOperation)#117 (5) {
>>> ["operand":protected]=>
>>> object(Google\AdsApi\AdWords\v201705\cm\AdGroupAd)#116 (8) {
>>>   ["adGroupId":protected]=>
>>>   string(11) "47899933378"
>>>   ["ad":protected]=>
>>>   object(Google\AdsApi\AdWords\v201705\cm\ExpandedTextAd)#113 (18) {
>>> ["headlinePart1":protected]=>
>>> string(44) "高力レリーPRバー"
>>> ["headlinePart2":protected]=>
>>> string(26) "WEB広も時稿!"
>>> ["description":protected]=>
>>> string(104) "無でレリー配＆WEB広出新ースPRバー」をリス
>>> ["path1":protected]=>
>>> NULL
>>> ["path2":protected]=>
>>> NULL
>>> ["id":protected]=>
>>> NULL
>>> ["url":protected]=>
>>> NULL
>>> ["displayUrl":protected]=>
>>> NULL
>>> ["finalUrls":protected]=>
>>> array(1) {
>>>   [0]=>
>>>   string(28) "https://pr-bazooka.com/about;
>>> }
>>> ["finalMobileUrls":protected]=>
>>> NULL
>>> ["finalAppUrls":protected]=>
>>> NULL
>>> ["trackingUrlTemplate":protected]=>
>>> NULL
>>> ["urlCustomParameters":protected]=>
>>> NULL
>>> ["urlData":protected]=>
>>> NULL
>>> ["type":protected]=>
>>> NULL
>>> ["devicePreference":protected]=>
>>> NULL
>>> ["AdType":protected]=>
>>> NULL
>>> ["parameterMap":"Google\AdsApi\AdWords\v201705\cm\Ad":private]=>
>>> array(1) {
>>>   ["Ad.Type"]=>
>>>   string(6) "AdType"
>>> }
>>>   }
>>>   ["status":protected]=>
>>>   NULL
>>>   ["policySummary":protected]=>
>>>   NULL
>>>   ["labels":protected]=>
>>>   NULL
>>>   ["baseCampaignId":protected]=>
>>>   NULL
>>>   ["baseAdGroupId":protected]=>
>>>   NULL
>>>   ["forwardCompatibilityMap":protected]=>
>>>   NULL
>>> }
>>> ["exemptionRequests":protected]=>
>>> array(1) {
>>>   [0]=>
>>>   object(Google\AdsApi\AdWords\v201705\cm\ExemptionRequest)#150 (1) {
>>> ["key":protected]=>
>>> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationKey)#142 
>>> (2) {
>>>   ["policyName":protected]=>
>>>   string(7) "weapons"
>>>   ["violatingText":protected]=>
>>>   string(7) "bazooka"
>>> }
>>>   }
>>> }
>>> ["operator":protected]=>
>>> string(3) "ADD"
>>> ["OperationType":protected]=>
>>> NULL
>>> 
>>> ["parameterMap":"Google\AdsApi\AdWords\v201705\cm\Operation":private]=>
>>> array(1) {
>>>   ["Operation.Type"]=>
>>>   string(13) "OperationType"
>>> }
>>>   }
>>> }
>>>
>>>
>>>
>>>
>>> 2017年9月19日火曜日 7時35分53秒 UTC+9 Nadine Sundquist (AdWords API Team):

 Hello,

 I want to make sure I understand your question. I see that you sent me 
 the response with each error. Each error says that it is exemptable. Are 
 you saying that the code example is only sending one of the exemptions, 
 and 
 

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oksana,

Using the current credentials that you're using, I don't know of a way of 
doing that. We're still trying to figure how things got in this state. You 
do have a few possible workarounds:

   - *Option 1:* The email you sent us earlier is associated with a lot of 
   accounts. If you don't need that email associated with so many accounts, 
   then try removing it from those accounts. Then there will be fewer accounts 
   coming back. In this Help Center article 
   <https://support.google.com/adwords/answer/6372672>, there are 
   instructions on how to remove emails from an account.
   - *Option 2:* Using another email that has access to the accounts you 
   care about, generate another set of credentials. Then, use those 
   credentials to make calls.

Best,
Nadine, AdWords API Team

On Tuesday, September 19, 2017 at 6:32:31 AM UTC-4, Oksana Sulyma wrote:
>
> Hi Nadine,
>
> Thanks for the reply. The problem is we use CustomerService getCustomers 
> to get the list of customer IDs. And we get UNEXPECTED_INTERNAL_API_ERROR 
> on this stage. Is there any other automatic way to know customer IDs? 
>
> Thanks!
>
> Oksana
>
> On 19.09.17 01:40, 'Nadine Sundquist (AdWords API Team)' via AdWords API 
> Forum wrote:
>
> Hi Oksana, 
>
> Thanks for bumping this thread. We're still looking into this. Have you 
> had a chance to try out the solution of putting the client customer ID in 
> the header to limit the number of users coming back as explained in this 
> blog post 
> <http://www.google.com/url?q=http%3A%2F%2Fgoogleadsdeveloper.blogspot.com%2F2016%2F10%2Faccess-multiple-adwords-accounts-with.html=D=1=AFQjCNEH3SX6FPsDXB-yFWRQ5BkOGKUxLg>?
>  
> I'm hoping that will at least be a workaround while we get to the bottom of 
> this.
>
> Thanks,
> Nadine, AdWords API Team
>
> On Monday, September 18, 2017 at 6:39:56 AM UTC-4, Oksana Sulyma wrote: 
>>
>> Any news on this? Thanks!
>>
>> On Wednesday, September 13, 2017 at 3:10:20 PM UTC+3, Oksana Sulyma 
>> wrote: 
>>>
>>> Sent details in private message. Thanks!
>>>
>>> On Tuesday, September 12, 2017 at 8:06:47 PM UTC+3, Shwetha Vastrad 
>>> (AdWords API Team) wrote: 
>>>>
>>>> Hi, 
>>>>
>>>> Could you provide the email address which was used to authorize the 
>>>> request along with the complete SOAP request and response logs? Please use 
>>>> *Reply 
>>>> privately to author* when responding. 
>>>>
>>>> Thanks,
>>>> Shwetha, 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+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 a topic in the 
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/adwords-api/1oR9kPSQ3Ls/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> adwords-api+unsubscr...@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/9f052817-f69c-4a8f-9ea7-c9fba9b3ab63%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/adwords-api/9f052817-f69c-4a8f-9ea7-c9fba9b3ab63%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/2cc032c6-c8f7-4b67-b3cd-13ab88e66605%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Abnormally high number of cancelled/failed batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Jordan,

This issue looks a bit different. Usually no results back means there was 
an unrecoverable error. At this point, I'm not sure what that is. I'll hunt 
that down for you to figure out what's going on. I'll get back to you when 
I have the reason.

Regards,
Nadine, AdWords API Team

On Tuesday, September 19, 2017 at 6:11:24 AM UTC-4, jor...@jcrocker.uk 
wrote:
>
> Hi Nadine,
>
> Sorry to open this thread again but we are experiencing the same problem 
> again.
>
> Example Job ID's:
>
> 567961108
> 568327521
>
> I believe the number of partition operations is under the prescribed 
> limit, but the jobs are going straight to cancelled and not providing any 
> error messages.
>
> Please can you advise urgently.
>
> Kind regards,
> Jordan
>
> On Wednesday, August 16, 2017 at 8:16:56 AM UTC+1, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Greetings All,
>>
>> I've filed an issue on this so we can dive deeper into why this is 
>> happening. I'll get back to you when we've made more progress on why this 
>> is happening again.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Wednesday, August 16, 2017 at 12:15:08 AM UTC+8, GregT wrote:
>>>
>>> We also are. Here are a few sample job ids from us, in case it helps:
>>>
>>> 546629438
>>> 546628553
>>> 546690922
>>> 546964719
>>> 546610328
>>> 546608684
>>> 546962208
>>> 546611558
>>> 546606977
>>> 546961335
>>> 546605693
>>> 546959982
>>> 546959979
>>> 546958008
>>> 546956727
>>> 546676590
>>> 546676494
>>> 546676485
>>> 546676170
>>> 546354463
>>> 546353035
>>> 546338374
>>> 546338884
>>> 546338836
>>>
>>> Thanks,
>>> Greg
>>>
>>> On Tuesday, August 15, 2017 at 3:57:05 AM UTC-5, jor...@jcrocker.uk 
>>> wrote:

 Hello Nadine,

 We are experiencing this problem again, with the following sample jobs 
 IDs:

 546679208
 546680861
 546680843
 546739639
 546680837
 546740809
 546740803
 546738088
 546740836
 546679832
 546680852
 546739642
 546738997
 547027008
 546680846
 546680882
 546738103
 546740464
 546740800
 546679220
 546740467
 546740839
 547027005
 546679214
 546740797
 546740812
 546680849
 546679205
 546679217
 546679835


 Thanks for your help.

 Kind regards,
 Jordan

 On Thursday, July 6, 2017 at 2:45:53 PM UTC+1, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hello Simon,
>
> The fix is now on our production servers. Please give it another try. 
> If you're still experiencing issues, please get back to me.
>
> Thanks,
> Nadine, AdWords API Team
>
> On Wednesday, July 5, 2017 at 8:23:27 AM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Simon,
>>
>> It looks like we have found the root cause. Now that the holidays are 
>> winding down here in the US, we can look at trying to find a solution. 
>> I'll 
>> keep you in the loop.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Wednesday, July 5, 2017 at 5:32:44 AM UTC-4, si...@hotsnapper.com 
>> wrote:
>>>
>>> Hello Nadine, 
>>>
>>> I am working alongside Jordan do we have an update?
>>>
>>> Regards
>>>
>>> Simon
>>>
>>>
>>>
>>> On Tuesday, June 27, 2017 at 10:18:31 PM UTC+1, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Jordan,

 I took a look on our servers, and at first glance it does look like 
 it could be the same issue. I've sent on the job IDs to my teammate 
 who's 
 assigned to this. I'll get back to you when I hear back. This looks 
 like a 
 tough one. Thank you for providing these job IDs.

 Take care,
 Nadine, AdWords API Team

 On Tuesday, June 27, 2017 at 5:25:31 AM UTC-4, jor...@jcrocker.uk 
 wrote:
>
> Hi Nadine,
>
> I am currently facing the same situation as Greg in that all jobs 
> I send are automatically going to a Cancelled status. These jobs are 
> for 
> product partitions.
>
> A few example job ID's:
>
> 520125237
> 520125243
> 519862123
> 520125246
> 519445444
> 520125249
> 520125240
>
> These are all for account 682-998-6792.
>
> Could this be related to the same cause as Greg's issue?
>
> Kind regards,
> Jordan
>
> On Wednesday, March 1, 2017 at 7:20:33 PM UTC, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hi Greg,
>>
>> One of the engineers on my team found the root cause. We seem to 
>> be having a few difficulties with operations that have product 
>> partitions. 
>> We're currently putting some code in place to 

Re: isExemptable does not become false

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

Thanks for clarifying all of this. That does make sense. I'm not a PHP 
expert, but it does look like the code is only including the first 
exemption request for each ad. I'm getting in touch with our PHP client 
library owner to verify that this is the case. I'll get back to you when I 
get an answer.

Regards,
Nadine, AdWords API Team

On Monday, September 18, 2017 at 8:34:34 PM UTC-4, Hideichi Saito wrote:
>
> thank you for your reply.
>
> Yes. Only one exception request is sent.
>
> As shown in var_dump ($ error);
> PolicyViolationError.isExemptable, is true.
>
> I will attach the contents of $ operations.
>
> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201705/ErrorHandling/HandlePolicyViolationError.php
> line:129. Set up and get var_dump ($operations);
>
> array(1) {
>   [0]=>
>   object(Google\AdsApi\AdWords\v201705\cm\AdGroupAdOperation)#117 (5) {
> ["operand":protected]=>
> object(Google\AdsApi\AdWords\v201705\cm\AdGroupAd)#116 (8) {
>   ["adGroupId":protected]=>
>   string(11) "47899933378"
>   ["ad":protected]=>
>   object(Google\AdsApi\AdWords\v201705\cm\ExpandedTextAd)#113 (18) {
> ["headlinePart1":protected]=>
> string(44) "高力レリーPRバー"
> ["headlinePart2":protected]=>
> string(26) "WEB広も時稿!"
> ["description":protected]=>
> string(104) "無でレリー配＆WEB広出新ースPRバー」をリス
> ["path1":protected]=>
> NULL
> ["path2":protected]=>
> NULL
> ["id":protected]=>
> NULL
> ["url":protected]=>
> NULL
> ["displayUrl":protected]=>
> NULL
> ["finalUrls":protected]=>
> array(1) {
>   [0]=>
>   string(28) "https://pr-bazooka.com/about;
> }
> ["finalMobileUrls":protected]=>
> NULL
> ["finalAppUrls":protected]=>
> NULL
> ["trackingUrlTemplate":protected]=>
> NULL
> ["urlCustomParameters":protected]=>
> NULL
> ["urlData":protected]=>
> NULL
> ["type":protected]=>
> NULL
> ["devicePreference":protected]=>
> NULL
> ["AdType":protected]=>
> NULL
> ["parameterMap":"Google\AdsApi\AdWords\v201705\cm\Ad":private]=>
> array(1) {
>   ["Ad.Type"]=>
>   string(6) "AdType"
> }
>   }
>   ["status":protected]=>
>   NULL
>   ["policySummary":protected]=>
>   NULL
>   ["labels":protected]=>
>   NULL
>   ["baseCampaignId":protected]=>
>   NULL
>   ["baseAdGroupId":protected]=>
>   NULL
>   ["forwardCompatibilityMap":protected]=>
>   NULL
> }
> ["exemptionRequests":protected]=>
> array(1) {
>   [0]=>
>   object(Google\AdsApi\AdWords\v201705\cm\ExemptionRequest)#150 (1) {
> ["key":protected]=>
> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationKey)#142 
> (2) {
>   ["policyName":protected]=>
>   string(7) "weapons"
>   ["violatingText":protected]=>
>   string(7) "bazooka"
> }
>   }
> }
> ["operator":protected]=>
> string(3) "ADD"
> ["OperationType":protected]=>
> NULL
> ["parameterMap":"Google\AdsApi\AdWords\v201705\cm\Operation":private]=>
> array(1) {
>   ["Operation.Type"]=>
>   string(13) "OperationType"
> }
>   }
> }
>
>
>
>
> 2017年9月19日火曜日 7時35分53秒 UTC+9 Nadine Sundquist (AdWords API Team):
>>
>> Hello,
>>
>> I want to make sure I understand your question. I see that you sent me 
>> the response with each error. Each error says that it is exemptable. Are 
>> you saying that the code example is only sending one of the exemptions, and 
>> it is not sending all 3 of them?
>>
>> Regards,
>> Nadine, AdWords API Team
>>
>> On Sunday, September 17, 2017 at 1:22:41 AM UTC-4, Hideichi Saito wrote:
>>>
>>> Many times, thank you for your reply.
>>>
>>> I was misunderstanding.
>>> "!!", I thought that this exemption request can not be made.
>>>
>>> Then, another problem came up.
>>> PolicyViolationError.isExemptable = true
>>> Although it is true, it is not included in ExemptionRequest.
>>>
>>> Actually, there are three errors.
>>>
>>>
>>> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201705/ErrorHandling/HandlePolicyViolationError.php
>>> line:75. Set up and get var_dump ($ error);
>>>
>>> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationError)#141 (12) {
>>>   ["key":protected]=>
>>>   object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationKey)#126 (2) {
>>> ["policyName":protected]=>
>>> string(23) "nonstandard_punctuation"
>>> ["violatingText":protected]=>
>>> string(2) "!!"
>>>   }
>>>   ["externalPolicyName":protected]=>
>>>   string(18) "句点記"
>>>   ["externalPolicyUrl":protected]=>
>>>   string(0) ""
>>>   ["externalPolicyDescription":protected]=>
>>>   string(768) "Google 広で、次よに読や号過に無味）使こは可れせ。
>>> 
>>> 広見し感符使こや1 

Re: UNEXPECTED_INTERNAL_API_ERROR with getCustomers

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Oksana,

Thanks for bumping this thread. We're still looking into this. Have you had 
a chance to try out the solution of putting the client customer ID in the 
header to limit the number of users coming back as explained in this blog 
post 
?
 
I'm hoping that will at least be a workaround while we get to the bottom of 
this.

Thanks,
Nadine, AdWords API Team

On Monday, September 18, 2017 at 6:39:56 AM UTC-4, Oksana Sulyma wrote:
>
> Any news on this? Thanks!
>
> On Wednesday, September 13, 2017 at 3:10:20 PM UTC+3, Oksana Sulyma wrote:
>>
>> Sent details in private message. Thanks!
>>
>> On Tuesday, September 12, 2017 at 8:06:47 PM UTC+3, Shwetha Vastrad 
>> (AdWords API Team) wrote:
>>>
>>> Hi,
>>>
>>> Could you provide the email address which was used to authorize the 
>>> request along with the complete SOAP request and response logs? Please use 
>>> *Reply 
>>> privately to author* when responding. 
>>>
>>> Thanks,
>>> Shwetha, 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+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.
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/9f052817-f69c-4a8f-9ea7-c9fba9b3ab63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: isExemptable does not become false

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I want to make sure I understand your question. I see that you sent me the 
response with each error. Each error says that it is exemptable. Are you 
saying that the code example is only sending one of the exemptions, and it 
is not sending all 3 of them?

Regards,
Nadine, AdWords API Team

On Sunday, September 17, 2017 at 1:22:41 AM UTC-4, Hideichi Saito wrote:
>
> Many times, thank you for your reply.
>
> I was misunderstanding.
> "!!", I thought that this exemption request can not be made.
>
> Then, another problem came up.
> PolicyViolationError.isExemptable = true
> Although it is true, it is not included in ExemptionRequest.
>
> Actually, there are three errors.
>
>
> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201705/ErrorHandling/HandlePolicyViolationError.php
> line:75. Set up and get var_dump ($ error);
>
> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationError)#141 (12) {
>   ["key":protected]=>
>   object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationKey)#126 (2) {
> ["policyName":protected]=>
> string(23) "nonstandard_punctuation"
> ["violatingText":protected]=>
> string(2) "!!"
>   }
>   ["externalPolicyName":protected]=>
>   string(18) "句点記"
>   ["externalPolicyUrl":protected]=>
>   string(0) ""
>   ["externalPolicyDescription":protected]=>
>   string(768) "Google 広で、次よに読や号過に無味）使こは可れせ。
> 
> 広見し感符使こや1 つ広で数感符使こ
> 句点記をりすと「無!!!」な）
> 本とな意合で字使こ（「39セルな）
> 一的使さな記（「~」、「*」な）をうとな、企名含れ場や業の準な用法「5* ホルな）に当る合除）
> 
> https://support.google.com/adwordspolicy/answer/6021546#048; 
> target="_blank">ポシ全をる/a>"
>   ["isExemptable":protected]=>
>   bool(true)
>   ["violatingParts":protected]=>
>   array(1) {
> [0]=>
> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationErrorPart)#125 
> (2) {
>   ["index":protected]=>
>   int(10)
>   ["length":protected]=>
>   int(2)
> }
>   }
>   ["fieldPath":protected]=>
>   string(38) "operations[0].operand.ad.headlinePart2"
>   ["fieldPathElements":protected]=>
>   array(4) {
> [0]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#138 (2) {
>   ["field":protected]=>
>   string(10) "operations"
>   ["index":protected]=>
>   int(0)
> }
> [1]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#137 (2) {
>   ["field":protected]=>
>   string(7) "operand"
>   ["index":protected]=>
>   NULL
> }
> [2]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#136 (2) {
>   ["field":protected]=>
>   string(2) "ad"
>   ["index":protected]=>
>   NULL
> }
> [3]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#135 (2) {
>   ["field":protected]=>
>   string(13) "headlinePart2"
>   ["index":protected]=>
>   NULL
> }
>   }
>   ["trigger":protected]=>
>   string(0) ""
>   ["errorString":protected]=>
>   string(33) "PolicyViolationError.POLICY_ERROR"
>   ["ApiErrorType":protected]=>
>   string(20) "PolicyViolationError"
>   ["parameterMap":"Google\AdsApi\AdWords\v201705\cm\ApiError":private]=>
>   array(1) {
> ["ApiError.Type"]=>
> string(12) "ApiErrorType"
>   }
> }
>
> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationError)#122 (12) {
>   ["key":protected]=>
>   object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationKey)#129 (2) {
> ["policyName":protected]=>
> string(23) "nonstandard_punctuation"
> ["violatingText":protected]=>
> string(26) "WEB広も時稿!"
>   }
>   ["externalPolicyName":protected]=>
>   string(18) "句点記"
>   ["externalPolicyUrl":protected]=>
>   string(0) ""
>   ["externalPolicyDescription":protected]=>
>   string(768) "Google 広で、次よに読や号過に無味）使こは可れせ。
> 
> 広見し感符使こや1 つ広で数感符使こ
> 句点記をりすと「無!!!」な）
> 本とな意合で字使こ（「39セルな）
> 一的使さな記（「~」、「*」な）をうとな、企名含れ場や業の準な用法「5* ホルな）に当る合除）
> 
> https://support.google.com/adwordspolicy/answer/6021546#048; 
> target="_blank">ポシ全をる/a>"
>   ["isExemptable":protected]=>
>   bool(true)
>   ["violatingParts":protected]=>
>   array(1) {
> [0]=>
> object(Google\AdsApi\AdWords\v201705\cm\PolicyViolationErrorPart)#128 
> (2) {
>   ["index":protected]=>
>   int(0)
>   ["length":protected]=>
>   int(12)
> }
>   }
>   ["fieldPath":protected]=>
>   string(38) "operations[0].operand.ad.headlinePart2"
>   ["fieldPathElements":protected]=>
>   array(4) {
> [0]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#123 (2) {
>   ["field":protected]=>
>   string(10) "operations"
>   ["index":protected]=>
>   int(0)
> }
> [1]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#120 (2) {
>   ["field":protected]=>
>   string(7) "operand"
>   ["index":protected]=>
>   NULL
> }
> [2]=>
> object(Google\AdsApi\AdWords\v201705\cm\FieldPathElement)#121 (2) {
>   ["field":protected]=>
>   string(2) "ad"
>   ["index":protected]=>
>   NULL
> }
> [3]=>
> 

Re: Batch jobs stay in state processing for several hours and finally get cancelled

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings Christian!

Here's an update on where we are on this. It turns out that the batch job 
service attempts to send all the requests, but is internally getting back a 
REQUEST_SIZE_LIMIT_EXCEEDED 
 error. 
That happens when there are more than 2000 operations in a normal service. 
What batch job service is doing in the background is that it's breaking up 
the request when that happens and then sends fewer requests. This is 
happening so often that the batch job finally cancels itself. That does 
appear to be an issue on our side because of this. We're exploring 
solutions, but there isn't a solution, yet. I'll update you when we have 
more information. At least we now know the root cause of your issue.

Best,
Nadine, AdWords API Team

On Friday, September 15, 2017 at 6:16:13 PM UTC-4, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Christian,
>
> Thanks for the update. I don't know of any code fixes that went in within 
> the last day.
>
> Batch job service can theoretically handle quite a few operations, but 
> even 1 000 000 is a lot when you think of all the updates that have to 
> happen on the back end. Some changes are more expensive than others and 
> take a bit longer because even though it looks like you're updating maybe 
> one field, there is logic that needs to check on things like if something 
> can be overridden at specific levels or if other objects in the account 
> will be affected by the change. That's why some things do take a bit longer.
>
> Regards,
> Nadine, AdWords API Team 
>
> On Friday, September 15, 2017 at 2:38:51 PM UTC-4, Christian wrote:
>>
>> Hi Nadine,
>>
>> thanks for looking into that.
>>
>> Today we reduced the total number of set-max-cpc operations to be below 
>> 100 000 and all 4 jobs (each at most 25 000 operations) completed 
>> successfully within a few minutes. Is there already a fix live? Let me know 
>> if we should have a try again with a larger number of operations.
>>
>> In case it is helpful for debugging, here are the IDs of the jobs 
>> successfully completed today: 565656811, 565639265, 565650926, 565663576.
>>
>> By the way: we also submit more than 1 000 000 bid modifier operations 
>> each day. The corresponding jobs do not get cancelled but still require 
>> several hours to complete. Do we have to limit our daily number of 
>> operations here or is that something the batch job service should be able 
>> to handle faster in theory? An example job ID would be 565684901.
>>
>> Best regards,
>> Christian
>>
>> On Friday, September 15, 2017 at 3:48:31 PM UTC+2, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hello Christian,
>>>
>>> I've taken a look into what's happening, and initially I don't see a 
>>> root cause. My team will dig further into it, and I'll get back to you when 
>>> I have the reason as to why these jobs are not successful.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, September 14, 2017 at 4:31:01 PM UTC-4, Christian wrote:

 Hi Shwetha,

 > If the submitted operations encounter an error during execution, the 
 results in the downloadUrl 
 
  should 
 contain the list of processingErrors 
 
  on 
 the batch job

 The problem here is that most of the cancelled jobs have no error 
 information -- neither in the job status we get when polling the jobs nor 
 in the result file pointed to by the download URL. If some of the 
 operations executed, we see them in the result file but not executed 
 operations are simply not referenced in the result file.

 > Could you retry the BatchJob request with fewer number of 
 operations? 

 For now we tried to reduce the total number of operations. I'll check 
 if this improves the situation. After that we will have a try with smaller 
 batch jobs.

 Best,
 Christian

 On Thursday, September 14, 2017 at 5:19:37 PM UTC+2, Shwetha Vastrad 
 (AdWords API Team) wrote:
>
> Hi Christian, 
>
> BatchJobService automatically retries operations that fail due to 
> transient errors such as RateExceededError 
> .
>  
> If the submitted operations encounter an error during execution, the 
> results in the downloadUrl 
> 
>  should 
> contain the list of processingErrors 
> 
>  on 
> the batch job. I'll get in touch with the 

Re: Batch jobs stay in state processing for several hours and finally get cancelled

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Christian,

Thanks for the update. I don't know of any code fixes that went in within 
the last day.

Batch job service can theoretically handle quite a few operations, but even 
1 000 000 is a lot when you think of all the updates that have to happen on 
the back end. Some changes are more expensive than others and take a bit 
longer because even though it looks like you're updating maybe one field, 
there is logic that needs to check on things like if something can be 
overridden at specific levels or if other objects in the account will be 
affected by the change. That's why some things do take a bit longer.

Regards,
Nadine, AdWords API Team 

On Friday, September 15, 2017 at 2:38:51 PM UTC-4, Christian wrote:
>
> Hi Nadine,
>
> thanks for looking into that.
>
> Today we reduced the total number of set-max-cpc operations to be below 
> 100 000 and all 4 jobs (each at most 25 000 operations) completed 
> successfully within a few minutes. Is there already a fix live? Let me know 
> if we should have a try again with a larger number of operations.
>
> In case it is helpful for debugging, here are the IDs of the jobs 
> successfully completed today: 565656811, 565639265, 565650926, 565663576.
>
> By the way: we also submit more than 1 000 000 bid modifier operations 
> each day. The corresponding jobs do not get cancelled but still require 
> several hours to complete. Do we have to limit our daily number of 
> operations here or is that something the batch job service should be able 
> to handle faster in theory? An example job ID would be 565684901.
>
> Best regards,
> Christian
>
> On Friday, September 15, 2017 at 3:48:31 PM UTC+2, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Christian,
>>
>> I've taken a look into what's happening, and initially I don't see a root 
>> cause. My team will dig further into it, and I'll get back to you when I 
>> have the reason as to why these jobs are not successful.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, September 14, 2017 at 4:31:01 PM UTC-4, Christian wrote:
>>>
>>> Hi Shwetha,
>>>
>>> > If the submitted operations encounter an error during execution, the 
>>> results in the downloadUrl 
>>> 
>>>  should 
>>> contain the list of processingErrors 
>>> 
>>>  on 
>>> the batch job
>>>
>>> The problem here is that most of the cancelled jobs have no error 
>>> information -- neither in the job status we get when polling the jobs nor 
>>> in the result file pointed to by the download URL. If some of the 
>>> operations executed, we see them in the result file but not executed 
>>> operations are simply not referenced in the result file.
>>>
>>> > Could you retry the BatchJob request with fewer number of operations? 
>>>
>>> For now we tried to reduce the total number of operations. I'll check if 
>>> this improves the situation. After that we will have a try with smaller 
>>> batch jobs.
>>>
>>> Best,
>>> Christian
>>>
>>> On Thursday, September 14, 2017 at 5:19:37 PM UTC+2, Shwetha Vastrad 
>>> (AdWords API Team) wrote:

 Hi Christian, 

 BatchJobService automatically retries operations that fail due to 
 transient errors such as RateExceededError 
 .
  
 If the submitted operations encounter an error during execution, the 
 results in the downloadUrl 
 
  should 
 contain the list of processingErrors 
 
  on 
 the batch job. I'll get in touch with the team to check why the BatchJobs 
 are getting cancelled. Could you retry the BatchJob request with fewer 
 number of operations? 

 Thanks,
 Shwetha, 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+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.
Visit this group at 

Re: isExemptable does not become false

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I noticed when you send the exemption request, you only send 1 exemption 
request for bazooka. When you sent the second mutate, you should have sent 
two exemption requests at the same time. One exemption request should have 
been for bazooka and the other should have been for !!. Could you please 
try sending two exemption requests for that one ad at the same time? If you 
still have issues after doing that, please get back to me.

Thanks,
Nadine, AdWords API Team

On Thursday, September 14, 2017 at 8:37:37 PM UTC-4, Hideichi Saito wrote:
>
> Thank you for your reply.
>
> I am sorry that the explanation is insufficient.
> Yes, I understand that there are two policy violations.
>
> One policy violation is for the word bazooka.
> PolicyViolationError.isExemptable = true, this is as expected.
>
> One policy violation is for the !!.
> PolicyViolationError.isExemptable = true, this is disappointing.
> I think that it can not be exempted from application, so I want you to 
> return false.
>
> As a result, I understand that it is an error in the second mutate.
>
>
> 2017年9月15日金曜日 0時38分21秒 UTC+9 Nadine Sundquist (AdWords API Team):
>>
>> Greetings!
>>
>> I think I may have found why this isn't working as expected. In the 
>> error, it is saying that the violation is the *!!* in the ad text. When 
>> the exemption request is sent, it does not mention the '!!'. It mentions 
>> the word *bazooka, *but there is no exemption being passed in for the 
>> *!!*. Can you please make sure that you have 1 exemption request for 
>> each policy violation. You have 2 policy violations here that can be 
>> exempted.
>>
>>- One policy violation is for the word *bazooka*.
>>- One policy violation is for the *!!*.
>>
>> ADD<
>> ns1:operand>000> xsi:type="ns1:ExpandedTextAd">https://exsample.com/about 
>> 
>> 高火力プレスリリースPRバズーカ> headlinePart1>WEB広告も同時出稿!!> description>無料でプレスリリース配信＆WEB広告出稿新サービス「PRバズーカ」をリリース> ns1:description><
>> ns1:policyName>weapons
>> bazooka> operations>
>>
>>
>> Please try adding an exemption request for all the policy violations. If 
>> you still experience issues, please get back to me.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, September 14, 2017 at 4:35:56 AM UTC-4, Hideichi Saito wrote:
>>>
>>> Thank you for your reply.
>>>
>>>
>>> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201705/ErrorHandling/HandlePolicyViolationError.php
>>> This sample is the first mutate, and if 
>>> PolicyViolationError.isExemptable = true, ExemptionRequest is possible.
>>> Although I understand that it is a sample called 
>>> PolicyViolationError.isExemptable = true, an error occurs with the second 
>>> mutate.
>>>
>>> Because it is google translation, please forgive me that it is difficult 
>>> to understand sentences.
>>> It is briefly described as follows.
>>>
>>> this sample code is,
>>> if PolicyViolationError.isExemptable = true then ExemptionRequest 
>>> executable.
>>> but error. 
>>>
>>>
>>> 2017年9月14日木曜日 16時42分17秒 UTC+9 Peter Oliquino:

 Hi Hideichi,

 Please correct my understanding if I am wrong. Could you confirm if my 
 understanding is correct that you initially sent a request to create ads 
 that you expect to be *isExemptable = false* but got an *isExemptable 
 = true* response instead? If my understanding is indeed correct, then 
 I'm afraid that identifying which values would pass or not pass the 
 policies of AdWords is already out of scope for our team.

 I would recommend that you consult with the product experts at the AdWords 
 Community Forum 
 
  in 
 order to identify which values would trigger an *isExemptable = false* as 
 response. However, if I misunderstood it correctly, please let me know so 
 I 
 can provide a better and more correct response.

 Best regards,
 Peter
 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+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.
Visit this group at https://groups.google.com/group/adwords-api.
To view 

Re: Batch jobs stay in state processing for several hours and finally get cancelled

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Christian,

I've taken a look into what's happening, and initially I don't see a root 
cause. My team will dig further into it, and I'll get back to you when I 
have the reason as to why these jobs are not successful.

Best,
Nadine, AdWords API Team

On Thursday, September 14, 2017 at 4:31:01 PM UTC-4, Christian wrote:
>
> Hi Shwetha,
>
> > If the submitted operations encounter an error during execution, the 
> results in the downloadUrl 
> 
>  should 
> contain the list of processingErrors 
> 
>  on 
> the batch job
>
> The problem here is that most of the cancelled jobs have no error 
> information -- neither in the job status we get when polling the jobs nor 
> in the result file pointed to by the download URL. If some of the 
> operations executed, we see them in the result file but not executed 
> operations are simply not referenced in the result file.
>
> > Could you retry the BatchJob request with fewer number of operations? 
>
> For now we tried to reduce the total number of operations. I'll check if 
> this improves the situation. After that we will have a try with smaller 
> batch jobs.
>
> Best,
> Christian
>
> On Thursday, September 14, 2017 at 5:19:37 PM UTC+2, Shwetha Vastrad 
> (AdWords API Team) wrote:
>>
>> Hi Christian, 
>>
>> BatchJobService automatically retries operations that fail due to 
>> transient errors such as RateExceededError 
>> .
>>  
>> If the submitted operations encounter an error during execution, the 
>> results in the downloadUrl 
>> 
>>  should 
>> contain the list of processingErrors 
>> 
>>  on 
>> the batch job. I'll get in touch with the team to check why the BatchJobs 
>> are getting cancelled. Could you retry the BatchJob request with fewer 
>> number of operations? 
>>
>> Thanks,
>> Shwetha, 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+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.
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/b4e322d0-8294-4170-ba13-15183d306f71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: isExemptable does not become false

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

I think I may have found why this isn't working as expected. In the error, 
it is saying that the violation is the *!!* in the ad text. When the 
exemption request is sent, it does not mention the '!!'. It mentions the 
word *bazooka, *but there is no exemption being passed in for the *!!*. Can 
you please make sure that you have 1 exemption request for each policy 
violation. You have 2 policy violations here that can be exempted.

   - One policy violation is for the word *bazooka*.
   - One policy violation is for the *!!*.

ADD<
ns1:operand>000https://exsample.com/about 

高火力プレスリリースPRバズーカWEB広告も同時出稿!!無料でプレスリリース配信＆
WEB広告出稿新サービス「PRバズーカ」をリリースweaponsbazooka


Please try adding an exemption request for all the policy violations. If 
you still experience issues, please get back to me.

Best,
Nadine, AdWords API Team

On Thursday, September 14, 2017 at 4:35:56 AM UTC-4, Hideichi Saito wrote:
>
> Thank you for your reply.
>
>
> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201705/ErrorHandling/HandlePolicyViolationError.php
> This sample is the first mutate, and if PolicyViolationError.isExemptable 
> = true, ExemptionRequest is possible.
> Although I understand that it is a sample called 
> PolicyViolationError.isExemptable = true, an error occurs with the second 
> mutate.
>
> Because it is google translation, please forgive me that it is difficult 
> to understand sentences.
> It is briefly described as follows.
>
> this sample code is,
> if PolicyViolationError.isExemptable = true then ExemptionRequest 
> executable.
> but error. 
>
>
> 2017年9月14日木曜日 16時42分17秒 UTC+9 Peter Oliquino:
>>
>> Hi Hideichi,
>>
>> Please correct my understanding if I am wrong. Could you confirm if my 
>> understanding is correct that you initially sent a request to create ads 
>> that you expect to be *isExemptable = false* but got an *isExemptable = 
>> true* response instead? If my understanding is indeed correct, then I'm 
>> afraid that identifying which values would pass or not pass the policies of 
>> AdWords is already out of scope for our team.
>>
>> I would recommend that you consult with the product experts at the AdWords 
>> Community Forum 
>> 
>>  in 
>> order to identify which values would trigger an *isExemptable = false* as 
>> response. However, if I misunderstood it correctly, please let me know so I 
>> can provide a better and more correct response.
>>
>> Best regards,
>> Peter
>> 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+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.
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/1bd70cef-a85d-4502-9684-d04ea5a8caf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch Job - Customizer Feed Item - NullError.NULL_CONTENT

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings Calin,

I got in touch with the owner of the PHP library on my team. He's working 
on figuring out a solution. Please keep an eye on GitHub repo 
 for a fix. I don't have an 
exact time as to when that will happen, but I'll keep an eye on it to try 
to inform you when ti is available.

Take care,
Nadine, AdWords API Team

On Wednesday, August 30, 2017 at 3:53:54 AM UTC-4, Calin Ignat wrote:
>
> Hello,
>
> Good news! I'm guessing the issues is here 
> 
>  and 
> will be easy to fix in future versions. Until then I will continue to use 
> mutate service to build feed items.
> Thank you very much for your assistance.
>
> Good day.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/36a034ed-c047-4e18-bf6c-bcc744ff074b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch Job - Customizer Feed Item - NullError.NULL_CONTENT

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Calin,

Thanks for giving that a try. That helps me narrow it down a bit as to 
where in the code something could be going wrong. If I need anything 
further, I'll reach out. 

Regards,
Nadine, AdWords API Team

On Tuesday, August 22, 2017 at 5:20:48 PM UTC+10, Calin Ignat wrote:
>
> Running now on v201708 
> 
>  of Release 28.1.0. 
> 
>  There 
> is no change, I get the same errors when trying to add feed items trough 
> the batch job. 
>
> On Tuesday, August 22, 2017 at 9:10:49 AM UTC+3, Calin Ignat wrote:
>>
>> Hello Nadine,
>>
>> Yes, for now thats how i'm making campaigns, using the mutate service for 
>> the feed items. That works *fine*, but i'm not sure how it will work for 
>> large amounts of operations in big campaigns. Also it takes a bit more time 
>> as first i need to make the campaign with the batch job, then get all the 
>> adGroups created and match them with the feed items info, then create the 
>> feed items trough mutate job using the id of the adGroup. But yes, that 
>> gets the job done...
>> Today I will update the client library, I will let you know if anything 
>> changes.
>>
>> Thank you,
>> Have a good day.
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/493e2bde-2bdf-4a7d-8671-9b4d1d2730c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch Job - Customizer Feed Item - NullError.NULL_CONTENT

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Calin,

Thanks for responding so quickly! If you're creating the same operations 
and passing them into the mutate service rather than the batch job service, 
is that still working for you for v201705? I'm just trying to pinpoint if 
this is a batch job service only issue.

Thanks,
Nadine, AdWords API Team

On Monday, August 21, 2017 at 5:41:20 PM UTC+10, Calin Ignat wrote:
>
> Hello Nadine,
>
> Yes, when i was talking about the old library I was referring at the old 
> now depreciated client libraries.
> My only point was that i was using that successfully adding feed items to 
> a feed using batch job.
>  
> We've recently updated to v201705 and I had rewritten all the code from 
> scratch for the tool that creates these campaigns.
> The actual code to add feed items its not very different from the example 
> here 
> .
>  
> The only difference is that instead of using mutate service i'm using the 
> operation for the batch job. All the other elements from the campaign are 
> working fine this way...
>
> Thank you,
> Good day.
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/aa159d75-0a0e-4b11-af98-98f953ada8f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch Job - Customizer Feed Item - NullError.NULL_CONTENT

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Calin,

When you say that you're using an old library versus a new one, are you 
talking about the client libraries 
 that we 
release? I just want to make sure we're working from the same baseline. 

Thanks,
Nadine, AdWords API Team

On Monday, August 21, 2017 at 4:21:10 PM UTC+10, Calin Ignat wrote:
>
> Good day,
>
> Any update on this?
> I still haven't figure it out.
>
> Thank you.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/db67c7b4-ffc2-49bb-939c-9def57e2880c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Abnormally high number of cancelled/failed batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings All,

I've filed an issue on this so we can dive deeper into why this is 
happening. I'll get back to you when we've made more progress on why this 
is happening again.

Best,
Nadine, AdWords API Team

On Wednesday, August 16, 2017 at 12:15:08 AM UTC+8, GregT wrote:
>
> We also are. Here are a few sample job ids from us, in case it helps:
>
> 546629438
> 546628553
> 546690922
> 546964719
> 546610328
> 546608684
> 546962208
> 546611558
> 546606977
> 546961335
> 546605693
> 546959982
> 546959979
> 546958008
> 546956727
> 546676590
> 546676494
> 546676485
> 546676170
> 546354463
> 546353035
> 546338374
> 546338884
> 546338836
>
> Thanks,
> Greg
>
> On Tuesday, August 15, 2017 at 3:57:05 AM UTC-5, jor...@jcrocker.uk wrote:
>>
>> Hello Nadine,
>>
>> We are experiencing this problem again, with the following sample jobs 
>> IDs:
>>
>> 546679208
>> 546680861
>> 546680843
>> 546739639
>> 546680837
>> 546740809
>> 546740803
>> 546738088
>> 546740836
>> 546679832
>> 546680852
>> 546739642
>> 546738997
>> 547027008
>> 546680846
>> 546680882
>> 546738103
>> 546740464
>> 546740800
>> 546679220
>> 546740467
>> 546740839
>> 547027005
>> 546679214
>> 546740797
>> 546740812
>> 546680849
>> 546679205
>> 546679217
>> 546679835
>>
>>
>> Thanks for your help.
>>
>> Kind regards,
>> Jordan
>>
>> On Thursday, July 6, 2017 at 2:45:53 PM UTC+1, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hello Simon,
>>>
>>> The fix is now on our production servers. Please give it another try. If 
>>> you're still experiencing issues, please get back to me.
>>>
>>> Thanks,
>>> Nadine, AdWords API Team
>>>
>>> On Wednesday, July 5, 2017 at 8:23:27 AM UTC-4, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hello Simon,

 It looks like we have found the root cause. Now that the holidays are 
 winding down here in the US, we can look at trying to find a solution. 
 I'll 
 keep you in the loop.

 Best,
 Nadine, AdWords API Team

 On Wednesday, July 5, 2017 at 5:32:44 AM UTC-4, si...@hotsnapper.com 
 wrote:
>
> Hello Nadine, 
>
> I am working alongside Jordan do we have an update?
>
> Regards
>
> Simon
>
>
>
> On Tuesday, June 27, 2017 at 10:18:31 PM UTC+1, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Jordan,
>>
>> I took a look on our servers, and at first glance it does look like 
>> it could be the same issue. I've sent on the job IDs to my teammate 
>> who's 
>> assigned to this. I'll get back to you when I hear back. This looks like 
>> a 
>> tough one. Thank you for providing these job IDs.
>>
>> Take care,
>> Nadine, AdWords API Team
>>
>> On Tuesday, June 27, 2017 at 5:25:31 AM UTC-4, jor...@jcrocker.uk 
>> wrote:
>>>
>>> Hi Nadine,
>>>
>>> I am currently facing the same situation as Greg in that all jobs I 
>>> send are automatically going to a Cancelled status. These jobs are for 
>>> product partitions.
>>>
>>> A few example job ID's:
>>>
>>> 520125237
>>> 520125243
>>> 519862123
>>> 520125246
>>> 519445444
>>> 520125249
>>> 520125240
>>>
>>> These are all for account 682-998-6792.
>>>
>>> Could this be related to the same cause as Greg's issue?
>>>
>>> Kind regards,
>>> Jordan
>>>
>>> On Wednesday, March 1, 2017 at 7:20:33 PM UTC, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hi Greg,

 One of the engineers on my team found the root cause. We seem to be 
 having a few difficulties with operations that have product 
 partitions. 
 We're currently putting some code in place to retry when those 
 particular 
 operations have issues.

 Cheers,
 Nadine, AdWords API Team

 On Wednesday, March 1, 2017 at 10:44:39 AM UTC-5, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hi Greg,
>
> Thanks for all the helpful details! I started investigating on our 
> servers to track down why this is happening. On my initial pass of 
> our 
> logs, I don't see a reason for the cancel happening when it appears 
> that 
> the job is finishing (whether it has errors or not). I'm pulling in a 
> few 
> more people here to take a look to help me solve this mystery. I'll 
> get 
> back to you when we've made a bit more progress on this.
>
> Best,
> Nadine, AdWords API Team
>
> On Tuesday, February 28, 2017 at 11:00:44 AM UTC-5, GregT wrote:
>>
>> Hi, Peter.
>>
>> We don't actually log the SOAP for these because the SOAP calls 
>> themselves aren't failing -- it's just that the status of the jobs 
>> are 
>> eventually getting returned as cancelled. As 

Re: Batch Job - Customizer Feed Item - NullError.NULL_CONTENT

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Calin,

Thanks for providing all those logs. I've filed an issue so we can take a 
look into this. At this point, I'm not sure what's happening. I'll get back 
to you when we've made more progress in figuring this out.

Best,
Nadine, AdWords API Team

On Friday, August 11, 2017 at 3:21:45 PM UTC+8, Calin Ignat wrote:
>
> As a quick follow up,
>
> I've made 2 more test campaigns and I will not delete them, I've attached 
> the soap, batch logs and xml results from the batch jobs for both of them.
> case1 - campaign all made in one batch job, feed items use temporary 
> adGroup id
> case2 - separated batch jobs, for the whole campaign and then another one 
> for the feed items associated to the real adGroups ID.
>
> Good day.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/cdc45842-82b3-4cd0-b6ec-26ffe959689f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch Job - Customizer Feed Item - NullError.NULL_CONTENT

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Calin,

I think I've solved the mystery here. I took a look at your account, and 
your ad group ID that you're specifying is in a campaign that was removed. 
That means that the ad group is no longer viable because the campaign is in 
the removed state. At least that's the case for the second message that you 
sent. As for the first case, please make sure that the new ad group you're 
creating is in an enabled or paused campaign rather than a removed one. 
That could possibly be causing the issue since that appeared to be the 
problem in the second case.

Best,
Nadine, AdWords API Team

On Thursday, August 10, 2017 at 6:28:22 PM UTC+8, Calin Ignat wrote:
>
> Good day.
>
> As an update, i've tried making another batch job for the feed items after 
> everything is done, i've used the real id of the adGroup but i am getting 
> the same error.
> I still haven't figured out what's wrong.
>
> Thank you, 
> Good day.
>
> *array* *(size=1)*
>   0 => 
> *object*(*Google\AdsApi\AdWords\v201705\cm\FeedItemOperation*)[*796*]
>   *protected* 'operand' => 
> *object*(*Google\AdsApi\AdWords\v201705\cm\FeedItem*)[*746*]
>   *protected* 'feedId' => int 57843974
>   *protected* 'feedItemId' => null
>   *protected* 'status' => null
>   *protected* 'startTime' => null
>   *protected* 'endTime' => null
>   *protected* 'attributeValues' => 
> *array* *(size=3)*
>   0 => 
> 
> *object*(*Google\AdsApi\AdWords\v201705\cm\FeedItemAttributeValue*)[*784*]
>   *protected* 'feedAttributeId' => int 1
>   *protected* 'integerValue' => null
>   *protected* 'doubleValue' => null
>   *protected* 'booleanValue' => null
>   *protected* 'stringValue' => string 
> 'US_NYC_NY_US_to_ROM_Italy' *(length=25)*
>   *protected* 'integerValues' => null
>   *protected* 'doubleValues' => null
>   *protected* 'booleanValues' => null
>   *protected* 'stringValues' => null
>   *protected* 'moneyWithCurrencyValue' => null
>   1 => 
> 
> *object*(*Google\AdsApi\AdWords\v201705\cm\FeedItemAttributeValue*)[*803*]
>   *protected* 'feedAttributeId' => int 2
>   *protected* 'integerValue' => null
>   *protected* 'doubleValue' => null
>   *protected* 'booleanValue' => null
>   *protected* 'stringValue' => int 1
>   *protected* 'integerValues' => null
>   *protected* 'doubleValues' => null
>   *protected* 'booleanValues' => null
>   *protected* 'stringValues' => null
>   *protected* 'moneyWithCurrencyValue' => null
>   2 => 
> 
> *object*(*Google\AdsApi\AdWords\v201705\cm\FeedItemAttributeValue*)[*800*]
>   *protected* 'feedAttributeId' => int 3
>   *protected* 'integerValue' => null
>   *protected* 'doubleValue' => null
>   *protected* 'booleanValue' => null
>   *protected* 'stringValue' => string '08-10-2017' 
> *(length=10)*
>   *protected* 'integerValues' => null
>   *protected* 'doubleValues' => null
>   *protected* 'booleanValues' => null
>   *protected* 'stringValues' => null
>   *protected* 'moneyWithCurrencyValue' => null
>   *protected* 'policyData' => null
>   *protected* 'devicePreference' => null
>   *protected* 'scheduling' => null
>   *protected* 'campaignTargeting' => null
>   *protected* 'adGroupTargeting' => 
> 
> *object*(*Google\AdsApi\AdWords\v201705\cm\FeedItemAdGroupTargeting*)[*807*]
>   *protected* 'TargetingAdGroupId' => int 44656141185
>   *protected* 'keywordTargeting' => null
>   *protected* 'geoTargeting' => null
>   *protected* 'geoTargetingRestriction' => null
>   *protected* 'urlCustomParameters' => null
>   *protected* 'operator' => string 'ADD' *(length=3)*
>   *protected* 'OperationType' => null
>   *private* 'parameterMap' (Google\AdsApi\AdWords\v201705\cm\Operation) 
> => 
> *array* *(size=1)*
>   'Operation.Type' => string 'OperationType' *(length=13)*
>
>
>
> 
> https://adwords.google.com/api/adwords/cm/v201705;>
>
>   
>  http://www.w3.org/2001/XMLSchema-instance; 
> xsi:type="NullError">
> operations[0].operand.adGroupTargeting.adGroupId fieldPath>
> 
>operations
>0
> 
> 
>operand
> 
> 
>adGroupTargeting
> 
> 
>adGroupId
> 
> 
> 

Re: Set up billing for every customer or Consolidated Billing?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Guadalupe,

Wow! You're really efficient in your questions. Let's see if I can get all 
of them answered.

   - For account creation and linking, you can check out our Managing 
   Accounts guide 
   
   .
   - Setting up billing information does need to be done outside of the API 
   (in the UI). However, as you noticed budget orders can be managed through 
   the BudgetOrderService, but it does require consolidated billing. I'm sure 
   you've already gone through our Budget Order Service guide 
   .
   - As for reports there are quite a few options 
   .

So, for your next steps:

   - Make sure that consolidated billing is set up for your account.
   - Then, on the forum choose *Reply privately to author* in the drop-down 
   and send me the account information where the consolidated billing is set 
   up. I can try to work with you to get this whitelisted.

Best,
Nadine, AdWords API Team

On Tuesday, July 18, 2017 at 12:54:41 AM UTC-4, Guadalupe Estrada wrote:
>
> Hello,
>
> We have a MCC account (agency) and an approved developer token, we've 
> already tested basic capabilities of the API. 
> The goal we have in mind is to create a solution integrated into our own 
> website to be able to manage their campaigns, where our clients will 
> perform several actions (via API):
>
>- Account creation/linking into our MCC account
>- Set up their own account billing information
>- View reports, etc.
>
> Now, I've read several posts that mention the API does not support 
> entering billing information for an account and can only be done via UI. 
> Is that the way it currently works?
> I've also read that being whitelisted for the BudgetOrderService would 
> allow us to create a BudgetOrder using our own billing account,
> Do we need to set up Consolidated Billing to apply to this process?
>
> We don't have a Google Representative/Account Manager. I need someone who 
> can help us with this.
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/be76d0a8-eb5f-41bd-a747-0236bdf5e13e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Abnormally high number of cancelled/failed batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Simon,

The fix is now on our production servers. Please give it another try. If 
you're still experiencing issues, please get back to me.

Thanks,
Nadine, AdWords API Team

On Wednesday, July 5, 2017 at 8:23:27 AM UTC-4, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hello Simon,
>
> It looks like we have found the root cause. Now that the holidays are 
> winding down here in the US, we can look at trying to find a solution. I'll 
> keep you in the loop.
>
> Best,
> Nadine, AdWords API Team
>
> On Wednesday, July 5, 2017 at 5:32:44 AM UTC-4, si...@hotsnapper.com 
> wrote:
>>
>> Hello Nadine, 
>>
>> I am working alongside Jordan do we have an update?
>>
>> Regards
>>
>> Simon
>>
>>
>>
>> On Tuesday, June 27, 2017 at 10:18:31 PM UTC+1, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hello Jordan,
>>>
>>> I took a look on our servers, and at first glance it does look like it 
>>> could be the same issue. I've sent on the job IDs to my teammate who's 
>>> assigned to this. I'll get back to you when I hear back. This looks like a 
>>> tough one. Thank you for providing these job IDs.
>>>
>>> Take care,
>>> Nadine, AdWords API Team
>>>
>>> On Tuesday, June 27, 2017 at 5:25:31 AM UTC-4, jor...@jcrocker.uk wrote:

 Hi Nadine,

 I am currently facing the same situation as Greg in that all jobs I 
 send are automatically going to a Cancelled status. These jobs are for 
 product partitions.

 A few example job ID's:

 520125237
 520125243
 519862123
 520125246
 519445444
 520125249
 520125240

 These are all for account 682-998-6792.

 Could this be related to the same cause as Greg's issue?

 Kind regards,
 Jordan

 On Wednesday, March 1, 2017 at 7:20:33 PM UTC, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hi Greg,
>
> One of the engineers on my team found the root cause. We seem to be 
> having a few difficulties with operations that have product partitions. 
> We're currently putting some code in place to retry when those particular 
> operations have issues.
>
> Cheers,
> Nadine, AdWords API Team
>
> On Wednesday, March 1, 2017 at 10:44:39 AM UTC-5, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hi Greg,
>>
>> Thanks for all the helpful details! I started investigating on our 
>> servers to track down why this is happening. On my initial pass of our 
>> logs, I don't see a reason for the cancel happening when it appears that 
>> the job is finishing (whether it has errors or not). I'm pulling in a 
>> few 
>> more people here to take a look to help me solve this mystery. I'll get 
>> back to you when we've made a bit more progress on this.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Tuesday, February 28, 2017 at 11:00:44 AM UTC-5, GregT wrote:
>>>
>>> Hi, Peter.
>>>
>>> We don't actually log the SOAP for these because the SOAP calls 
>>> themselves aren't failing -- it's just that the status of the jobs are 
>>> eventually getting returned as cancelled. As mentioned in the original 
>>> post, some have no processing or other errors at all - just the status 
>>> cancelled. Others have that status and have a single processing error: 
>>> BatchJobService.INTERNAL_ERROR, with no other information in the 
>>> processing 
>>> errors. An example of the printout of all the fields we get for that 
>>> error 
>>> is:
>>>
>>> errorType:BatchJobProcessingError, trigger:, 
>>> errorString:BatchJobProcessingError.INTERNAL_ERROR, fieldPath:, 
>>> reason:INTERNAL_ERROR
>>>
>>> A couple example jobs from yesterday that return the error (along 
>>> with being cancelled):
>>> 450605098
>>> 450816012
>>>
>>> A couple that have no error, but are just cancelled:
>>> 450865617
>>> 451028751
>>>
>>> All the ones listed in the original post fall into one of these two 
>>> categories, I believe.
>>>
>>> Thanks,
>>> Greg
>>>
>>> On Monday, February 27, 2017 at 10:07:26 PM UTC-6, Peter Oliquino 
>>> wrote:

 Hello Greg,

 To help us investigate further, could you please provide us the 
 SOAP logs for both request and response of one of your failed 
 BatchJobService if you were able to capture them. Please reply using 
 *Reply 
 privately to author *when sending the requested information. 
 Additionally, you may also inspect the downloadUrl and the list of 
 processingErrors in the BatchJob to get possible reasons for the 
 failure.

 Best regards,
 Peter
 AdWords API Team

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/

Re: Abnormally high number of cancelled/failed batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Simon,

It looks like we have found the root cause. Now that the holidays are 
winding down here in the US, we can look at trying to find a solution. I'll 
keep you in the loop.

Best,
Nadine, AdWords API Team

On Wednesday, July 5, 2017 at 5:32:44 AM UTC-4, si...@hotsnapper.com wrote:
>
> Hello Nadine, 
>
> I am working alongside Jordan do we have an update?
>
> Regards
>
> Simon
>
>
>
> On Tuesday, June 27, 2017 at 10:18:31 PM UTC+1, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello Jordan,
>>
>> I took a look on our servers, and at first glance it does look like it 
>> could be the same issue. I've sent on the job IDs to my teammate who's 
>> assigned to this. I'll get back to you when I hear back. This looks like a 
>> tough one. Thank you for providing these job IDs.
>>
>> Take care,
>> Nadine, AdWords API Team
>>
>> On Tuesday, June 27, 2017 at 5:25:31 AM UTC-4, jor...@jcrocker.uk wrote:
>>>
>>> Hi Nadine,
>>>
>>> I am currently facing the same situation as Greg in that all jobs I send 
>>> are automatically going to a Cancelled status. These jobs are for product 
>>> partitions.
>>>
>>> A few example job ID's:
>>>
>>> 520125237
>>> 520125243
>>> 519862123
>>> 520125246
>>> 519445444
>>> 520125249
>>> 520125240
>>>
>>> These are all for account 682-998-6792.
>>>
>>> Could this be related to the same cause as Greg's issue?
>>>
>>> Kind regards,
>>> Jordan
>>>
>>> On Wednesday, March 1, 2017 at 7:20:33 PM UTC, Nadine Sundquist (AdWords 
>>> API Team) wrote:

 Hi Greg,

 One of the engineers on my team found the root cause. We seem to be 
 having a few difficulties with operations that have product partitions. 
 We're currently putting some code in place to retry when those particular 
 operations have issues.

 Cheers,
 Nadine, AdWords API Team

 On Wednesday, March 1, 2017 at 10:44:39 AM UTC-5, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> Hi Greg,
>
> Thanks for all the helpful details! I started investigating on our 
> servers to track down why this is happening. On my initial pass of our 
> logs, I don't see a reason for the cancel happening when it appears that 
> the job is finishing (whether it has errors or not). I'm pulling in a few 
> more people here to take a look to help me solve this mystery. I'll get 
> back to you when we've made a bit more progress on this.
>
> Best,
> Nadine, AdWords API Team
>
> On Tuesday, February 28, 2017 at 11:00:44 AM UTC-5, GregT wrote:
>>
>> Hi, Peter.
>>
>> We don't actually log the SOAP for these because the SOAP calls 
>> themselves aren't failing -- it's just that the status of the jobs are 
>> eventually getting returned as cancelled. As mentioned in the original 
>> post, some have no processing or other errors at all - just the status 
>> cancelled. Others have that status and have a single processing error: 
>> BatchJobService.INTERNAL_ERROR, with no other information in the 
>> processing 
>> errors. An example of the printout of all the fields we get for that 
>> error 
>> is:
>>
>> errorType:BatchJobProcessingError, trigger:, 
>> errorString:BatchJobProcessingError.INTERNAL_ERROR, fieldPath:, 
>> reason:INTERNAL_ERROR
>>
>> A couple example jobs from yesterday that return the error (along 
>> with being cancelled):
>> 450605098
>> 450816012
>>
>> A couple that have no error, but are just cancelled:
>> 450865617
>> 451028751
>>
>> All the ones listed in the original post fall into one of these two 
>> categories, I believe.
>>
>> Thanks,
>> Greg
>>
>> On Monday, February 27, 2017 at 10:07:26 PM UTC-6, Peter Oliquino 
>> wrote:
>>>
>>> Hello Greg,
>>>
>>> To help us investigate further, could you please provide us the SOAP 
>>> logs for both request and response of one of your failed 
>>> BatchJobService if 
>>> you were able to capture them. Please reply using *Reply privately 
>>> to author *when sending the requested information. Additionally, 
>>> you may also inspect the downloadUrl and the list of processingErrors 
>>> in 
>>> the BatchJob to get possible reasons for the failure.
>>>
>>> Best regards,
>>> Peter
>>> 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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You 

Re: Abnormally high number of cancelled/failed batch jobs

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Jordan,

I took a look on our servers, and at first glance it does look like it 
could be the same issue. I've sent on the job IDs to my teammate who's 
assigned to this. I'll get back to you when I hear back. This looks like a 
tough one. Thank you for providing these job IDs.

Take care,
Nadine, AdWords API Team

On Tuesday, June 27, 2017 at 5:25:31 AM UTC-4, jor...@jcrocker.uk wrote:
>
> Hi Nadine,
>
> I am currently facing the same situation as Greg in that all jobs I send 
> are automatically going to a Cancelled status. These jobs are for product 
> partitions.
>
> A few example job ID's:
>
> 520125237
> 520125243
> 519862123
> 520125246
> 519445444
> 520125249
> 520125240
>
> These are all for account 682-998-6792.
>
> Could this be related to the same cause as Greg's issue?
>
> Kind regards,
> Jordan
>
> On Wednesday, March 1, 2017 at 7:20:33 PM UTC, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hi Greg,
>>
>> One of the engineers on my team found the root cause. We seem to be 
>> having a few difficulties with operations that have product partitions. 
>> We're currently putting some code in place to retry when those particular 
>> operations have issues.
>>
>> Cheers,
>> Nadine, AdWords API Team
>>
>> On Wednesday, March 1, 2017 at 10:44:39 AM UTC-5, Nadine Sundquist 
>> (AdWords API Team) wrote:
>>>
>>> Hi Greg,
>>>
>>> Thanks for all the helpful details! I started investigating on our 
>>> servers to track down why this is happening. On my initial pass of our 
>>> logs, I don't see a reason for the cancel happening when it appears that 
>>> the job is finishing (whether it has errors or not). I'm pulling in a few 
>>> more people here to take a look to help me solve this mystery. I'll get 
>>> back to you when we've made a bit more progress on this.
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Tuesday, February 28, 2017 at 11:00:44 AM UTC-5, GregT wrote:

 Hi, Peter.

 We don't actually log the SOAP for these because the SOAP calls 
 themselves aren't failing -- it's just that the status of the jobs are 
 eventually getting returned as cancelled. As mentioned in the original 
 post, some have no processing or other errors at all - just the status 
 cancelled. Others have that status and have a single processing error: 
 BatchJobService.INTERNAL_ERROR, with no other information in the 
 processing 
 errors. An example of the printout of all the fields we get for that error 
 is:

 errorType:BatchJobProcessingError, trigger:, 
 errorString:BatchJobProcessingError.INTERNAL_ERROR, fieldPath:, 
 reason:INTERNAL_ERROR

 A couple example jobs from yesterday that return the error (along with 
 being cancelled):
 450605098
 450816012

 A couple that have no error, but are just cancelled:
 450865617
 451028751

 All the ones listed in the original post fall into one of these two 
 categories, I believe.

 Thanks,
 Greg

 On Monday, February 27, 2017 at 10:07:26 PM UTC-6, Peter Oliquino wrote:
>
> Hello Greg,
>
> To help us investigate further, could you please provide us the SOAP 
> logs for both request and response of one of your failed BatchJobService 
> if 
> you were able to capture them. Please reply using *Reply privately to 
> author *when sending the requested information. Additionally, you may 
> also inspect the downloadUrl and the list of processingErrors in the 
> BatchJob to get possible reasons for the failure.
>
> Best regards,
> Peter
> 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+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.
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/26fdee65-bc72-44e2-b7c0-25304826761e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

['Nadine Sundquist (AdWords API Team)' via 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

On Monday, June 26, 2017 at 8:12:10 AM UTC-4, cv wrote:
>
> 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,
>
>
>
>
>
> On Thursday, 30 March 2017 19:42:23 UTC+5:30, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> 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
>>
>> On Thursday, March 30, 2017 at 12:28:50 AM UTC-4, cv wrote:
>>>
>>> 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] => 
>>> )
>>>
>>>
>>> On Monday, 29 February 2016 11:08:24 UTC+5:30, cv wrote:

 Hello Nadine,

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

 Thanks,

 On Thursday, 25 February 2016 20:29:45 UTC+5:30, Nadine Sundquist 
 (AdWords API Team) wrote:
>
> 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 
> 08 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 

Re: Unable to create DynamicSearchAd in v201705

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oliver,

Sometimes when the AdWords product is in transition, such as in this move 
from dynamic search ads to the new expanded dynamic search ads, you'll see 
that the AdWords UI and the AdWords API are not in perfect step with each 
other. There are times when the UI changes first, and there are other times 
when the API will change first. This happens to be one of those cases where 
you see the side effects of this process.

Please take this opportunity to encourage your users to move to expanded 
dynamic search ads 
. 
That way they can be ahead of the game. If you have any further questions, 
feel free to reach out.

Take care,
Nadine, AdWords API Team

On Thursday, June 22, 2017 at 6:05:24 AM UTC-4, Oliver wrote:
>
> Thanks.  However, we're still able to create these ads in the web 
> interface in this type of adgroup.This inconsistency makes it confusing 
> to our users who question why it's possible in web interface but not API.
>
>
>
> On Wednesday, 21 June 2017 18:21:16 UTC+1, Nadine Sundquist (AdWords API 
> Team) wrote:
>>
>> Hello Oliver,
>>
>> It turns out that you found a mistake in our blog post, and it took a bit 
>> of discussion to get everyone on the same page here. With this last release 
>> DSAs can no longer be added to ad groups of type SEARCH_STANDARD. We will 
>> be updating the blog post shortly. Thank you for catching this!
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Tuesday, June 13, 2017 at 12:24:14 PM UTC-4, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Greetings Oliver,
>>>
>>> I took a look into this as well. It does look unexpected. Thank you for 
>>> providing all the additional detail. I've started an internal thread to 
>>> start looking into it. I'll get back to you as soon as we make further 
>>> progress in figuring out what changed in our code base. If you don't hear 
>>> from me soon, feel free to bump this thread.
>>>
>>> Cheers,
>>> Nadine, AdWords API Team
>>>
>>> On Tuesday, June 13, 2017 at 2:49:29 AM UTC-4, Oliver wrote:

 Hi Shwetha,

 You say:
 *>> You can only create Dynamic Search Ads 
  
 in 
 ad groups with adGroupType 
 
  as 
 SEARCH_DYNAMIC_ADS.*

 We don't believe this is the case.  We're referring here to 
 *DynamicSearchAd 
 *and *not *ExpandedDynamicSearchAd.  We've always been able to create 
 *DynamicSearchAd* in adgroups with type  SEARCH_STANDARD.  The 
 documentation below also confirms we can do this:

 http://googleadsdeveloper.blogspot.co.uk/2017/05/validation-rules-for-new-dynamic-ad.html?m=0=fi

 The last paragraph in the above document says:
 *>> Ad groups with AdGroupType 
 
  of SEARCH_STANDARD are not 
 affected by this change. You can still continue adding expanded text ads, 
 dynamic search ads, call ads, and various criterion types 
  
 to 
 them.*

 Example adgroup ID:  19597050263

 Just to confirm, I'm not referring to creating the new Expanded DSA. 
  I'm referring to only DSA.

 Looking forward to hearing back from you.

 Oliver


 On Monday, 12 June 2017 17:28:21 UTC+1, Shwetha Vastrad (AdWords API 
 Team) wrote:
>
> Hi Oliver,
>
> You can only create Dynamic Search Ads 
> 
>  
> in ad groups with adGroupType 
> 
>  
> as SEARCH_DYNAMIC_ADS. If you try to create a ExpandedDynamicSearchAd 
> 
>  
> in an adGroup with adGroupType 
> 
>  
> as SEARCH_STANDARD, you'll get the 
> OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_AD_GROUP_TYPE error. 
> Could you provide an example AdGroupId where you are able to create an 
> ExpandedDynamicSearchAd in the UI? Please use *Reply privately to 
> author* when responding. 
>
> Thanks,
> Shwetha, 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

Re: Unable to create DynamicSearchAd in v201705

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Oliver,

It turns out that you found a mistake in our blog post, and it took a bit 
of discussion to get everyone on the same page here. With this last release 
DSAs can no longer be added to ad groups of type SEARCH_STANDARD. We will 
be updating the blog post shortly. Thank you for catching this!

Best,
Nadine, AdWords API Team

On Tuesday, June 13, 2017 at 12:24:14 PM UTC-4, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Greetings Oliver,
>
> I took a look into this as well. It does look unexpected. Thank you for 
> providing all the additional detail. I've started an internal thread to 
> start looking into it. I'll get back to you as soon as we make further 
> progress in figuring out what changed in our code base. If you don't hear 
> from me soon, feel free to bump this thread.
>
> Cheers,
> Nadine, AdWords API Team
>
> On Tuesday, June 13, 2017 at 2:49:29 AM UTC-4, Oliver wrote:
>>
>> Hi Shwetha,
>>
>> You say:
>> *>> You can only create Dynamic Search Ads 
>>  
>> in 
>> ad groups with adGroupType 
>> 
>>  as 
>> SEARCH_DYNAMIC_ADS.*
>>
>> We don't believe this is the case.  We're referring here to *DynamicSearchAd 
>> *and *not *ExpandedDynamicSearchAd.  We've always been able to create 
>> *DynamicSearchAd* in adgroups with type  SEARCH_STANDARD.  The 
>> documentation below also confirms we can do this:
>>
>> http://googleadsdeveloper.blogspot.co.uk/2017/05/validation-rules-for-new-dynamic-ad.html?m=0=fi
>>
>> The last paragraph in the above document says:
>> *>> Ad groups with AdGroupType 
>> 
>>  of SEARCH_STANDARD are not 
>> affected by this change. You can still continue adding expanded text ads, 
>> dynamic search ads, call ads, and various criterion types 
>>  to 
>> them.*
>>
>> Example adgroup ID:  19597050263
>>
>> Just to confirm, I'm not referring to creating the new Expanded DSA.  I'm 
>> referring to only DSA.
>>
>> Looking forward to hearing back from you.
>>
>> Oliver
>>
>>
>> On Monday, 12 June 2017 17:28:21 UTC+1, Shwetha Vastrad (AdWords API 
>> Team) wrote:
>>>
>>> Hi Oliver,
>>>
>>> You can only create Dynamic Search Ads 
>>>  
>>> in ad groups with adGroupType 
>>> 
>>>  
>>> as SEARCH_DYNAMIC_ADS. If you try to create a ExpandedDynamicSearchAd 
>>> 
>>>  
>>> in an adGroup with adGroupType 
>>> 
>>>  
>>> as SEARCH_STANDARD, you'll get the 
>>> OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_AD_GROUP_TYPE error. 
>>> Could you provide an example AdGroupId where you are able to create an 
>>> ExpandedDynamicSearchAd in the UI? Please use *Reply privately to 
>>> author* when responding. 
>>>
>>> Thanks,
>>> Shwetha, 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+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.
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/e9c59db8-d5bf-4d3d-8d46-913067dce0cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to get the account Labels using account label service

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

Could you please start a new thread? This looks like a new issue, so it 
would be so helpful for you to do that. In that post, it would be great if 
you had the SOAP XML (with personal information not shown). To look up an 
error like this, we would need the *requestId* that is in the response that 
comes back.

Thanks,
Nadine, AdWords API Team

On Wednesday, June 21, 2017 at 10:43:23 AM UTC-4, silent_coder wrote:
>
> Hi nadine,
>
> When I use AccountLabels in Selector, it gives me:
>
> InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>
> What could be the problem here? Thanks
>
> On Saturday, December 5, 2015 at 12:00:30 AM UTC+8, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hi Kamran,
>>
>> Thanks for clarifying! The service you'll want to use is 
>> ManagedCustomerService->get() 
>> 
>>  at 
>> the manager account level of your hierarchy. In your Selector 
>> ,
>>  
>> you'll want to choose:
>>
>>- CustomerId
>>- AccountLabels
>>
>> That will give you a mapping of each account with its associated account 
>> labels.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Friday, December 4, 2015 at 7:39:28 AM UTC-5, rc1...@gmail.com wrote:
>>>
>>> Hi Nadine,
>>>
>>> Thank you for the quick update now I understand how to get the labels on 
>>> account level.
>>> Please see below for the request ID i used to get the labels.
>>> 00052611ba919d700ac246870d033586
>>>
>>> But sorry I think I was not very clear earlier, actually I want to get 
>>> Labels associated with particular account, e.g. i have many accounts in and 
>>> i want to know through API, which labels are associated with each account.
>>>
>>> Can you please let me know which API request should I be using to get 
>>> this data?
>>>
>>> Regards,
>>>
>>> Kamran
>>>
>>> On Thursday, December 3, 2015 at 6:06:15 PM UTC-5, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 Hi Kamran,

 Thanks for providing the *requestId*. That really made everything a 
 lot easier to track down. So, it looks like you're calling 
 AccountLabelService 
 
  against 
 a customer account, rather than a manager account. Try using the 
 LabelService 
 
  
 instead at that level of your account hierarchy. If you call 
 AccountLabelService 
 one level above that account, which would be the manager account level, 
 then you would get back account level labels.

 Happy coding,
 Nadine, AdWords API Team

 On Thursday, December 3, 2015 at 3:15:34 PM UTC-5, rc1...@gmail.com 
 wrote:
>
> Hi Team,
>
> I am not able to get the Labels associated with the account.
>
> I am using Account Label Service to get the account labels.
>
> The Request ID is mentioned below. Please let me know if you need 
> anything else.
>
> 00052603c66655900ac246870d033586
>
> Thanks,
>
> Kamran
>


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/3199ea83-fa99-4a6a-b906-9d38bcebefcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: OperationAccessDenied.fieldPathElements not an array, Perl AdWords API v201702

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Phillip,

Thanks for all the additional information. Giving us the batch job IDs 
meant I could retrieve the output that was being parsed, which made it 
easily reproducible. It was indeed an issue in the Perl library. I've made 
a fix, and the fix will be in the next push of the Perl client library. In 
the meantime, if you would like to fix it in your own code base until that 
push goes out, here's the fix.

In ErrorUtils.pm replace:

($field_path_elements && (scalar $field_path_elements > 0))


with
 

>  ($field_path_elements && (scalar @{$field_path_elements} > 0))


The issue was that if the field path elements for that error only had one 
element (which is not very common), Perl assumes it's just a string rather 
than an array. By forcing it always to an array, everything works properly. 
I gave it a try across all your errors, and it looks good to go.

Happy coding,
Nadine, AdWords API Team 

On Wednesday, June 14, 2017 at 5:24:02 PM UTC-4, Shwetha Vastrad (AdWords 
API Team) wrote:
>
> Hi Phillip, 
>
> In that case, do you happen to have the BatchJobIds in which this error 
> occurred? It'll be helpful in identifying the source of the issue. 
>
> Thanks,
> Shwetha, 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+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.
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/9cb47318-cdec-4fca-89a6-0d8ac69f7aee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to create DynamicSearchAd in v201705

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings Oliver,

I took a look into this as well. It does look unexpected. Thank you for 
providing all the additional detail. I've started an internal thread to 
start looking into it. I'll get back to you as soon as we make further 
progress in figuring out what changed in our code base. If you don't hear 
from me soon, feel free to bump this thread.

Cheers,
Nadine, AdWords API Team

On Tuesday, June 13, 2017 at 2:49:29 AM UTC-4, Oliver wrote:
>
> Hi Shwetha,
>
> You say:
> *>> You can only create Dynamic Search Ads 
>  in 
> ad groups with adGroupType 
> 
>  as 
> SEARCH_DYNAMIC_ADS.*
>
> We don't believe this is the case.  We're referring here to *DynamicSearchAd 
> *and *not *ExpandedDynamicSearchAd.  We've always been able to create 
> *DynamicSearchAd* in adgroups with type  SEARCH_STANDARD.  The 
> documentation below also confirms we can do this:
>
> http://googleadsdeveloper.blogspot.co.uk/2017/05/validation-rules-for-new-dynamic-ad.html?m=0=fi
>
> The last paragraph in the above document says:
> *>> Ad groups with AdGroupType 
> 
>  of SEARCH_STANDARD are not 
> affected by this change. You can still continue adding expanded text ads, 
> dynamic search ads, call ads, and various criterion types 
>  to 
> them.*
>
> Example adgroup ID:  19597050263
>
> Just to confirm, I'm not referring to creating the new Expanded DSA.  I'm 
> referring to only DSA.
>
> Looking forward to hearing back from you.
>
> Oliver
>
>
> On Monday, 12 June 2017 17:28:21 UTC+1, Shwetha Vastrad (AdWords API Team) 
> wrote:
>>
>> Hi Oliver,
>>
>> You can only create Dynamic Search Ads 
>>  
>> in ad groups with adGroupType 
>> 
>>  
>> as SEARCH_DYNAMIC_ADS. If you try to create a ExpandedDynamicSearchAd 
>> 
>>  
>> in an adGroup with adGroupType 
>> 
>>  
>> as SEARCH_STANDARD, you'll get the 
>> OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_AD_GROUP_TYPE error. 
>> Could you provide an example AdGroupId where you are able to create an 
>> ExpandedDynamicSearchAd in the UI? Please use *Reply privately to author* 
>> when responding. 
>>
>> Thanks,
>> Shwetha, 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+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.
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/caa92a51-d71c-4eb9-a3f0-8e0ed6aa4305%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Click Performance Report - LopRegionCriteriaId is not available for clicks in the US

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello,

I now see what you're getting at.

Query: SELECT AoiMetroCriteriaId, LopMetroCriteriaId FROM 
> CLICK_PERFORMANCE_REPORT DURING YESTERDAY
> Result: Returns only --.
> Query: SELECT MetroCriteriaId FROM GEO_PERFORMANCE_REPORT DURING YESTERDAY
> Result: Returns IDs for everything.


I ran the queries just as you described and saw that behavior. I would 
expect that behavior to be consistent across reports. I've filed an issue, 
and we're working on trying to figure out what's going on. I'll get back to 
you when we've made more progress on figuring out why there's a difference. 
Thank you for being so patient in describing this.

Best,
Nadine, AdWords API Team

On Friday, May 26, 2017 at 12:08:35 AM UTC-4, do...@predictivebid.com wrote:
>
> Hi,
>
> Thank you for your response.
>
> 1. If you generate a Geo Performance report, with this field: 
> https://developers.google.com/adwords/api/docs/appendix/reports/geo-performance-report#regioncriteriaid,
>  
> you can clearly see there are states for US locations in the region 
> criteria id, and I've been using this report for a long time - it has 
> always been like this. So, if I understand correctly, in the Geo 
> Performance report it's not the same region definition as in the Click 
> Performance report?
> 2. If you define a region as a Geo Target with Target Type "Region". How 
> do you define Metro? I don't see it in the Target Type
>
> On Friday, May 26, 2017 at 1:43:04 AM UTC+3, Nadine Sundquist (AdWords API 
> Team) wrote:
>>
>> Greetings!
>>
>> When comparing the UI to the API, it can be a little confusing because 
>> phrases like Metro or Region in the UI can get overloaded and encompass 
>> multiple things. When it comes to the API, the Geotargets guide 
>>  
>> is the things we rely on. In the Geotargets guide, there's a link to the 
>> AdWords 
>> API Location Criteria table 
>> .
>>  
>> I'll be working off that table to explain what's going on.
>>
>> One of the things that can seem confusing is that if a specific location 
>> in the United States is returned, there is no region. Let's cover that 
>> first. If you go into that table and filter by *Country Code* of *US*, 
>> you'll see that the resulting table has a lot of *Target Types*. If you 
>> then do another filter on top of that of *Target Type, *you'll see that 
>> there isn't an option of *Region*. In our system, the United States does 
>> not have any regions. Some other countries, like China with country code 
>> CN, do have regions. That's why the *Region* field is always *--* when 
>> the United States is the specific country. In the API, we rely completely 
>> on that *Target Type* to determine if a column gets populated. 
>>
>> In that table, if you choose *Criteria Id 9052894*, like you mentioned 
>> earlier, you'll see that the target type is *City*, and that's why the 
>> City column gets populated. Another factor that plays into this is the 
>> *Parent 
>> ID* in that table. If you have a specific location that is a city, then 
>> the city will get populated. If the parent of that item is a state, and 
>> then the parent of that state is a country, then the *Country* column 
>> will get populated. We work our way up the chain of parent IDs.
>>
>> I hope that clears things up a bit! If you need any further help, feel 
>> free to reach out.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Thursday, May 25, 2017 at 12:18:24 PM UTC-4, do...@predictivebid.com 
>> wrote:
>>>
>>> I forgot to mention: The most specific location was 9052894 and *City 
>>> (Physical location)* was 9052894, as I would expect.
>>>
>>> On Thursday, May 25, 2017 at 7:01:10 PM UTC+3, do...@predictivebid.com 
>>> wrote:

 I just gave it as an example. I believe in other reports you will see 
 the region as a state, even if the most specific is a state. this is an 
 inconsistent behavior
 I have also examples of cities, like 9052894 (Spanish Lake), where no 
 region was available. like I said, I didn't find even one case where I had 
 a region for US locations. I Believe this is a bug

 On Thursday, May 25, 2017 at 6:57:05 PM UTC+3, Sreelakshmi Sasidharan 
 (AdWords API Team) wrote:
>
> Hi, 
>
> In the particular example shared, the criteria Id : 21176 is of target 
> type 'State'. Which means that any target type which is lesser in 
> hierarchy 
> (of a location) would not have a value to report. And the results in your 
> case seems to be as expected. All the three values listed below are 
> somewhat similar to a 'City'.
>
> * City
> * Metro Area 
> * Region
>
> You could check this 
>  guide for 
> better clarity and examples for most common target type(s). If you happen 

Re: Click Performance Report - LopRegionCriteriaId is not available for clicks in the US

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Greetings!

When comparing the UI to the API, it can be a little confusing because 
phrases like Metro or Region in the UI can get overloaded and encompass 
multiple things. When it comes to the API, the Geotargets guide 
 is 
the things we rely on. In the Geotargets guide, there's a link to the AdWords 
API Location Criteria table 
.
 
I'll be working off that table to explain what's going on.

One of the things that can seem confusing is that if a specific location in 
the United States is returned, there is no region. Let's cover that first. 
If you go into that table and filter by *Country Code* of *US*, you'll see 
that the resulting table has a lot of *Target Types*. If you then do 
another filter on top of that of *Target Type, *you'll see that there isn't 
an option of *Region*. In our system, the United States does not have any 
regions. Some other countries, like China with country code CN, do have 
regions. That's why the *Region* field is always *--* when the United 
States is the specific country. In the API, we rely completely on that *Target 
Type* to determine if a column gets populated. 

In that table, if you choose *Criteria Id 9052894*, like you mentioned 
earlier, you'll see that the target type is *City*, and that's why the City 
column gets populated. Another factor that plays into this is the *Parent 
ID* in that table. If you have a specific location that is a city, then the 
city will get populated. If the parent of that item is a state, and then 
the parent of that state is a country, then the *Country* column will get 
populated. We work our way up the chain of parent IDs.

I hope that clears things up a bit! If you need any further help, feel free 
to reach out.

Best,
Nadine, AdWords API Team

On Thursday, May 25, 2017 at 12:18:24 PM UTC-4, do...@predictivebid.com 
wrote:
>
> I forgot to mention: The most specific location was 9052894 and *City 
> (Physical location)* was 9052894, as I would expect.
>
> On Thursday, May 25, 2017 at 7:01:10 PM UTC+3, do...@predictivebid.com 
> wrote:
>>
>> I just gave it as an example. I believe in other reports you will see the 
>> region as a state, even if the most specific is a state. this is an 
>> inconsistent behavior
>> I have also examples of cities, like 9052894 (Spanish Lake), where no 
>> region was available. like I said, I didn't find even one case where I had 
>> a region for US locations. I Believe this is a bug
>>
>> On Thursday, May 25, 2017 at 6:57:05 PM UTC+3, Sreelakshmi Sasidharan 
>> (AdWords API Team) wrote:
>>>
>>> Hi, 
>>>
>>> In the particular example shared, the criteria Id : 21176 is of target 
>>> type 'State'. Which means that any target type which is lesser in hierarchy 
>>> (of a location) would not have a value to report. And the results in your 
>>> case seems to be as expected. All the three values listed below are 
>>> somewhat similar to a 'City'.
>>>
>>> * City
>>> * Metro Area 
>>> * Region
>>>
>>> You could check this 
>>>  guide for 
>>> better clarity and examples for most common target type(s). If you happen 
>>> to notice missing data where the target type of the criteria Id is postal 
>>> code,city etc., Please share the downloaded report along with your client 
>>> customer Id so that I can debug further. You could also check this 
>>> 
>>>  forum 
>>> discussion about the location hierarchy for better clarity. 
>>>
>>> Thanks,
>>> Sreelakshmi, 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+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.
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/4f8a7bd8-cedd-4f4c-9b1b-e28cc9869a3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What is the ClickType display value in the Ad Performance Report for "Purchase on Google"?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Charlie,

That enum is indeed missing. Our team is currently working on adding it. 
I'll post back here when it's ready to go.

Cheers,
Nadine, AdWords API Team

On Tuesday, May 2, 2017 at 12:08:37 PM UTC-4, char...@roirevolution.com 
wrote:
>
> Hello all,
>
> I see this data in performance reports now, but it doesn't appear in the 
> enums in the documentation, so we can't filter for it.
>
> Does anyone know what the enum value is or if this is not available yet in 
> the API?
>
> Thanks!
>
>
> On Tuesday, December 6, 2016 at 4:39:51 PM UTC-5, HK wrote:
>>
>> As far as I can tell, this is now available in the ad performance report 
>> as follows:
>>
>> clickType="Shopping ad - Sell on Google"
>>
>> Hans 
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/8d9f3738-4caa-46d3-8538-d530bc87063f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bounce Rate in Campaign Performance Report segments (Bug probably)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi Vlad,

This should be fixed now as of yesterday. Could you please give this a try 
to see if it now looks good to you? If not, please get back to me.

Thanks,
Nadine, AdWords API Team

On Friday, April 14, 2017 at 9:08:16 AM UTC-4, Nadine Sundquist (AdWords 
API Team) wrote:
>
> Hello Vlad,
>
> I've gotten a couple of other reports from people on this. We're actively 
> working on a solution. Thanks for writing this out so clearly! It made it 
> easy to flag that I've seen this before. I'll post back here when we've 
> made more progress on finding the source of the issue.
>
> Best,
> Nadine, AdWords API Team
>
> On Thursday, April 13, 2017 at 11:15:41 AM UTC-4, Vlad Zloteanu wrote:
>>
>> I've seen this on DSA campaigns (maybe a DSA bug).
>>
>> Adwords Account ID (client customer ID): 5845103608
>>
>>
>> Fetching this report through the API:
>>
>> {'dateRangeType': 'CUSTOM_DATE',
>>  'downloadFormat': 'CSV',
>>  'reportName': 'Custom CAMPAIGN_PERFORMANCE_REPORT',
>>  'reportType': 'CAMPAIGN_PERFORMANCE_REPORT',
>>  'selector': {'dateRange': {'max': '20170413', 'min': '20170411'},
>>   'fields': ['Date', 'CampaignId', 'BounceRate'],
>>   'predicates': []}}
>>
>> Excerpt of the received CSV:
>>
>> ['2017-04-12,347606525,0.00%\n',
>> * '2017-04-11,347606525,100.00%\n',*
>> * '2017-04-11,347606525,47.03%\n',*
>>  '2017-04-12,347606525,44.35%\n',
>>  '2017-04-13,347606525,40.66%\n']
>>
>> As you can see, some dates are present twice, with different bounce rates.
>>
>> When adding another columns like Clicks or ClickAssistedConversions, 
>> Cost, the report is re-aggregated (example: the cost is doubled).
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/46f8dc64-e663-4d5c-92f5-bd70f86477e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GMB Extensions, can't use personal account?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hi JC,

Woot! Glad you made some progress. I was surprised as well that the 
personal account didn't work. Please stick to business accounts. In the 
meantime, I'm going to check around here to find out why a personal account 
didn't work and if that was intentional. I'll get back to you once I find 
out more.

Take care,
Nadine, AdWords API Team

On Thursday, April 27, 2017 at 10:19:14 PM UTC-4, JC Lee wrote:
>
> Hi Nadine,
>
> Using business account works! But as Ivan noted above, personal accounts 
> should work too.
>
> Should I limit my users to business accounts?
>
> On Friday, 28 April 2017 00:05:45 UTC+8, Nadine Sundquist (AdWords API 
> Team) wrote:
>>
>> Hello JC,
>>
>> Thanks for sending us those details. I was able to find the stack trace 
>> on our servers to get more information based on what you provided. It 
>> appears that our code is looking for a GMB business account rather than a 
>> GMB personal account. Can you try creating a GMB business account 
>>  and then giving it 
>> another try?
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Thursday, April 27, 2017 at 12:06:30 AM UTC-4, JC Lee wrote:
>>>
>>> I have replied privately with the details you asked for.
>>>
>>> Unfortunately, I haven't gotten a reply about the personal account id 
>>> from GMB forum.
>>>
>>> On Wednesday, 26 April 2017 19:27:32 UTC+8, Ivan Bautista wrote:

 Hi JC,

 With regards to retrieving your personal account id, it would be best 
 to confirm with the GMB team 
  as we only 
 handle the AdWords API part of the integration.

 As for the InternalApiError.UNEXPECTED_INTERNAL_API_ERROR 
 ,
  
 this could sometimes be triggered by a temporary server-side issue. Could 
 you retry running the service again and see if the error persists?

 Also, to help us investigate further, could you reply to us privately 
 (using *reply privately to author* option) with your SOAP request and 
 response?

 Regards,
 Ivan
 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+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.
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/f6349832-121e-4ffa-9c74-ebef0b6ad500%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GMB Extensions, can't use personal account?

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello JC,

Thanks for sending us those details. I was able to find the stack trace on 
our servers to get more information based on what you provided. It appears 
that our code is looking for a GMB business account rather than a GMB 
personal account. Can you try creating a GMB business account 
 and then giving it 
another try?

Thanks,
Nadine, AdWords API Team

On Thursday, April 27, 2017 at 12:06:30 AM UTC-4, JC Lee wrote:
>
> I have replied privately with the details you asked for.
>
> Unfortunately, I haven't gotten a reply about the personal account id from 
> GMB forum.
>
> On Wednesday, 26 April 2017 19:27:32 UTC+8, Ivan Bautista wrote:
>>
>> Hi JC,
>>
>> With regards to retrieving your personal account id, it would be best to 
>> confirm with the GMB team 
>>  as we only 
>> handle the AdWords API part of the integration.
>>
>> As for the InternalApiError.UNEXPECTED_INTERNAL_API_ERROR 
>> ,
>>  
>> this could sometimes be triggered by a temporary server-side issue. Could 
>> you retry running the service again and see if the error persists?
>>
>> Also, to help us investigate further, could you reply to us privately 
>> (using *reply privately to author* option) with your SOAP request and 
>> response?
>>
>> Regards,
>> Ivan
>> 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+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.
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/676ae8de-6597-4826-80d5-e5f643623da5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bounce Rate in Campaign Performance Report segments (Bug probably)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Vlad,

I've gotten a couple of other reports from people on this. We're actively 
working on a solution. Thanks for writing this out so clearly! It made it 
easy to flag that I've seen this before. I'll post back here when we've 
made more progress on finding the source of the issue.

Best,
Nadine, AdWords API Team

On Thursday, April 13, 2017 at 11:15:41 AM UTC-4, Vlad Zloteanu wrote:
>
> I've seen this on DSA campaigns (maybe a DSA bug).
>
> Adwords Account ID (client customer ID): 5845103608
>
>
> Fetching this report through the API:
>
> {'dateRangeType': 'CUSTOM_DATE',
>  'downloadFormat': 'CSV',
>  'reportName': 'Custom CAMPAIGN_PERFORMANCE_REPORT',
>  'reportType': 'CAMPAIGN_PERFORMANCE_REPORT',
>  'selector': {'dateRange': {'max': '20170413', 'min': '20170411'},
>   'fields': ['Date', 'CampaignId', 'BounceRate'],
>   'predicates': []}}
>
> Excerpt of the received CSV:
>
> ['2017-04-12,347606525,0.00%\n',
> * '2017-04-11,347606525,100.00%\n',*
> * '2017-04-11,347606525,47.03%\n',*
>  '2017-04-12,347606525,44.35%\n',
>  '2017-04-13,347606525,40.66%\n']
>
> As you can see, some dates are present twice, with different bounce rates.
>
> When adding another columns like Clicks or ClickAssistedConversions, Cost, 
> the report is re-aggregated (example: the cost is doubled).
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/85bcb87f-7484-4749-a561-f830ee37bc39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API Errors Suddenly Occuring (InternalApiError.UNEXPECTED_INTERNAL_API_ERROR) (ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKEND)

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Robert,

There aren't any known issues right now with those particular errors. If 
those errors are persisting, please start a new forum thread, and we can 
take a look to see what's going on. It could be something specific that 
you're passing in that is causing the error.

Thanks,
Nadine, AdWords API Team

On Wednesday, April 5, 2017 at 9:32:49 AM UTC-4, Robert Dorsey II wrote:
>
> Hello Nadine,
>
> We are seeing the same errors in the last 5 days intermittently, on our 
> end, do you know if there is an internal Google issue going on with the 
> API? We are trying to identify if it is a problem on our end or the API 
> itself.
>
> Thank you!
>
> On Thursday, August 25, 2016 at 9:18:13 AM UTC-4, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hi Mark and Greg,
>>
>> Thanks for reporting this. Yes, there were some disruptive issues that 
>> were happening at that time on our side. They were resolved within an hour. 
>> If you continue to see anything like this, please get back to me right away.
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Wednesday, August 24, 2016 at 6:43:34 PM UTC-4, Mark Rogoyski wrote:
>>>
>>> The service seems to have recovered and we no longer see the abundance 
>>> of errors.
>>>
>>> Any update on the Google side on what the issue was?
>>>
>>> On Wednesday, August 24, 2016 at 2:44:29 PM UTC-7, GregT wrote:

 We are seeing the same kind of thing. It is taking a large number of 
 retries to get any calls to work.

 Thanks,
 Greg

 On Wednesday, August 24, 2016 at 4:38:29 PM UTC-5, Mark Rogoyski wrote:
>
> Starting at around 14:14 PDT, we started getting an unusually high 
> error rate using the API (Using v201605)
>
> We are getting the following errors on a large number of API requests:
> - InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
> - ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKEND
>
> Did something change on the AdWords API side around 14:14 PDT today 
> (Aug 24)?
>


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/3c001af0-f4e0-421c-af88-d55a7601b651%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Performance problems downloading criteria report via API

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Paul,

The only reasons I can think of you getting a RATE_EXCEEDED 

 
would be if you were retrying on error quite rapidly due to this issue or 
if you have Basic access, and you exceeded your limit. Unfortunately, we 
can't do a reset for that. With the error, you should have gotten a few 
more specifics if you need to wait another 30 seconds or if you exceeded 
the number of operations per day. Please take a look RATE_EXCEEDED under 
Common Errors 

 
for more detail on how to respond to an error like this. If you need 
further help, please start a new forum thread, and my team would be happy 
to help.

Thanks,
Nadine, AdWords API Team

On Tuesday, April 4, 2017 at 10:02:12 AM UTC-4, Paul Newbury wrote:
>
> Cheers guys!
> I'm getting RATE_EXCEEDED, just curious if there's a way I can see what 
> time this is reset in my account? Or, maybe, is this a knock on effect from 
> the earlier issue?
>
> Thanks again
>
> On Monday, April 3, 2017 at 9:41:29 PM UTC+1, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hello Everyone!
>>
>> We've resolved the issue. The duration of this issue lasted from March 
>> 31st until today. You should no longer be seeing this error. If you see it 
>> again, please get back to me. We're currently working on putting measures 
>> in place to ensure that this particular issue does not pop up again.
>>
>> Take care,
>> Nadine, AdWords API Team
>>
>> On Monday, April 3, 2017 at 4:10:21 PM UTC-4, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> Hi Josh,
>>>
>>> Please start a new thread on this one. That'll make it easier for us to 
>>> track and for people to +1 your particular issue.
>>>
>>> Thanks,
>>> Nadine, AdWords API Team
>>>
>>> On Monday, April 3, 2017 at 3:41:11 PM UTC-4, Josh Gabel wrote:

 We've been noticing a different type of reportdownload issue.

 When running the following AWQL report request to v201702 we're getting 
 a blank report returned. No actual errors reported, just a report with 
 empty data rows. I have confirmed that we had campaigns that meet the 
 conditions with clicks, impressions, and cost, but can't get the report to 
 go send data back.

 SELECT CampaignId, CampaignName, CampaignStatus, Clicks, Impressions, 
 Cost FROM CAMPAIGN_PERFORMANCE_REPORT WHERE CampaignStatus != 'REMOVED' 
 AND 
 Impressions > 0 DURING 20170327,20170402

 On Monday, 3 April 2017 14:05:49 UTC-4, Alex wrote:
>
> Hey Vishal,
>
> I've realised we're getting the same issues as others here, with the 
> Keywords Performance Report too. Saw the error last Friday, and again 
> over 
> the weekend, and this morning.
>
> Has anyone got any information about the potential cause?
>
>
> On Friday, March 31, 2017 at 8:16:01 PM UTC+1, LE Max wrote:
>>
>> We have been experiencing problems for the last several hours in 
>> retrieving reports via the API. 
>>
>>  
>>
>> When we request a criteria report, we are getting the following 
>> message: 'Unable to create report, Type: 
>> ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE'
>>
>>  
>>
>> We have made repeated attempts with the same failed result. Can you 
>> please let me know if there is an issue with the system?
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/a12505b9-42e1-4144-9f8a-fb299778508e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Performance problems downloading criteria report via API

['Nadine Sundquist (AdWords API Team)' via AdWords API Forum]

Hello Everyone!

We've resolved the issue. The duration of this issue lasted from March 31st 
until today. You should no longer be seeing this error. If you see it 
again, please get back to me. We're currently working on putting measures 
in place to ensure that this particular issue does not pop up again.

Take care,
Nadine, AdWords API Team

On Monday, April 3, 2017 at 4:10:21 PM UTC-4, Nadine Sundquist (AdWords API 
Team) wrote:
>
> Hi Josh,
>
> Please start a new thread on this one. That'll make it easier for us to 
> track and for people to +1 your particular issue.
>
> Thanks,
> Nadine, AdWords API Team
>
> On Monday, April 3, 2017 at 3:41:11 PM UTC-4, Josh Gabel wrote:
>>
>> We've been noticing a different type of reportdownload issue.
>>
>> When running the following AWQL report request to v201702 we're getting a 
>> blank report returned. No actual errors reported, just a report with empty 
>> data rows. I have confirmed that we had campaigns that meet the conditions 
>> with clicks, impressions, and cost, but can't get the report to go send 
>> data back.
>>
>> SELECT CampaignId, CampaignName, CampaignStatus, Clicks, Impressions, 
>> Cost FROM CAMPAIGN_PERFORMANCE_REPORT WHERE CampaignStatus != 'REMOVED' AND 
>> Impressions > 0 DURING 20170327,20170402
>>
>> On Monday, 3 April 2017 14:05:49 UTC-4, Alex wrote:
>>>
>>> Hey Vishal,
>>>
>>> I've realised we're getting the same issues as others here, with the 
>>> Keywords Performance Report too. Saw the error last Friday, and again over 
>>> the weekend, and this morning.
>>>
>>> Has anyone got any information about the potential cause?
>>>
>>>
>>> On Friday, March 31, 2017 at 8:16:01 PM UTC+1, LE Max wrote:

 We have been experiencing problems for the last several hours in 
 retrieving reports via the API. 

  

 When we request a criteria report, we are getting the following 
 message: 'Unable to create report, Type: 
 ReportDownloadError.ERROR_WRITING_REPORT_TO_FILE'

  

 We have made repeated attempts with the same failed result. Can you 
 please let me know if there is an issue with the system?

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+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.
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/a398470b-f74c-4c0b-ba38-8129a6f6c8a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.