Re: TargetingIdeaService range of dates

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

The custom filter has not been added yet. However, this is available in the 
KeywordPlanService 
<https://developers.google.com/google-ads/api/reference/rpc/google.ads.googleads.v0.services#google.ads.googleads.v0.services.KeywordPlanService>
 
of the new Google Ads API we announced in April 
<https://ads-developers.googleblog.com/2018/04/join-beta-for-new-adwords-api.html>,
 
where you can set the forecast_period 
<https://developers.google.com/google-ads/api/docs/fields/keyword_plan#keyword_planforecast_period>
 
of a plan to one of *NEXT_WEEK*, *NEXT_MONTH*, or *NEXT_QUARTER*.

Thanks,
Josh, AdWords API Team

On Tuesday, December 11, 2018 at 6:06:50 PM UTC-5, Hitesh Paryani wrote:
>
> Hi there Josh,
>
> Have you added the custom range filter yet?
>
> On Friday, March 2, 2018 at 7:35:29 PM UTC+5:30, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> No updates to report at this time. We'll be sure to announce any changes 
>> in release notes 
>> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201802>
>>  and 
>> on our blog 
>> <http://googleadsdeveloper.blogspot.com/search/label/adwords_api> if 
>> this happens.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, March 2, 2018 at 1:23:47 AM UTC-5, ta...@evolvedigitallabs.com 
>> wrote:
>>>
>>> Hi,
>>>
>>> Any update in this topic again? Do we have option to give custom date 
>>> range in TargetingIdeaService in version vv201705? Specifically, with 
>>> python.
>>> Thanks!
>>>
>>> On Tuesday, November 24, 2015 at 8:21:33 AM UTC-6, Josh Radcliff 
>>> (AdWords API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> There have not been any changes to *TargetingIdeaService* around 
>>>> dates. The service still only returns *TARGETED_MONTHLY_SEARCHES* for 
>>>> the last 12 months.
>>>>
>>>> Best regards,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, November 24, 2015 at 8:44:28 AM UTC-5, Deepa Varma wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>  Any update in this topic ? Do we have option to give date 
>>>>> range in TargetingIdeaService in version v201509 ? Please help 
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, 3 September 2014 01:59:15 UTC+5:30, Josh Radcliff 
>>>>> (AdWords API Team) wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The API does not support custom date ranges. The closest you can get 
>>>>>> to approximating that functionality is to include the 
>>>>>> *TARGETED_MONTHLY_SEARCHES* attribute type you mentioned in your 
>>>>>> request.
>>>>>>
>>>>>> Best regards,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Tuesday, September 2, 2014 4:55:29 AM UTC-4, Alex wrote:
>>>>>>>
>>>>>>> Hello
>>>>>>>
>>>>>>> I am trying to use PHP TargetingIdeaService (v201402) to get 
>>>>>>> TARGETED_MONTHLY_SEARCHES. 
>>>>>>> Is it possible to restrict the result of a range of dates, as it 
>>>>>>> happens in KeywordPlanner ( 
>>>>>>> http://gyazo.com/568f5499d1096ba05e776a05c135b4f9 )? 
>>>>>>>
>>>>>>
> This communication is confidential and privileged and is directed to and 
> for the use of the addressee only. The recipient if not the addressee 
> should not use this message if erroneously received, and access and use of 
> this e-mail in any manner by anyone other than the addressee is 
> unauthorized. If you are not the intended recipient, please notify the 
> sender by return email and immediately destroy all copies of this message 
> and any attachments and delete it from your computer system permanently. 
> The recipient acknowledges that Switchme Technologies and Services Pvt 
> Limited may be unable to exercise control or ensure or guarantee the 
> integrity of the text of the email message and the text is not warranted as 
> to completeness and accuracy. Before opening and accessing the attachment, 
> if any, please check and scan for virus.

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/66428be0-6662-4b54-9893-8a3ea56d4bc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot find AdWords API Center

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Heber,

Could you start a separate topic for this question so one of my colleagues 
can assist? This topic covers a variety of issues going all the way back to 
2014, so it's getting difficult for others to follow. I'm going to lock the 
topic to avoid confusion.

Thanks,
Josh, AdWords API Team

On Wednesday, November 28, 2018 at 6:00:35 PM UTC-5, Heber Olivar Silva 
wrote:
>
> Hi Josh, 
>
> The Central API did not appear to my account and when I invoke 
> method managedCustomerService I receive the tag totalNumEntries with value 
> '0' (zero).
>
> Is there anything else to approve or submit?
>
> Let me know if you need any further information.
>
>
> Best Regards,
> Heber Olivar
> -
>
>
> On Thursday, July 19, 2018 at 2:35:41 PM UTC-3, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Stephane,
>>
>> Did you create a production manager account or a test account 
>> <https://developers.google.com/adwords/api/docs/test-accounts>? I ask 
>> because you'll only see the *AdWords API Center* from a production 
>> manager account. You won't see it if your account is either of the 
>> following:
>>
>> a) A test manager account
>> b) A non-manager (client) account
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, July 19, 2018 at 12:26:46 AM UTC-4, Stephane Michot wrote:
>>>
>>> Hi,
>>>
>>> I'm having the same issue, I cannot see from the menu AdWords API Center 
>>> ( neither new interface/old). Despite I've tried the steps you suggested, 
>>> create a Manager Account, etc... Maybe I do something wrong...
>>>
>>> Any suggestions?
>>>
>>> Thanks
>>>
>>> Le mardi 10 juillet 2018 14:45:32 UTC+2, Josh Radcliff (AdWords API 
>>> Team) a écrit :
>>>>
>>>> Hi,
>>>>
>>>> Sorry this has been so frustrating for you. Hopefully I can clear a few 
>>>> things up.
>>>>
>>>> First, you can only apply for a developer token under a production 
>>>> manager account. Once you've applied:
>>>>
>>>>- While your token is pending approval, you can use that developer 
>>>>token to issue API requests against *any* *test *account, 
>>>>regardless of its account hierarchy, provided your request includes 
>>>> OAuth 
>>>>credentials for the account you are issuing the API request against 
>>>>(specified via the clientCustomerId header 
>>>>
>>>> <https://developers.google.com/adwords/api/docs/guides/call-structure#request_headers>
>>>>).
>>>>- Once your token is approved, you can use that developer token to 
>>>>issue API requests against *any* *production* or *test* account, 
>>>>regardless of its account hierarchy, provided your request includes the 
>>>>proper OAuth credentials.
>>>>
>>>> *Test* accounts serve two purposes:
>>>>
>>>>1. They allow you to use the API while your token is pending 
>>>>approval.
>>>>2. Once your token is approved, they allow you to test your code 
>>>>and experiment with the API without worrying about generating ad spend, 
>>>>since test accounts will not serve ads.
>>>>
>>>> A complicating factor at the moment is that the new AdWords experience 
>>>> in the UI does not clearly identify test accounts. We're aware of this 
>>>> issue and are working on a fix. As a *workaround* to that issue, I 
>>>> suggested checking if the *AdWords API Center* appears in your 
>>>> *manager *account, since the *AdWords API Center* only appears in an 
>>>> account if it is both: a) a *production *account; and b) a *manager* 
>>>> account. 
>>>> Therefore, if you log in as a *manager* account and do *not* see the 
>>>> *AdWords 
>>>> API Center*, then that account is a test account.
>>>>
>>>> If you're still not sure if your account is a test account, you can 
>>>> send your client customer ID only to me by clicking *Reply privately 
>>>> to author* on this message.
>>>>
>>>> Please let me know if the above doesn't clear things up.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, July 9, 2018 at 5:37:40 PM UTC-4, vodosof...@gmail.com 
>>>> wrote:
>>>>>
>>>>> Really, Adwords API is the most 

Re: AdService throws UNEXPECTED_INTERNAL_API_ERROR when filtering by AdType

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Dorian,

Thanks again for raising this issue. The fix for this is live, so you can 
now filter by *AdType* in your *AdService* get requests. Please give it 
another try and post back here if you encounter any issues.

Cheers,
Josh, AdWords API Team

On Monday, October 22, 2018 at 12:20:26 PM UTC-4, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi Dorian,
>
> Thanks for sending over the logs. I'm following up on the internal error 
> and will provide an update as soon as I hear back.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, October 22, 2018 at 7:19:30 AM UTC-4, Dorian Kind wrote:
>>
>> Hi Peter,
>>
>> thanks for your response. I've sent the SOAP logs in a private message.
>>
>> Best regards,
>> Dorian
>>
>> On Monday, 22 October 2018 12:42:48 UTC+2, Peter Oliquino (AdWords API 
>> Team) wrote:
>>>
>>> Hi Dorian,
>>>
>>> Could you send your SOAP logs as well? Our team will investigate this 
>>> and will get back to you as soon as we identify the root cause. You may 
>>> send them privately using the *reply privately to author* option.
>>>
>>> Thanks and regards,
>>> Peter
>>> AdWords API Team
>>>
>>> On Monday, October 22, 2018 at 5:54:39 PM UTC+8, Dorian Kind wrote:
>>>>
>>>> Hi,
>>>>
>>>> As the title says, AdService reproducibly errors out 
>>>> with InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when using a selector 
>>>> with a predicate that filters by AdType. For example, use the following 
>>>> AdService selector:
>>>>
>>>> {
>>>> 'predicates': [{
>>>> 'field': 'AdType',
>>>> 'operator': 'NOT_EQUALS',
>>>> 'values': ['IMAGE_AD']
>>>> }],
>>>> 'fields': [
>>>> 'Id'
>>>> ],
>>>> 'paging': {
>>>> 'numberResults': 10
>>>> }
>>>> }
>>>>
>>>> The result has been always UNEXPECTED_INTERNAL_API_ERROR for the ~10 
>>>> accounts that I tested. The operator in the predicate does not seem to 
>>>> matter, as soon as you filter on AdType, the error occurs. Happy to 
>>>> provide 
>>>> SOAP conversations.
>>>>
>>>> Best regards,
>>>> Dorian
>>>>
>>>>
>>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/39af297c-1577-475d-bf7e-89861b07d76e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API limits for TargetingIdeaService

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Karthick,

Yes, what you've described below is correct. The count in the snippet you 
provided is the count of results (TargetingIdeaPage.entries 
<https://developers.google.com/adwords/api/docs/reference/v201809/TargetingIdeaService.TargetingIdeaPage#entries>)
 
from a *single* TargetingIdeaService.get 
<https://developers.google.com/adwords/api/docs/reference/v201809/TargetingIdeaService#get>
 call. 
It's there as an example and to emphasize that regardless of the number of 
entries in a *single* *TargetingIdeaPage*, that one request still only 
counts as one operation.

Thanks,
Josh, AdWords API Team

On Friday, November 2, 2018 at 12:38:55 AM UTC-4, karthick r wrote:
>
> Hello Josh,  
>
> Keyword Stats seems straightforward. 
>
> Consider the following scenarios : 
> Keyword Stats Request config - 
>
> Num of seed keywords: 700
> Page size : 700
> Assuming that, I send in 700 Seed keywords in one stats request and if I 
> get back 700 keywords with the stats. That's counted as one operation.
>
> Keyword ideas Request config - 
> Seed keywords per keyword ideas request: 200
> Page size: 800
> Assuming that, I send in 200 Seed keywords in one ideas request and if I 
> get back 1600 keywords in total. I need to execute 2 get calls to read 
> through the results as I have defined the Page size as 800 (which is the 
> max limit). That's counted as two operations.  
>
> Is my understanding right ? 
>
> From the rate sheet 
> Operation: get
> Count: 100 targeting ideas
> Service: TargetingIdeaService 1
>
> What does the count mean here ?
>
> Thanks!
> Karthick
>
>
> On Friday, October 26, 2018 at 2:06:34 PM UTC-7, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Karthick,
>>
>> Each of the calls will count as *one* operation. From the rate limits 
>> guide (highlighting is mine):
>>
>> A get operation is counted as one operation, regardless of the number of 
>>> results objects.
>>
>>
>> When you mentioned "reading through the response", do you mean issuing a 
>> *get* request for each page of responses? If so, then each of those *get* 
>> requests 
>> will count as one operation as well.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, October 26, 2018 at 1:42:35 AM UTC-4, karthick r wrote:
>>>
>>> Hello,
>>>
>>> My job is to get the search volume (STATS) for 10,000 keywords and pass 
>>> in these 10,000 keywords to generate keyword ideas (IDEAS).  I have a 
>>> question on the API limits of the TargetingIdeaService. 
>>>
>>>
>>> https://developers.google.com/adwords/api/docs/appendix/limits#targeting-idea
>>>  
>>> Looking at this link, I understand that I can send 700 keywords to get 
>>> the stats and 200 keywords per request to get keyword ideas. If this is the 
>>> limit, then I need ~ 15 API calls to get the STATS and 50 API calls to get 
>>> the IDEAS. Does these 65 calls translate to 65 Operations ? 
>>>
>>> In this page https://developers.google.com/adwords/api/docs/ratesheet 
>>> it says 
>>>
>>> Operation: get
>>> Count: 100 targeting ideas
>>> Service: TargetingIdeaService 1
>>>
>>> How do I calculate the number of operations ?
>>>
>>> Also, are there restrictions on the number of keywords returned in the 
>>> keyword ideas response ? If API returns 2000 keyword ideas for a batch of 
>>> 200, I will have to read it in batches of 700. Does reading through the 
>>> response count towards the operations ?
>>>
>>> I already have the code to retry after the recommended time in case of 
>>> rate limit errors. 
>>>
>>> I am trying to find out the optimal payload size for my STATS and IDEAS 
>>> reports. 
>>>
>>>
>>>
>>> Thanks!
>>> Karthick
>>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/a593c3df-d448-4b71-a2e7-5203af95d361%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to use pending developer token against test account

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

A fix for this has been deployed, but it will only fix *newly created* client 
accounts under a test manager account. If you encountered this error, 
please create a new client account under your test manager account and use 
the new account for API requests. There's no need to create a new test 
*manager* account.

Thanks,
Josh, AdWords API Team

On Thursday, October 25, 2018 at 10:23:15 AM UTC-4, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi,
>
> We are working on a fix for this issue. I'll post an update here as soon 
> as I have more information.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, October 25, 2018 at 7:06:47 AM UTC-4, a...@gmail.com wrote:
>>
>> This did not work for me.
>>
>>  I can create test accounts through the API on the Test Manager account, 
>> but accessing them via the API still results in 
>> the DEVELOPER_TOKEN_NOT_APPROVED error.
>>
>> On Thursday, October 25, 2018 at 2:39:41 AM UTC+3, 
>> bi...@companionlabs.com wrote:
>>>
>>> We were able to work around this issue by using the Google AdWords API 
>>> to create a test managed customer account using ManagedCustomerService to 
>>> ADD the new ManagedCustomer.
>>>
>>> *Sample Code*
>>>
>>> https://developers.google.com/adwords/api/docs/samples/java/account-management
>>>
>>> *ManagedCustomerOperation*
>>>
>>> https://developers.google.com/adwords/api/docs/reference/v201802/ManagedCustomerService.ManagedCustomerOperation
>>>
>>> *ManagedCustomer*
>>>
>>> https://developers.google.com/adwords/api/docs/reference/v201802/ManagedCustomerService.ManagedCustomer
>>>
>>> Best regards,
>>> Bill
>>>
>>> On Thursday, October 18, 2018 at 6:24:10 AM UTC-4, Peter Oliquino 
>>> (AdWords API Team) wrote:
>>>>
>>>> Hi Joab,
>>>>
>>>> There is currently an ongoing issue affecting newly created test 
>>>> accounts which result in an error similar to yours. Allow me to update you 
>>>> once a fix has been made available.
>>>>
>>>> Best regards,
>>>> Peter
>>>> AdWords API Team
>>>>
>>>> On Thursday, October 18, 2018 at 5:09:13 PM UTC+8, Adwords Trapica 
>>>> wrote:
>>>>>
>>>>> Hello Forum,
>>>>>
>>>>> I created new developer token till I'll get approval answer I tried to 
>>>>> use it with my test account.
>>>>> I created test accounts and campaigns in my test accounts manager and 
>>>>> tried to run API call,
>>>>> yet I'm getting Error: soap:Client: 
>>>>> [QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED @ ; trigger:''].
>>>>>
>>>>> Any idea?
>>>>>
>>>>> Joab
>>>>>
>>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/21b90d86-3d46-400e-a19e-2c28a3a4aecb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't create partition tree or I just don't understand it

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

You can get the list of valid product bidding categories for each country 
using ConstantDataService.getProductBiddingCategoryData 
,
 
where your request includes a predicate for the *Country* of interest.

However, based on this Google Ads Help Center article 
,
 
bidding categories are not supported for Czechia, so you'll want to use one 
of the other product dimensions for this particular Shopping campaign.

Thanks,
Josh, AdWords API Team

On Friday, October 26, 2018 at 2:18:55 AM UTC-4, WDirk wrote:
>
> Ok, I've sent you a SOAP request ^^
>
> Dne čtvrtek 25. října 2018 20:41:18 UTC+2 Sreelakshmi Sasidharan (AdWords 
> API Team) napsal(a):
>>
>> Hello, 
>>
>> The INVALID_PRODUCT_BIDDING_CATEGORY 
>> 
>>  indicates 
>> that "Bidding categories do not form a valid path in the Shopping bidding 
>> category taxonomy". Since you were able to verify that, could you please 
>> enable 
>> logging 
>> 
>>  and 
>> share you SOAP request? You could reply privately to the author while 
>> sharing the details. 
>>
>> Thanks,
>> Sreelakshmi, AdWords API Team
>>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/c47752ca-4e14-4a75-9290-20d74d95db9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API limits for TargetingIdeaService

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Karthick,

Each of the calls will count as *one* operation. From the rate limits guide 
(highlighting is mine):

A get operation is counted as one operation, regardless of the number of 
> results objects.


When you mentioned "reading through the response", do you mean issuing a 
*get* request for each page of responses? If so, then each of those *get* 
requests 
will count as one operation as well.

Thanks,
Josh, AdWords API Team

On Friday, October 26, 2018 at 1:42:35 AM UTC-4, karthick r wrote:
>
> Hello,
>
> My job is to get the search volume (STATS) for 10,000 keywords and pass in 
> these 10,000 keywords to generate keyword ideas (IDEAS).  I have a question 
> on the API limits of the TargetingIdeaService. 
>
>
> https://developers.google.com/adwords/api/docs/appendix/limits#targeting-idea
>  
> Looking at this link, I understand that I can send 700 keywords to get the 
> stats and 200 keywords per request to get keyword ideas. If this is the 
> limit, then I need ~ 15 API calls to get the STATS and 50 API calls to get 
> the IDEAS. Does these 65 calls translate to 65 Operations ? 
>
> In this page https://developers.google.com/adwords/api/docs/ratesheet it 
> says 
>
> Operation: get
> Count: 100 targeting ideas
> Service: TargetingIdeaService 1
>
> How do I calculate the number of operations ?
>
> Also, are there restrictions on the number of keywords returned in the 
> keyword ideas response ? If API returns 2000 keyword ideas for a batch of 
> 200, I will have to read it in batches of 700. Does reading through the 
> response count towards the operations ?
>
> I already have the code to retry after the recommended time in case of 
> rate limit errors. 
>
> I am trying to find out the optimal payload size for my STATS and IDEAS 
> reports. 
>
>
>
> Thanks!
> Karthick
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/e096f3f5-5d63-4512-8dc2-6b09ac7646f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: SOAP error with Marketing API

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

I see that the type of that ad is MultiAssetResponsiveDisplayAd 
,
 
which was introduced in the AdWords API in v201806 
.
 
Since you're using v201802, the API won't return this ad from services. 
However, you should still be able to retrieve it via v201802 reports such 
as the AD_PERFORMANCE_REPORT 
.
 
If you migrate to v201806, or better yet, v201809, you'll be able to 
retrieve this ad from *AdGroupAdService*.

Thanks,
Josh, AdWords API Team

On Wednesday, October 24, 2018 at 11:44:30 AM UTC-4, d...@gmail.com wrote:
>
> Hi! We're using google marketing api on our customer's behalf, and been 
> having issues loading info for one of the banners he manages. Here's a 
> screenshot, out client provided, that shows a banner by id 299082079370  
>
>   
> present 
> in the system.
>
> Could you please help us with this issue, thanks!
>
> Here's a full SOAP request info: 
>
> *[2018-10-23 14:57:20] AdWords.INFO: 
> clientCustomerId=4482376070 operations=1 service=AdGroupAdService 
> method=get responseTime=235 requestId=000578e6962789900a37a093ee072469 
> server=adwords.google.com  isFault=0 
> faultMessage= [] []*
> *[2018-10-23 14:57:20] AdWords.DEBUG: POST 
> /api/adwords/cm/v201802/AdGroupAdService?wsdl HTTP/1.1 Host: 
> adwords.google.com  Connection: close 
> User-Agent: PHP-SOAP/5.4.45-1~dotdeb+7.1 Content-Type: text/xml; 
> charset=utf-8 SOAPAction: "" Content-Length: 2187 Authorization: REDACTED 
>   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ 
> " 
> xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201802 
> ">4482376070REDACTEDunknown
>  
> (AwApi-PHP, googleads-php-lib/33.1.0, 
> PHP/5.4.45-1~dotdeb+7.1)falsefalseAdGroupIdStatusUrlDisplayUrlCreativeFinalUrlsCreativeFinalMobileUrlsCreativeTrackingUrlTemplateCreativeUrlCustomParametersAdTypeDevicePreferenceUrlDataPolicySummaryDescriptionDescription1Description2MarketingImageLogoImageShortHeadlineLongHeadlineBusinessNameTemplateIdTemplateAdUnionIdTemplateAdNameTemplateAdDurationTemplateOriginAdIdHeadlinePart1HeadlinePart2Path1Path2IdIN299082079370StatusINENABLEDDISABLEDPAUSED0500
>  
> HTTP/1.1 200 OK Content-Type: text/xml; charset=UTF-8 Date: Tue, 23 Oct 
> 2018 14:57:20 GMT Expires: Tue, 23 Oct 2018 14:57:20 GMT Cache-Control: 
> private, max-age=0 X-Content-Type-Options: nosniff X-Frame-Options: 
> SAMEORIGIN X-XSS-Protection: 1; mode=block Server: GSE Alt-Svc: 
> quic=":443"; ma=2592000; v="44,43,39,35" Accept-Ranges: none Vary: 
> Accept-Encoding Connection: close  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/ 
> "> xmlns="https://adwords.google.com/api/adwords/cm/v201802 
> ">000578e6962789900a37a093ee072469AdGroupAdServiceget1235  
> xmlns="https://adwords.google.com/api/adwords/cm/v201802 
> ">0AdGroupAdPage*
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/54b78fd7-63da-442e-bffb-f31808c3cfec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to use pending developer token against test account

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

We are working on a fix for this issue. I'll post an update here as soon as 
I have more information.

Thanks,
Josh, AdWords API Team

On Thursday, October 25, 2018 at 7:06:47 AM UTC-4, avlad@gmail.com 
wrote:
>
> This did not work for me.
>
>  I can create test accounts through the API on the Test Manager account, 
> but accessing them via the API still results in 
> the DEVELOPER_TOKEN_NOT_APPROVED error.
>
> On Thursday, October 25, 2018 at 2:39:41 AM UTC+3, bi...@companionlabs.com 
> wrote:
>>
>> We were able to work around this issue by using the Google AdWords API to 
>> create a test managed customer account using ManagedCustomerService to ADD 
>> the new ManagedCustomer.
>>
>> *Sample Code*
>>
>> https://developers.google.com/adwords/api/docs/samples/java/account-management
>>
>> *ManagedCustomerOperation*
>>
>> https://developers.google.com/adwords/api/docs/reference/v201802/ManagedCustomerService.ManagedCustomerOperation
>>
>> *ManagedCustomer*
>>
>> https://developers.google.com/adwords/api/docs/reference/v201802/ManagedCustomerService.ManagedCustomer
>>
>> Best regards,
>> Bill
>>
>> On Thursday, October 18, 2018 at 6:24:10 AM UTC-4, Peter Oliquino 
>> (AdWords API Team) wrote:
>>>
>>> Hi Joab,
>>>
>>> There is currently an ongoing issue affecting newly created test 
>>> accounts which result in an error similar to yours. Allow me to update you 
>>> once a fix has been made available.
>>>
>>> Best regards,
>>> Peter
>>> AdWords API Team
>>>
>>> On Thursday, October 18, 2018 at 5:09:13 PM UTC+8, Adwords Trapica wrote:

 Hello Forum,

 I created new developer token till I'll get approval answer I tried to 
 use it with my test account.
 I created test accounts and campaigns in my test accounts manager and 
 tried to run API call,
 yet I'm getting Error: soap:Client: 
 [QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED @ ; trigger:''].

 Any idea?

 Joab

>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/1c9cc602-bbf7-498a-91e2-4512d5dec76a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdService throws UNEXPECTED_INTERNAL_API_ERROR when filtering by AdType

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Dorian,

Thanks for sending over the logs. I'm following up on the internal error 
and will provide an update as soon as I hear back.

Cheers,
Josh, AdWords API Team

On Monday, October 22, 2018 at 7:19:30 AM UTC-4, Dorian Kind wrote:
>
> Hi Peter,
>
> thanks for your response. I've sent the SOAP logs in a private message.
>
> Best regards,
> Dorian
>
> On Monday, 22 October 2018 12:42:48 UTC+2, Peter Oliquino (AdWords API 
> Team) wrote:
>>
>> Hi Dorian,
>>
>> Could you send your SOAP logs as well? Our team will investigate this and 
>> will get back to you as soon as we identify the root cause. You may send 
>> them privately using the *reply privately to author* option.
>>
>> Thanks and regards,
>> Peter
>> AdWords API Team
>>
>> On Monday, October 22, 2018 at 5:54:39 PM UTC+8, Dorian Kind wrote:
>>>
>>> Hi,
>>>
>>> As the title says, AdService reproducibly errors out 
>>> with InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when using a selector 
>>> with a predicate that filters by AdType. For example, use the following 
>>> AdService selector:
>>>
>>> {
>>> 'predicates': [{
>>> 'field': 'AdType',
>>> 'operator': 'NOT_EQUALS',
>>> 'values': ['IMAGE_AD']
>>> }],
>>> 'fields': [
>>> 'Id'
>>> ],
>>> 'paging': {
>>> 'numberResults': 10
>>> }
>>> }
>>>
>>> The result has been always UNEXPECTED_INTERNAL_API_ERROR for the ~10 
>>> accounts that I tested. The operator in the predicate does not seem to 
>>> matter, as soon as you filter on AdType, the error occurs. Happy to provide 
>>> SOAP conversations.
>>>
>>> Best regards,
>>> Dorian
>>>
>>>
>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/3ec10da1-1ff1-4eef-9d6b-8581c25b2179%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Dynamics Remarketing ads for retail

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

IA_BUNDLE);
>
> $layout = new TemplateElementField();
> $layout->setName('layout');
> $layout->setFieldText('Custom');
> $layout->setType(TemplateElementFieldType::ENUM);
>
> $adData = new TemplateElement();
> $adData->setUniqueName('adData');
> $adData->setFields([$media, $layout]);
>
> $html5Ad->setTemplateElements([$adData]);
>
> // Create ad group ad.
> $adGroupAd = new AdGroupAd();
> $adGroupAd->setAdGroupId($adGroupId);
> $adGroupAd->setAd($html5Ad);
> // Optional: Set additional settings.
> //$adGroupAd->getAd()->setAdType("DYNAMIC_SEARCH_AD");
> $adGroupAd->getAd()->setAdType("THIRD_PARTY_REDIRECT_AD");
> $adGroupAd->setStatus(AdGroupAdStatus::ENABLED);
>
> // Create ad group ad operation and add it to the list.
> $operation = new AdGroupAdOperation();
> $operation->setOperand($adGroupAd);
> $operation->setOperator(Operator::ADD);
> $operations[] = $operation;
>
> // Create the ad group ad on the server and print out some 
> information
> // about it.
> $result = $adGroupAdService->mutate($operations);
> foreach ($result->getValue() as $adGroupAd) {
> printf(
> "New HTML5 ad with ID %d and display URL '%s' was 
> created.\n",
> $adGroupAd->getAd()->getId(),
> $adGroupAd->getAd()->getDisplayUrl()
> );
> }
> }
> catch(\Exception $e){
> $msg=$e->getErrors()[0]->getReason();
> print_r($msg);
> }
> }
> public static function main(){
> // Generate a refreshable OAuth2 credential for authentication.
>     $oAuth2Credential = (new OAuth2TokenBuilder())
> ->withClientId("ClientIdapp")
> ->withClientSecret("ClientSecret")
> ->withRefreshToken("refreshtoken")
> ->build();
> 
> $session = (new AdWordsSessionBuilder())
> ->fromFile('adsapi_php.ini')
> ->withOAuth2Credential($oAuth2Credential)
> ->withClientCustomerId("")
> ->build();
> self::runExample(new 
> AdWordsServices(),$session,intval(self::AD_GROUP_ID));
> }
> }
> AddHtml5Ad::main();
>
> On Tuesday, 19 June 2018 23:34:33 UTC+5:30, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Although the AdWords API does not support template ID 416, you can now 
>> create a ResponsiveDisplayAd 
>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.ResponsiveDisplayAd>
>>  for 
>> your dynamic remarketing campaigns. The process for doing so will be 
>> essentially the same as the *createAd* step of the Add a Shopping 
>> dynamic remarketing campaign example 
>> <https://developers.google.com/adwords/api/docs/samples/java/advanced-operations#add-a-shopping-dynamic-remarketing-campaign>
>> .
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, June 18, 2018 at 4:19:40 PM UTC-4, Amit P Jivani wrote:
>>>
>>> Is this feature available now? 
>>>
>>>
>>> On Saturday, 19 December 2015 01:52:56 UTC+5:30, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> The AdWords API lets you manage the feed items for dynamic remarketing 
>>>> ads, but it does not support creating the dynamic display ads (with 
>>>> Template Ad ID 416) themselves. Therefore, you'll need to create the ads 
>>>> through the user interface first. After that, you'll be able to use the 
>>>> API 
>>>> to add/remove/update the dynamic data used for those ads.
>>>>
>>>> For more info on managing your feed items for dynamic remarketing ads, 
>>>> check out our Dynamic Remarketing guide 
>>>> <https://developers.google.com/adwords/api/docs/guides/dynamic-remarketing>
>>>> .
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Thursday, December 17, 2015 at 5:21:48 PM UTC-5, Ezequiel Murillo 
>>>> wrote:
>>>>>
>>>>> Sorry, I think I didn't explain myself as I should have. I want to 
>>>>> cr

Re: BatchJobError.DISK_QUOTA_EXCEEDED with no apparent reason

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sam,

I've raised this with the batch job team. I'll let you know once they have 
addressed the quota problem on the most recent account mentioned below.

Thanks,
Josh, AdWords API Team

On Wednesday, September 12, 2018 at 10:45:57 AM UTC-4, Samuel Barbosa wrote:
>
> Hi Josh,
>
> I am having the exact same problem that I had previously but now for my 
> account 4723477910. I have double checked and there are no BatchJobs 
> running, they are all "CANCELED" or "DONE", but I am still getting 
> "BatchJobError.DISK_QUOTA_EXCEEDED".
>
> Can you check this for me please?
>
> Regards,
>
> Sam
>
> On Tue, Jul 10, 2018 at 11:44 AM Samuel Barbosa  wrote:
>
>> Thanks Josh, things seem to be working alright now.
>>
>> Regards,
>>
>> Sam
>>
>> On Monday, July 9, 2018 at 4:23:10 PM UTC-3, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Sam,
>>>
>>> The quota for your account has been reset. Please try creating batch 
>>> jobs again and let me know if you encounter any issues.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, July 6, 2018 at 9:51:52 AM UTC-4, Josh Radcliff (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi Sam,
>>>>
>>>> I've raised this issue with the batch job engineering team and will 
>>>> reply back as soon as I have an update. This appears to be a problem on 
>>>> our 
>>>> side, since your account does not have any pending batch jobs and should 
>>>> therefore be well below the quota.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Thursday, July 5, 2018 at 4:19:05 PM UTC-4, Alan Justino da Silva 
>>>> wrote:
>>>>>
>>>>> @dannison, is there any possibility of the quota being not "refuelled" 
>>>>> by some detail we all missed? Everything is done or canceled already.
>>>>>
>>>>> Maybe something on a lower level, like cgroups, filesystem inodes, 
>>>>> temporary files?
>>>>>
>>>>> Em quinta-feira, 5 de julho de 2018 02:42:35 UTC-3, Dannison Yao 
>>>>> (AdWords API Team) escreveu:
>>>>>>
>>>>>> Hi Sam,
>>>>>>
>>>>>> The error BatchJobError.DISK_QUOTA_EXCEEDED 
>>>>>> <https://developers.google.com/adwords/api/docs/appendix/limits#batch-job>
>>>>>>  is 
>>>>>> encountered when you have reached the size limit for batch job 
>>>>>> operations 
>>>>>> which is a total of 1GB. What you could do is check for the 
>>>>>> diskUsageQuotaBalance 
>>>>>> <https://developers.google.com/adwords/api/docs/reference/v201806/BatchJobService.BatchJob#diskusagequotabalance>
>>>>>>  which 
>>>>>> will return the disk quota balance of the batch job's customer in KB. 
>>>>>> You 
>>>>>> can check and cancel the batch jobs in the AWAITING_FILE or ACTIVE 
>>>>>> status 
>>>>>> and retry the request or you could wait until the size of pending 
>>>>>> operations falls below the limit before creating new jobs.
>>>>>>
>>>>>> Regards,
>>>>>> Dannison
>>>>>> AdWords API Team
>>>>>>
>>>>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> Also find us on our blog:
>> https://googleadsdeveloper.blogspot.com/
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>  
>> You received this message because you are subscribed to the Google
>> Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/adwords-api/dTrdr3I4SoE/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.
>&g

Re: Policy violations - v201710 vs 201706

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

tising policies page you mentioned 
>>> (like "work @home", "big big SALE", "FR33 ShiPPiNG", "buy hunting rifle", 
>>> various brand names that produce trademark violations in production, etc.), 
>>> and these are accepted by the sandbox without issue, although production 
>>> v201802 produces policy violations. As I mentioned, the only thing I can 
>>> get to produce a policy violation (the new PolicyFindingError) in the 
>>> sandbox for v201806 expanded text ads is multiple exclamation points in a 
>>> row. Is this expected (it seems like it wouldn't be, considering you 
>>> pointed to the advertising policies page for examples of ad text that 
>>> should trigger errors)? I guess, in reality, if the answer to #1 above is 
>>> yes, then since I can produce that error with multiple exclamation points, 
>>> this question is irrelevant, although it seems odd. 
>>>
>>> Thanks,
>>> Greg
>>>
>>> On Thursday, July 26, 2018 at 4:35:39 PM UTC-5, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi Greg,
>>>>
>>>> I ran some tests and spoke with my colleagues today. Starting with 
>>>> v201806, some ad types will return a *PolicyFindingError* *instead of* a 
>>>> *PolicyViolationError* when there are policy issues. Here's the note 
>>>> we added to the Policy Exemption Requests guide 
>>>> <https://developers.google.com/adwords/api/docs/guides/exemption-requests> 
>>>> for 
>>>> the v201806 release (yellow highlights mine):
>>>>
>>>> *Note:* Starting in v201806, some ad types (including ExpandedTextAd 
>>>> <https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.ExpandedTextAd>)
>>>>  
>>>> will fail with a PolicyFindingError 
>>>> <https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.PolicyFindingError>
>>>>  instead. This new type of error indicates that the ad will certainly 
>>>> fail review again even if an exemption is requested. You can save these 
>>>> ads 
>>>> anyway by using the ignorablePolicyTopicIds 
>>>> <https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.AdGroupAdOperation#ignorablePolicyTopicIds>
>>>>  field. 
>>>> They will fail review, but could be approved later if you fix the 
>>>> underlying issue, for example by getting the correct certificate.
>>>>
>>>> Therefore, if you're looking to handle errors specifically for 
>>>> *ExpandedTextAds*, you'll want to:
>>>>
>>>>1. Modify your error handling to instead check for 
>>>>    *PolicyFindingError*.
>>>>2. If you want to resubmit an operation even though it's likely to 
>>>>wind up with policy errors, collect all of the policyTopicIds 
>>>>
>>>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.PolicyTopicEntry#policytopicid>
>>>>  from 
>>>>the error's policyTopicEntries 
>>>>
>>>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.PolicySummary#policytopicentries>,
>>>>  
>>>>add those IDs to the operation's ignorablePolicyTopicIds 
>>>>
>>>> <https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.AdGroupAdOperation#ignorablePolicyTopicIds>,
>>>>  
>>>>then resubmit the operation.
>>>>
>>>> You can see examples of ad text that will trigger these errors in this 
>>>> Advertising Policies Help page 
>>>> <https://support.google.com/adspolicy/answer/6021546#048>.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Thursday, July 26, 2018 at 11:13:27 AM UTC-4, Josh Radcliff (AdWords 
>>>> API Team) wrote:
>>>>>
>>>>> Hi Greg,
>>>>>
>>>>> Sorry for the delay. I've gathered some information but I need to work 
>>>>> through some of the finer points and run through examples myself in order 
>>>>> to give you a complete answer. Stay tuned!
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Tuesday, July 24, 2018 at 5:11:51 PM UTC-4, GregT wrote:
>>>>>>
>>>

Re: Get merchant center ids associated with the Adwords account

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

You can now get this information using the CustomerService.getServiceLinks 
<https://developers.google.com/adwords/api/docs/reference/v201806/CustomerService#getServiceLinks>
 method, 
which will return ServiceLink 
<https://developers.google.com/adwords/api/docs/reference/v201806/CustomerService.ServiceLink>
 objects. 
On objects where *serviceType = MERCHANT_CENTER*, the serviceLinkId 
<https://developers.google.com/adwords/api/docs/reference/v201806/CustomerService.ServiceLink#servicelinkid>
 will 
be the merchant center ID.

Thanks,
Josh, AdWords API Team

On Tuesday, August 21, 2018 at 5:09:09 PM UTC-4, Vivek Patel wrote:
>
> Is this feature available now?
>
> On Thursday, December 11, 2014 at 12:07:23 AM UTC+5:30, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi,
>>
>> I've passed this feature request along, but I do not have a date for when 
>> or if this will be added. In the meantime, using the Content API for 
>> Shopping 
>> <https://developers.google.com/shopping-content/multiclientaccounts/mcaccounts>
>>  
>> is the only option.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, December 10, 2014 7:47:12 AM UTC-5, Bas Hilbers wrote:
>>>
>>>
>>> Will this be possible in the future?
>>>
>>>
>>> On Thursday, April 17, 2014 5:27:33 PM UTC+2, Josh Radcliff (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'm not aware of a way to get this information at the *account* level 
>>>> from the AdWords API, but I searched and it looks like you can go the 
>>>> other 
>>>> direction (get AdWords accounts for a Merchant Center account) through the 
>>>> Content API for Shopping.
>>>>
>>>>
>>>> https://developers.google.com/shopping-content/multiclientaccounts/mcaccounts
>>>>
>>>> If you have questions about that API please check out its forum 
>>>> <https://groups.google.com/forum/#!forum/google-content-api-for-shopping>
>>>> .
>>>>
>>>> If instead you want to discover the merchant center ID for a *campaign*, 
>>>> you can get this information from the AdWords API by including the 
>>>> "Settings" field in your CampaignService 
>>>> <https://developers.google.com/adwords/api/docs/reference/v201402/CampaignService#get>
>>>>  selector.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, April 14, 2014 10:26:45 AM UTC-4, Niki B wrote:
>>>>>
>>>>>
>>>>> How do I get a list of merchant ids that are associated with an 
>>>>> AdWords account?  This is need for creating shopping campaigns.  Thanks.
>>>>>
>>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/bbd2900c-9883-43ec-8279-09f127738061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Undocumented error INCOMPATIBLE_WITH_RESTRICTION_TYPE

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

The ad group in question was of type DISPLAY_ENGAGEMENT 
,
 
which is only supported in AdWords API reports, but not in management 
services. My suggestion to Tom was to try this operation with an ad group 
of type *DISPLAY_STANDARD* instead.

Tom, did that suggestion solve the problem for you?

Thanks,
Josh, AdWords API Team

On Monday, August 20, 2018 at 11:17:54 AM UTC-4, 
btourtell...@wordstream.com wrote:
>
> Hello Tom,
>
> Did you guys ever figure out what the cause of the undocumented AdError.
> INCOMPATIBLE_WITH_RESTRICTION_TYPE was?
>
> On Tuesday, December 19, 2017 at 4:12:47 PM UTC-5, Tom Cz wrote:
>>
>> I have created a new AdWords account via my MCC account. About this I 
>> have created a campaign and an ad group. All this can be read out well via 
>> the API.  
>> But if I want to create an ad, I get the following undocumented errors.
>>
>> [AdError.INCOMPATIBLE_WITH_RESTRICTION_TYPE @ operations[0].operand.ad]
>>
>>
>> In another AdWords account, which is also managed by our MCC, this is 
>> possible without any problems.
>>
>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/5919d929-7fe7-4c6d-9a6e-62633aa99a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to retrieve disapproval reasons for an ad through the api

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

The service and reports don't support querying by disapproval date or ad 
creation/modification date. If you want to track that information, you 
could store the status of ads for each day locally, then compare that 
against today's results.

Thanks,
Josh, AdWords API Team

On Tuesday, August 14, 2018 at 3:44:31 PM UTC-4, Matthew Macchia wrote:
>
> Is there a way to get the disapproved ads only for yesterday?
> When I query for them it gives me the full list of ads ever. Rather than a 
> subset of yesterdays ads.
>
>
> On Wednesday, November 20, 2013 at 4:09:34 AM UTC-7, Gaurav Agarwal wrote:
>>
>> Hi,
>>
>> We are trying to retrieve disapproval reasons for an ad rejected which is 
>> trademark disapproved and we are not getting anything through the api, 
>> while we can see the reasons on UI.
>>
>> We are seeing this behaviour for all the ads that are disapproved 
>> currently.
>>
>> An example soap request-response is as follows. Kindly let us know what 
>> we are missing and how to retrieve the disapproval reasons in such cases.
>>
>> Thanks and Regards,
>> Gaurav
>>
>>
>> SOAP LOG : > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/; 
>>  
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema; 
>>  
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
>> >>  soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next; 
>>  soapenv:mustUnderstand="0" 
>> xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201306; 
>> >1158401043>  xmlns="https://adwords.google.com/api/adwords/cm/v201306; 
>> >AdGroupIdStatusIdUrlDisplayUrlAdGroupCreativeApprovalStatusHeadlineDescription1Description2DevicePreferenceDisapprovalReasonsAdGroupIdEQUALS4486137122IdEQUALS27087061322
>>
>> http://schemas.xmlsoap.org/soap/envelope/; 
>> >> xmlns="https://adwords.google.com/api/adwords/cm/v201306; 
>> >0004eb954cfbde800a42f8a7133aAdGroupAdServiceget0172>  xmlns="https://adwords.google.com/api/adwords/cm/v201306; 
>> >1AdGroupAdPage4486137122>  xsi:type="TextAd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
>> >27087061322http://m.nextag.com/goto.jsp?p={ifsearch:355840}{ifcontent:352182}search={keyword}t=ag%3D4486137122crid=50608gg_param1={param1}gg_ace={aceid}gg_mt={matchtype}gg_aid={creative}gg_param2={param2}gg_target={target}gg_net={network}gg_adpos={adposition}gg_rand={random}gg_dev={device}gg_site={placement}gg_dm={devicemodel}www.NexTag.com/Epson-CX4800-Ink30001TextAdEpson
>>  CX4800 Ink BargainsFind Great Deals on Epson 
>> StylusCX4800 Ink Cartridges. Many 
>> Colors!ENABLEDDISAPPROVEDtrueSEARCHAdStats0.0
>>
>>
>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/1652157b-a79f-41ab-bb9d-9c50706007b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Thanks, everyone, for your patience while we tracked down the root cause of 
this issue. The problem was that when a specific transient error occurred 
during processing on our side, it was being incorrectly reported back in 
the response  with status code 400 (bad request). A fix was deployed so 
that the proper status code of 500 (internal server error) will now be 
returned in this situation.

Best regards,
Josh, AdWords API Team

On Thursday, July 26, 2018 at 9:09:47 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> We've identified the root cause and are working on a fix. I'll update this 
> discussion once the fix has been deployed.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Arthur,
>>
>> Does the same request succeed on retry? If so, then you are encountering 
>> the same issue being discussed here. I advise having retry logic in your 
>> reporting jobs, both in general and to mitigate this particular issue.
>>
>> Also, please note that v201710 will be sunset on July 25 
>> <https://ads-developers.googleblog.com/2018/06/adwords-api-v201710-sunset-reminder.html>.
>>  
>> Please make sure you migrate to a newer version 
>> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201806>
>>  
>> of the AdWords API before that date.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
>> arthur.baldu...@brainweb.com.br wrote:
>>>
>>> Hello everyone,
>>>
>>> I'm working on an application that retrieves data from the Adwords API 
>>> and I'm facing the same 400 - Bad Request problem. We are working with the 
>>> v201710 version. 
>>> Yesterday I worked normally on the application and today when I arrived 
>>> I faced the exact same problem reported here. I didn't change anything in 
>>> the code that was working just yesterday! 
>>> I spent a lot of time searching for a possible mistake and just want to 
>>> make sure that it might not be an error from my part.
>>>
>>> Thanks a lot for your attention!
>>>
>>> best regards,
>>>
>>> Arthur
>>>
>>> Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
>>> (AdWords API Team) escreveu:
>>>>
>>>> Hi Zweitze,
>>>>
>>>> Thanks for providing those details. The engineer investigating this 
>>>> said they'll be quite helpful. I'll reply back when he has an update.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>>>>
>>>>> This error was away at my site for quite a few weeks, but reappeared 
>>>>> this morning. The response headers that came with the error were:
>>>>>
>>>>> Content-Disposition 
>>>>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>>>>> X-Content-Type-Options nosniff
>>>>> X-Frame-Options SAMEORIGIN
>>>>> X-XSS-Protection 1; mode=block
>>>>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>>>>> Content-Length 0
>>>>> Cache-Control private, max-age=0
>>>>> Content-Type application/x-gzip; charset=UTF-8
>>>>> Date Tue, 17 Jul 2018 04:42:09 GMT
>>>>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>>>>> Server GSE
>>>>>
>>>>> The error occured with some old code running v201710.
>>>>> CustomerId and ReportDefinition are available if necessary, but I can 
>>>>> assure you that that same ReportDefinition (a 
>>>>> PLACEMENT_PERFORMANCE_REPORT 
>>>>> this time) was successfully used thousands of times.
>>>>>
>>>>>
>>>>>
>>>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/dc384749-6710-4c18-b2f1-97eb500e89f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ads (beta) api operation limits

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Don,

I have good news: the operations limit for the Google Ads API has been 
increased to 5,000 so that it matches the operations limit for the AdWords 
API <https://developers.google.com/adwords/api/docs/appendix/limits#general>. 
Thanks for bringing this to our attention!

Cheers,
Josh, AdWords API Team

On Friday, August 10, 2018 at 12:24:44 PM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Don,
>
> The Google Ads API does not have a partial failure feature just yet, so 
> all operations in a mutate request will fail if *any* operation in the 
> request encounters an error.
>
> Thanks for providing the error message for the operation count limit. I'm 
> looking into that one and will get back to you.
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, August 10, 2018 at 12:20:23 PM UTC-4, Don Mitchell wrote:
>>
>> [12:19:16] ERROR 
>> {"google.ads.googleads.v0.errors.googleadsfailure-bin"=>"\n>\n\x02\b\r\x128Received
>>  
>> 2000 operations, exceeding the maximum of 1000.", 
>> "grpc-status-details-bin"=>"\b\x03\x12%Request contains an invalid 
>> argument.\x1A\x87\x01\
>> nCtype.googleapis.com/google.ads.googleads.v0.errors.GoogleAdsFailure\x12@\n 
>> <http://nCtype.googleapis.com/google.ads.googleads.v0.errors.GoogleAdsFailure%5Cx12@%5Cn>>\n\x02\b\r\x128Received
>>  
>> 2000 operations, exceeding the maximum of 1000.", "request-id"=>
>> "aIELZe9qUXmF1KoeDy2tTA"}
>>
>>
>>
>>
>> On Wednesday, 8 August 2018 16:15:59 UTC-4, Don Mitchell wrote:
>>>
>>> Even though the beta Ads api uses a streaming protocol, it still has 
>>> operation limits. For CampaignBudget.mutate_campaign_budgets (DELETE 
>>> operation), it told me the limit is 1000. In general are the limits 5000 
>>> per request as per the adwords limits (
>>> https://developers.google.com/adwords/api/docs/appendix/limits)? For 
>>> download, there doesn't seem to be a limit (not the 10K limit from 
>>> Adwords). Can I get a definitive statement on the limits with the 
>>> exceptions?
>>>
>>> Also, how does the api return operation validation failures when only a 
>>> subset of operations on a request fail? There's no partial failure property 
>>> in the result. Does it fail the whole request if just one operation is 
>>> invalid? Does it silently fail?
>>>
>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/d89ed7cc-a2c5-40de-b951-81228a7bb63c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ads (beta) api operation limits

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Don,

The Google Ads API does not have a partial failure feature just yet, so all 
operations in a mutate request will fail if *any* operation in the request 
encounters an error.

Thanks for providing the error message for the operation count limit. I'm 
looking into that one and will get back to you.

Cheers,
Josh, AdWords API Team

On Friday, August 10, 2018 at 12:20:23 PM UTC-4, Don Mitchell wrote:
>
> [12:19:16] ERROR 
> {"google.ads.googleads.v0.errors.googleadsfailure-bin"=>"\n>\n\x02\b\r\x128Received
>  
> 2000 operations, exceeding the maximum of 1000.", 
> "grpc-status-details-bin"=>"\b\x03\x12%Request contains an invalid 
> argument.\x1A\x87\x01\
> nCtype.googleapis.com/google.ads.googleads.v0.errors.GoogleAdsFailure\x12@\n 
> >\n\x02\b\r\x128Received
>  
> 2000 operations, exceeding the maximum of 1000.", "request-id"=>
> "aIELZe9qUXmF1KoeDy2tTA"}
>
>
>
>
> On Wednesday, 8 August 2018 16:15:59 UTC-4, Don Mitchell wrote:
>>
>> Even though the beta Ads api uses a streaming protocol, it still has 
>> operation limits. For CampaignBudget.mutate_campaign_budgets (DELETE 
>> operation), it told me the limit is 1000. In general are the limits 5000 
>> per request as per the adwords limits (
>> https://developers.google.com/adwords/api/docs/appendix/limits)? For 
>> download, there doesn't seem to be a limit (not the 10K limit from 
>> Adwords). Can I get a definitive statement on the limits with the 
>> exceptions?
>>
>> Also, how does the api return operation validation failures when only a 
>> subset of operations on a request fail? There's no partial failure property 
>> in the result. Does it fail the whole request if just one operation is 
>> invalid? Does it silently fail?
>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/41251f0b-81f8-4aa4-8f5a-eb0250b33da9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: why i am not able to create the MCC test account.?

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

If you are reading this or are one of the people who raised this issue, I 
could use your help. The engineers working on this problem are looking for 
a *recent* example (within the last 3-5 days) of someone who went through 
the test account signup process and wound up with a non-test account. If 
you have such an example, please send the account's customer ID *only to me* by 
clicking *Reply privately to author* on this post.

Thanks,
Josh, AdWords API Team

On Thursday, July 19, 2018 at 3:00:18 PM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> I have good news! The new AdWords experience now indicates if an account 
> is a test account via a red *Test account* banner in the top right corner:
>
>
> <https://lh3.googleusercontent.com/-XJSx9VMSbQ4/W1Dfj86MRfI/AE4/ny0_Ba-ud40bqCOKXdeGMK3xBaOkXYP2wCLcBGAs/s1600/test-account.png>
>
> Thanks,
>
> Josh, AdWords API Team
>
>
>
>
> On Monday, July 9, 2018 at 3:32:00 AM UTC-4, Satyaprakash Mishra wrote:
>>
>> Hi,
>>
>> On step 3, I am not able to see the *Return to previous AdWords*.
>>
>> find the below screenshot.
>>
>>
>>
>>
>> On Fri, Jul 6, 2018 at 6:23 PM, 'Josh Radcliff (AdWords API Team)' via 
>> AdWords API and Google Ads API Forum  
>> wrote:
>>
>>> Hi Satyaprakash,
>>>
>>> The new AdWords experience doesn't clearly indicate when an account is a 
>>> test account. To find that information, please complete the following steps 
>>> for the original account you mentioned:
>>>
>>> 1. Log into the account.
>>> 2. In the upper right corner, click the wrench icon.
>>> 3. In the upper right corner of the window that appears, click *Return 
>>> to previous AdWords*.
>>> 4. Check if you see a red banner that says *This is a test account!*
>>>
>>> If you do not see the red banner in step 4, then the account is not a 
>>> test account. If you'd like, you can send the customer ID of the account to 
>>> me by clicking *Reply privately to author* on this message.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, July 6, 2018 at 3:46:15 AM UTC-4, Peter Oliquino (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi Satyaprakash,
>>>>
>>>> We've reached out to the rest of our team to discuss this issue. We'll 
>>>> update you immediately once we have information regarding this.
>>>>
>>>> Best regards,
>>>> Peter
>>>> AdWords API Team
>>>>
>>> -- 
>>> -- 
>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>> Also find us on our blog:
>>> https://googleadsdeveloper.blogspot.com/
>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>>  
>>> You received this message because you are subscribed to the Google
>>> Groups "AdWords API and Google Ads 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 and Google Ads 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/efd8fe9e-fd35-4736-8ffb-cd992a9c1c3b%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/adwords-api/efd8fe9e-fd35-4736-8ffb-cd992a9c1c3b%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/3d76e6e6-6aa6-4cc6-9cf0-4561e8eb5fb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Policy violations - v201710 vs 201706

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg,

I ran some tests and spoke with my colleagues today. Starting with v201806, 
some ad types will return a *PolicyFindingError* *instead of* a 
*PolicyViolationError* when there are policy issues. Here's the note we 
added to the Policy Exemption Requests guide 
<https://developers.google.com/adwords/api/docs/guides/exemption-requests> for 
the v201806 release (yellow highlights mine):

*Note:* Starting in v201806, some ad types (including ExpandedTextAd 
<https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.ExpandedTextAd>)
 
will fail with a PolicyFindingError 
<https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.PolicyFindingError>
 instead. This new type of error indicates that the ad will certainly fail 
review again even if an exemption is requested. You can save these ads 
anyway by using the ignorablePolicyTopicIds 
<https://developers.google.com/adwords/api/docs/reference/latest/AdGroupAdService.AdGroupAdOperation#ignorablePolicyTopicIds>
 field. 
They will fail review, but could be approved later if you fix the 
underlying issue, for example by getting the correct certificate.

Therefore, if you're looking to handle errors specifically for 
*ExpandedTextAds*, you'll want to:

   1. Modify your error handling to instead check for *PolicyFindingError*.
   2. If you want to resubmit an operation even though it's likely to wind 
   up with policy errors, collect all of the policyTopicIds 
   
<https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.PolicyTopicEntry#policytopicid>
 from 
   the error's policyTopicEntries 
   
<https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.PolicySummary#policytopicentries>,
 
   add those IDs to the operation's ignorablePolicyTopicIds 
   
<https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.AdGroupAdOperation#ignorablePolicyTopicIds>,
 
   then resubmit the operation.

You can see examples of ad text that will trigger these errors in this 
Advertising Policies Help page 
<https://support.google.com/adspolicy/answer/6021546#048>.

Cheers,
Josh, AdWords API Team

On Thursday, July 26, 2018 at 11:13:27 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Greg,
>
> Sorry for the delay. I've gathered some information but I need to work 
> through some of the finer points and run through examples myself in order 
> to give you a complete answer. Stay tuned!
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, July 24, 2018 at 5:11:51 PM UTC-4, GregT wrote:
>>
>> Hi, Josh.
>>
>> It's been a couple weeks. Just checking in to see if there's any update?
>>
>> Thanks,
>> Greg
>>
>> On Friday, July 6, 2018 at 10:07:56 AM UTC-5, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Greg, Peter,
>>>
>>> Thanks for providing such detailed information on this issue. I've 
>>> passed this on to the policy expert on the engineering team and will let 
>>> you know as soon as I have an update.
>>>
>>> Cheers,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, July 3, 2018 at 11:20:56 AM UTC-4, GregT wrote:
>>>>
>>>> I just wanted to mention that we're experiencing something similar 
>>>> moving to v201806 and trying to test that things are working. We have 
>>>> tests 
>>>> where some should be exemptable ad text and some not exemptable, to make 
>>>> sure we handle things correctly. At this point, the only thing we can get 
>>>> to trigger any kind of policy violation in a test account with v201806 is 
>>>> multiple exclamation points, which trigger the new PolicyFindingError 
>>>> (which is good that we can trigger that). 
>>>>
>>>> But, using all kinds of other ad text that produce 
>>>> PolicyViolationErrors in production in v201802 and/or are explicitly 
>>>> mentioned as violating the ad editorial policy (like "work @home", "big 
>>>> big 
>>>> SALE", "FR33 ShiPPiNG", "buy hunting rifle", various brand names that 
>>>> produce trademark violations in production, etc.) don't produce any kind 
>>>> of 
>>>> PolicyViolationError against our test accounts in v201806, breaking our 
>>>> tests and making it very hard to make sure the code works.
>>>>
>>>> For us, and possibly Peter, if you could just give us some example ad 
>>>> texts that would produce both exemptable and non-exemptable 
>>>> PolicyViolationErrors in test accounts with v201806, that'd be good enough 
>>&

Re: Policy violations - v201710 vs 201706

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg,

Sorry for the delay. I've gathered some information but I need to work 
through some of the finer points and run through examples myself in order 
to give you a complete answer. Stay tuned!

Thanks,
Josh, AdWords API Team

On Tuesday, July 24, 2018 at 5:11:51 PM UTC-4, GregT wrote:
>
> Hi, Josh.
>
> It's been a couple weeks. Just checking in to see if there's any update?
>
> Thanks,
> Greg
>
> On Friday, July 6, 2018 at 10:07:56 AM UTC-5, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Greg, Peter,
>>
>> Thanks for providing such detailed information on this issue. I've passed 
>> this on to the policy expert on the engineering team and will let you know 
>> as soon as I have an update.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Tuesday, July 3, 2018 at 11:20:56 AM UTC-4, GregT wrote:
>>>
>>> I just wanted to mention that we're experiencing something similar 
>>> moving to v201806 and trying to test that things are working. We have tests 
>>> where some should be exemptable ad text and some not exemptable, to make 
>>> sure we handle things correctly. At this point, the only thing we can get 
>>> to trigger any kind of policy violation in a test account with v201806 is 
>>> multiple exclamation points, which trigger the new PolicyFindingError 
>>> (which is good that we can trigger that). 
>>>
>>> But, using all kinds of other ad text that produce PolicyViolationErrors 
>>> in production in v201802 and/or are explicitly mentioned as violating the 
>>> ad editorial policy (like "work @home", "big big SALE", "FR33 ShiPPiNG", 
>>> "buy hunting rifle", various brand names that produce trademark violations 
>>> in production, etc.) don't produce any kind of PolicyViolationError against 
>>> our test accounts in v201806, breaking our tests and making it very hard to 
>>> make sure the code works.
>>>
>>> For us, and possibly Peter, if you could just give us some example ad 
>>> texts that would produce both exemptable and non-exemptable 
>>> PolicyViolationErrors in test accounts with v201806, that'd be good enough 
>>> (rather than, for example, trying to make the test accounts in v201806 do 
>>> identical policy violation checks as production).
>>>
>>> Thanks in advance,
>>> Greg
>>>
>>>
>>> On Tuesday, July 3, 2018 at 5:51:44 AM UTC-5, Peter Lanser wrote:
>>>>
>>>> Hi, we are currently migrating from Adwords API v201710 to v201806 and 
>>>> we are observing an issue regarding policy violations / excemption 
>>>> requests.
>>>>
>>>> Part of our test suite is the creation of an (expanded) text ad 
>>>> triggering a PolicyViolationError. Everything is fine with v201710 - we 
>>>> are 
>>>> expecting this error (and creating an excemption request later).
>>>>
>>>> [INFO] 
>>>> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
>>>> SOAP response:
>>>> 
>>>> http://schemas.xmlsoap.org/soap/envelope/;>
>>>> ...
>>>> 
>>>> 
>>>> ...
>>>> 
>>>> https://adwords.google.com/api/adwords/cm/v201710;>
>>>> ...
>>>> http://www.w3.org/2001/XMLSchema-instance; 
>>>> xsi:type="PolicyViolationError">
>>>> ...
>>>> 
>>>> PolicyViolationError.POLICY_ERROR
>>>> 
>>>> PolicyViolationError
>>>> 
>>>> weapons
>>>> Rifle
>>>> 
>>>> Google 
>>>> AdWords
>>>> 
>>>> This ad or keyword 
>>>> requires review before it can run.
>>>> true
>>>> ...
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>
>>>> However, the error is not triggered when using v201806. The expected 
>>>> error is not triggered:
>>>>
>>>> [DEBUG] 
>>>> com.google.api.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

We've identified the root cause and are working on a fix. I'll update this 
discussion once the fix has been deployed.

Thanks,
Josh, AdWords API Team

On Friday, July 20, 2018 at 9:43:45 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Arthur,
>
> Does the same request succeed on retry? If so, then you are encountering 
> the same issue being discussed here. I advise having retry logic in your 
> reporting jobs, both in general and to mitigate this particular issue.
>
> Also, please note that v201710 will be sunset on July 25 
> <https://ads-developers.googleblog.com/2018/06/adwords-api-v201710-sunset-reminder.html>.
>  
> Please make sure you migrate to a newer version 
> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201806>
>  
> of the AdWords API before that date.
>
> Thanks,
> Josh, AdWords API Team
>
> On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
> arthur.baldu...@brainweb.com.br wrote:
>>
>> Hello everyone,
>>
>> I'm working on an application that retrieves data from the Adwords API 
>> and I'm facing the same 400 - Bad Request problem. We are working with the 
>> v201710 version. 
>> Yesterday I worked normally on the application and today when I arrived I 
>> faced the exact same problem reported here. I didn't change anything in the 
>> code that was working just yesterday! 
>> I spent a lot of time searching for a possible mistake and just want to 
>> make sure that it might not be an error from my part.
>>
>> Thanks a lot for your attention!
>>
>> best regards,
>>
>> Arthur
>>
>> Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
>> (AdWords API Team) escreveu:
>>>
>>> Hi Zweitze,
>>>
>>> Thanks for providing those details. The engineer investigating this said 
>>> they'll be quite helpful. I'll reply back when he has an update.
>>>
>>> Cheers,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>>>
>>>> This error was away at my site for quite a few weeks, but reappeared 
>>>> this morning. The response headers that came with the error were:
>>>>
>>>> Content-Disposition 
>>>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>>>> X-Content-Type-Options nosniff
>>>> X-Frame-Options SAMEORIGIN
>>>> X-XSS-Protection 1; mode=block
>>>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>>>> Content-Length 0
>>>> Cache-Control private, max-age=0
>>>> Content-Type application/x-gzip; charset=UTF-8
>>>> Date Tue, 17 Jul 2018 04:42:09 GMT
>>>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>>>> Server GSE
>>>>
>>>> The error occured with some old code running v201710.
>>>> CustomerId and ReportDefinition are available if necessary, but I can 
>>>> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
>>>> this time) was successfully used thousands of times.
>>>>
>>>>
>>>>
>>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/b6a48e3f-4153-4f63-989c-c36bb87803a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Arthur,

Does the same request succeed on retry? If so, then you are encountering 
the same issue being discussed here. I advise having retry logic in your 
reporting jobs, both in general and to mitigate this particular issue.

Also, please note that v201710 will be sunset on July 25 
<https://ads-developers.googleblog.com/2018/06/adwords-api-v201710-sunset-reminder.html>.
 
Please make sure you migrate to a newer version 
<https://developers.google.com/adwords/api/docs/reference/release-notes/v201806>
 
of the AdWords API before that date.

Thanks,
Josh, AdWords API Team

On Thursday, July 19, 2018 at 4:50:57 PM UTC-4, 
arthur.baldu...@brainweb.com.br wrote:
>
> Hello everyone,
>
> I'm working on an application that retrieves data from the Adwords API and 
> I'm facing the same 400 - Bad Request problem. We are working with the 
> v201710 version. 
> Yesterday I worked normally on the application and today when I arrived I 
> faced the exact same problem reported here. I didn't change anything in the 
> code that was working just yesterday! 
> I spent a lot of time searching for a possible mistake and just want to 
> make sure that it might not be an error from my part.
>
> Thanks a lot for your attention!
>
> best regards,
>
> Arthur
>
> Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff 
> (AdWords API Team) escreveu:
>>
>> Hi Zweitze,
>>
>> Thanks for providing those details. The engineer investigating this said 
>> they'll be quite helpful. I'll reply back when he has an update.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>>
>>> This error was away at my site for quite a few weeks, but reappeared 
>>> this morning. The response headers that came with the error were:
>>>
>>> Content-Disposition 
>>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>>> X-Content-Type-Options nosniff
>>> X-Frame-Options SAMEORIGIN
>>> X-XSS-Protection 1; mode=block
>>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>>> Content-Length 0
>>> Cache-Control private, max-age=0
>>> Content-Type application/x-gzip; charset=UTF-8
>>> Date Tue, 17 Jul 2018 04:42:09 GMT
>>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>>> Server GSE
>>>
>>> The error occured with some old code running v201710.
>>> CustomerId and ReportDefinition are available if necessary, but I can 
>>> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
>>> this time) was successfully used thousands of times.
>>>
>>>
>>>
>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/3e643199-e70b-4980-ad71-93c769d8a808%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: why i am not able to create the MCC test account.?

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

I have good news! The new AdWords experience now indicates if an account is 
a test account via a red *Test account* banner in the top right corner:

<https://lh3.googleusercontent.com/-XJSx9VMSbQ4/W1Dfj86MRfI/AE4/ny0_Ba-ud40bqCOKXdeGMK3xBaOkXYP2wCLcBGAs/s1600/test-account.png>

Thanks,

Josh, AdWords API Team




On Monday, July 9, 2018 at 3:32:00 AM UTC-4, Satyaprakash Mishra wrote:
>
> Hi,
>
> On step 3, I am not able to see the *Return to previous AdWords*.
>
> find the below screenshot.
>
>
>
>
> On Fri, Jul 6, 2018 at 6:23 PM, 'Josh Radcliff (AdWords API Team)' via 
> AdWords API and Google Ads API Forum  wrote:
>
>> Hi Satyaprakash,
>>
>> The new AdWords experience doesn't clearly indicate when an account is a 
>> test account. To find that information, please complete the following steps 
>> for the original account you mentioned:
>>
>> 1. Log into the account.
>> 2. In the upper right corner, click the wrench icon.
>> 3. In the upper right corner of the window that appears, click *Return 
>> to previous AdWords*.
>> 4. Check if you see a red banner that says *This is a test account!*
>>
>> If you do not see the red banner in step 4, then the account is not a 
>> test account. If you'd like, you can send the customer ID of the account to 
>> me by clicking *Reply privately to author* on this message.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, July 6, 2018 at 3:46:15 AM UTC-4, Peter Oliquino (AdWords API 
>> Team) wrote:
>>>
>>> Hi Satyaprakash,
>>>
>>> We've reached out to the rest of our team to discuss this issue. We'll 
>>> update you immediately once we have information regarding this.
>>>
>>> Best regards,
>>> Peter
>>> AdWords API Team
>>>
>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> Also find us on our blog:
>> https://googleadsdeveloper.blogspot.com/
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>  
>> You received this message because you are subscribed to the Google
>> Groups "AdWords API and Google Ads 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 and Google Ads 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/efd8fe9e-fd35-4736-8ffb-cd992a9c1c3b%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/adwords-api/efd8fe9e-fd35-4736-8ffb-cd992a9c1c3b%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/12139bd4-678d-40d3-a062-3f4bd8a25570%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot find AdWords API Center

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Stephane,

Did you create a production manager account or a test account 
<https://developers.google.com/adwords/api/docs/test-accounts>? I ask 
because you'll only see the *AdWords API Center* from a production manager 
account. You won't see it if your account is either of the following:

a) A test manager account
b) A non-manager (client) account

Thanks,
Josh, AdWords API Team

On Thursday, July 19, 2018 at 12:26:46 AM UTC-4, Stephane Michot wrote:
>
> Hi,
>
> I'm having the same issue, I cannot see from the menu AdWords API Center ( 
> neither new interface/old). Despite I've tried the steps you suggested, 
> create a Manager Account, etc... Maybe I do something wrong...
>
> Any suggestions?
>
> Thanks
>
> Le mardi 10 juillet 2018 14:45:32 UTC+2, Josh Radcliff (AdWords API Team) 
> a écrit :
>>
>> Hi,
>>
>> Sorry this has been so frustrating for you. Hopefully I can clear a few 
>> things up.
>>
>> First, you can only apply for a developer token under a production 
>> manager account. Once you've applied:
>>
>>- While your token is pending approval, you can use that developer 
>>token to issue API requests against *any* *test *account, regardless 
>>of its account hierarchy, provided your request includes OAuth 
>> credentials 
>>for the account you are issuing the API request against (specified via 
>> the clientCustomerId 
>>header 
>>
>> <https://developers.google.com/adwords/api/docs/guides/call-structure#request_headers>
>>).
>>- Once your token is approved, you can use that developer token to 
>>issue API requests against *any* *production* or *test* account, 
>>regardless of its account hierarchy, provided your request includes the 
>>proper OAuth credentials.
>>
>> *Test* accounts serve two purposes:
>>
>>1. They allow you to use the API while your token is pending approval.
>>2. Once your token is approved, they allow you to test your code and 
>>experiment with the API without worrying about generating ad spend, since 
>>test accounts will not serve ads.
>>
>> A complicating factor at the moment is that the new AdWords experience in 
>> the UI does not clearly identify test accounts. We're aware of this issue 
>> and are working on a fix. As a *workaround* to that issue, I suggested 
>> checking if the *AdWords API Center* appears in your *manager *account, 
>> since the *AdWords API Center* only appears in an account if it is both: 
>> a) a *production *account; and b) a *manager* account. Therefore, if you 
>> log in as a *manager* account and do *not* see the *AdWords API Center*, 
>> then that account is a test account.
>>
>> If you're still not sure if your account is a test account, you can send 
>> your client customer ID only to me by clicking *Reply privately to 
>> author* on this message.
>>
>> Please let me know if the above doesn't clear things up.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, July 9, 2018 at 5:37:40 PM UTC-4, vodosof...@gmail.com wrote:
>>>
>>> Really, Adwords API is the most confusing API I've ever seen in my 
>>> entire life.
>>>
>>> I made a manager account .. then when I test it says that 
>>> (AuthorizationError.USER_PERMISSION_DENIED) .. when searched online found 
>>> that that's because I'm testing on non-test account .. I created a test 
>>> account then now you say API CENTRE is not available for testing 
>>> accounts
>>> How is that possible! Please give us clear instructions how to even test 
>>> any of this API !!
>>>
>>>
>>> On Wednesday, May 23, 2018 at 5:08:26 PM UTC+2, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> Is the account you are using a manager account? If you're not sure, you 
>>>> can send your client customer ID only to me by clicking *Reply 
>>>> privately to author *on this message.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, May 22, 2018 at 5:33:04 PM UTC-4, nikkyus...@gmail.com 
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm having the same issue, I've tried the steps you suggested, but it 
>>>>> seems the account I'm using *is not* a test account, but still, I 
>>>>> cannot see from the menu AdWords API Center ( neither new interface nor 
>>>>> old 
>>>>> one).
>&g

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Zweitze,

Thanks for providing those details. The engineer investigating this said 
they'll be quite helpful. I'll reply back when he has an update.

Cheers,
Josh, AdWords API Team

On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>
> This error was away at my site for quite a few weeks, but reappeared this 
> morning. The response headers that came with the error were:
>
> Content-Disposition 
> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
> X-Content-Type-Options nosniff
> X-Frame-Options SAMEORIGIN
> X-XSS-Protection 1; mode=block
> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
> Content-Length 0
> Cache-Control private, max-age=0
> Content-Type application/x-gzip; charset=UTF-8
> Date Tue, 17 Jul 2018 04:42:09 GMT
> Expires Tue, 17 Jul 2018 04:42:09 GMT
> Server GSE
>
> The error occured with some old code running v201710.
> CustomerId and ReportDefinition are available if necessary, but I can 
> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
> this time) was successfully used thousands of times.
>
>
>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/b6cd9682-265f-4240-bf39-4b28e4e74358%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot find AdWords API Center

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Sorry this has been so frustrating for you. Hopefully I can clear a few 
things up.

First, you can only apply for a developer token under a production manager 
account. Once you've applied:

   - While your token is pending approval, you can use that developer token 
   to issue API requests against *any* *test *account, regardless of its 
   account hierarchy, provided your request includes OAuth credentials for the 
   account you are issuing the API request against (specified via the 
clientCustomerId 
   header 
   
<https://developers.google.com/adwords/api/docs/guides/call-structure#request_headers>
   ).
   - Once your token is approved, you can use that developer token to issue 
   API requests against *any* *production* or *test* account, regardless of 
   its account hierarchy, provided your request includes the proper OAuth 
   credentials.

*Test* accounts serve two purposes:

   1. They allow you to use the API while your token is pending approval.
   2. Once your token is approved, they allow you to test your code and 
   experiment with the API without worrying about generating ad spend, since 
   test accounts will not serve ads.

A complicating factor at the moment is that the new AdWords experience in 
the UI does not clearly identify test accounts. We're aware of this issue 
and are working on a fix. As a *workaround* to that issue, I suggested 
checking if the *AdWords API Center* appears in your *manager *account, 
since the *AdWords API Center* only appears in an account if it is both: a) 
a *production *account; and b) a *manager* account. Therefore, if you log 
in as a *manager* account and do *not* see the *AdWords API Center*, then 
that account is a test account.

If you're still not sure if your account is a test account, you can send 
your client customer ID only to me by clicking *Reply privately to author* on 
this message.

Please let me know if the above doesn't clear things up.

Cheers,
Josh, AdWords API Team

On Monday, July 9, 2018 at 5:37:40 PM UTC-4, vodosoft.fu...@gmail.com wrote:
>
> Really, Adwords API is the most confusing API I've ever seen in my entire 
> life.
>
> I made a manager account .. then when I test it says that 
> (AuthorizationError.USER_PERMISSION_DENIED) .. when searched online found 
> that that's because I'm testing on non-test account .. I created a test 
> account then now you say API CENTRE is not available for testing 
> accounts
> How is that possible! Please give us clear instructions how to even test 
> any of this API !!
>
>
> On Wednesday, May 23, 2018 at 5:08:26 PM UTC+2, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Is the account you are using a manager account? If you're not sure, you 
>> can send your client customer ID only to me by clicking *Reply privately 
>> to author *on this message.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, May 22, 2018 at 5:33:04 PM UTC-4, nikkyus...@gmail.com wrote:
>>>
>>> Hi,
>>>
>>> I'm having the same issue, I've tried the steps you suggested, but it 
>>> seems the account I'm using *is not* a test account, but still, I 
>>> cannot see from the menu AdWords API Center ( neither new interface nor old 
>>> one).
>>>
>>> Any suggestions?
>>>
>>> Thanks
>>>
>>> On Wednesday, 14 March 2018 14:13:02 UTC, Josh Radcliff (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> You'll only see the AdWords API Center if your manager account is *not* a 
>>>> test manager account. Unfortunately, the only way to determine if the 
>>>> account is a test manager account is:
>>>>
>>>>1. Click on the wrench in the upper right corner
>>>>2. Click on *Return to previous AdWords* in the upper right corner 
>>>>of the menu that pops up
>>>>3. Look for a red banner with *This is a test account!*
>>>>
>>>> If you're still having trouble, please send your customer ID 
>>>> (xxx-xxx-) to me by clicking *Reply privately to author* and I'll 
>>>> take a look.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Wednesday, March 14, 2018 at 5:04:12 AM UTC-4, Ryan wrote:
>>>>>
>>>>> I'm also not seeing the link to the Adwords API Center in what I'm 
>>>>> pretty sure is my manager account. I do see Accounts on the left side, 
>>>>> and 
>>>>> under my profile where accounts are also listed there's a grey Manager 
>>>>> subheading under the account I'm presently logged into.
>>>>>
>&g

Re: BatchJobError.DISK_QUOTA_EXCEEDED with no apparent reason

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sam,

The quota for your account has been reset. Please try creating batch jobs 
again and let me know if you encounter any issues.

Thanks,
Josh, AdWords API Team

On Friday, July 6, 2018 at 9:51:52 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Sam,
>
> I've raised this issue with the batch job engineering team and will reply 
> back as soon as I have an update. This appears to be a problem on our side, 
> since your account does not have any pending batch jobs and should 
> therefore be well below the quota.
>
> Cheers,
> Josh, AdWords API Team
>
> On Thursday, July 5, 2018 at 4:19:05 PM UTC-4, Alan Justino da Silva wrote:
>>
>> @dannison, is there any possibility of the quota being not "refuelled" by 
>> some detail we all missed? Everything is done or canceled already.
>>
>> Maybe something on a lower level, like cgroups, filesystem inodes, 
>> temporary files?
>>
>> Em quinta-feira, 5 de julho de 2018 02:42:35 UTC-3, Dannison Yao (AdWords 
>> API Team) escreveu:
>>>
>>> Hi Sam,
>>>
>>> The error BatchJobError.DISK_QUOTA_EXCEEDED 
>>> <https://developers.google.com/adwords/api/docs/appendix/limits#batch-job> 
>>> is 
>>> encountered when you have reached the size limit for batch job operations 
>>> which is a total of 1GB. What you could do is check for the 
>>> diskUsageQuotaBalance 
>>> <https://developers.google.com/adwords/api/docs/reference/v201806/BatchJobService.BatchJob#diskusagequotabalance>
>>>  which 
>>> will return the disk quota balance of the batch job's customer in KB. You 
>>> can check and cancel the batch jobs in the AWAITING_FILE or ACTIVE status 
>>> and retry the request or you could wait until the size of pending 
>>> operations falls below the limit before creating new jobs.
>>>
>>> Regards,
>>> Dannison
>>> AdWords API Team
>>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/d0d90db1-596a-4114-84f0-445cbf101f6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to retrieve disapproval reasons for an ad through the api

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Max,

You can use the PolicySummary field 

 to 
retrieve all policy-related information for an ad, including trademark 
issues. You might find the CombinedApprovalStatus 

 field 
useful as well.

Cheers,
Josh, AdWords API Team

On Friday, July 6, 2018 at 4:05:16 PM UTC-4, maxim.napa...@system1.com 
wrote:
>
> Hey there,
>
> I am trying to run a similar report, but I noticed that the 
> AdGroupAdTrademarkDisapproved field no longer exists. Is there any way to 
> still retrieve this information via the reporting API?
>
> Best,
> Max
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/7cd124da-ed9e-4a0e-9456-4f172af6e4d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Policy violations - v201710 vs 201706

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg, Peter,

Thanks for providing such detailed information on this issue. I've passed 
this on to the policy expert on the engineering team and will let you know 
as soon as I have an update.

Cheers,
Josh, AdWords API Team

On Tuesday, July 3, 2018 at 11:20:56 AM UTC-4, GregT wrote:
>
> I just wanted to mention that we're experiencing something similar moving 
> to v201806 and trying to test that things are working. We have tests where 
> some should be exemptable ad text and some not exemptable, to make sure we 
> handle things correctly. At this point, the only thing we can get to 
> trigger any kind of policy violation in a test account with v201806 is 
> multiple exclamation points, which trigger the new PolicyFindingError 
> (which is good that we can trigger that). 
>
> But, using all kinds of other ad text that produce PolicyViolationErrors 
> in production in v201802 and/or are explicitly mentioned as violating the 
> ad editorial policy (like "work @home", "big big SALE", "FR33 ShiPPiNG", 
> "buy hunting rifle", various brand names that produce trademark violations 
> in production, etc.) don't produce any kind of PolicyViolationError against 
> our test accounts in v201806, breaking our tests and making it very hard to 
> make sure the code works.
>
> For us, and possibly Peter, if you could just give us some example ad 
> texts that would produce both exemptable and non-exemptable 
> PolicyViolationErrors in test accounts with v201806, that'd be good enough 
> (rather than, for example, trying to make the test accounts in v201806 do 
> identical policy violation checks as production).
>
> Thanks in advance,
> Greg
>
>
> On Tuesday, July 3, 2018 at 5:51:44 AM UTC-5, Peter Lanser wrote:
>>
>> Hi, we are currently migrating from Adwords API v201710 to v201806 and we 
>> are observing an issue regarding policy violations / excemption requests.
>>
>> Part of our test suite is the creation of an (expanded) text ad 
>> triggering a PolicyViolationError. Everything is fine with v201710 - we are 
>> expecting this error (and creating an excemption request later).
>>
>> [INFO] 
>> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
>> SOAP response:
>> 
>> http://schemas.xmlsoap.org/soap/envelope/;>
>> ...
>> 
>> 
>> ...
>> 
>> https://adwords.google.com/api/adwords/cm/v201710;>
>> ...
>> http://www.w3.org/2001/XMLSchema-instance; 
>> xsi:type="PolicyViolationError">
>> ...
>> 
>> PolicyViolationError.POLICY_ERROR
>> 
>> PolicyViolationError
>> 
>> weapons
>> Rifle
>> 
>> Google 
>> AdWords
>> 
>> This ad or keyword 
>> requires review before it can run.
>> true
>> ...
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> However, the error is not triggered when using v201806. The expected 
>> error is not triggered:
>>
>> [DEBUG] 
>> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
>> SOAP response:
>> 
>> http://schemas.xmlsoap.org/soap/envelope/;>
>> ...
>> 
>> https://adwords.google.com/api/adwords/cm/v201806;>
>> 
>> 
>> AdGroupAdReturnValue
>> 
>> ...
>> http://www.w3.org/2001/XMLSchema-instance; xsi:type="ExpandedTextAd">
>> ...
>> 
>> PAUSED
>> 
>> REVIEW_IN_PROGRESS
>> 
>> UNDER_REVIEW
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> We are aware that there are some changes concerning policy violations as 
>> mentioned in 
>> https://developers.google.com/adwords/api/docs/reference/release-notes/v201806#policy
>>  
>> and 
>> https://developers.google.com/adwords/api/docs/guides/exemption-requests.
>> However, we wouldn't have expected that no error is triggered at all.
>>
>> Are we missing something? Why isn't the policy error triggered when using 
>> v201806?
>>
>> Thanks for your help,
>> Peter
>>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 

Re: BatchJobError.DISK_QUOTA_EXCEEDED with no apparent reason

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sam,

I've raised this issue with the batch job engineering team and will reply 
back as soon as I have an update. This appears to be a problem on our side, 
since your account does not have any pending batch jobs and should 
therefore be well below the quota.

Cheers,
Josh, AdWords API Team

On Thursday, July 5, 2018 at 4:19:05 PM UTC-4, Alan Justino da Silva wrote:
>
> @dannison, is there any possibility of the quota being not "refuelled" by 
> some detail we all missed? Everything is done or canceled already.
>
> Maybe something on a lower level, like cgroups, filesystem inodes, 
> temporary files?
>
> Em quinta-feira, 5 de julho de 2018 02:42:35 UTC-3, Dannison Yao (AdWords 
> API Team) escreveu:
>>
>> Hi Sam,
>>
>> The error BatchJobError.DISK_QUOTA_EXCEEDED 
>>  
>> is 
>> encountered when you have reached the size limit for batch job operations 
>> which is a total of 1GB. What you could do is check for the 
>> diskUsageQuotaBalance 
>> 
>>  which 
>> will return the disk quota balance of the batch job's customer in KB. You 
>> can check and cancel the batch jobs in the AWAITING_FILE or ACTIVE status 
>> and retry the request or you could wait until the size of pending 
>> operations falls below the limit before creating new jobs.
>>
>> Regards,
>> Dannison
>> AdWords API Team
>>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/c4fe993c-a874-4a23-a71f-8465feee3f09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: why i am not able to create the MCC test account.?

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Satyaprakash,

The new AdWords experience doesn't clearly indicate when an account is a 
test account. To find that information, please complete the following steps 
for the original account you mentioned:

1. Log into the account.
2. In the upper right corner, click the wrench icon.
3. In the upper right corner of the window that appears, click *Return to 
previous AdWords*.
4. Check if you see a red banner that says *This is a test account!*

If you do not see the red banner in step 4, then the account is not a test 
account. If you'd like, you can send the customer ID of the account to me 
by clicking *Reply privately to author* on this message.

Thanks,
Josh, AdWords API Team

On Friday, July 6, 2018 at 3:46:15 AM UTC-4, Peter Oliquino (AdWords API 
Team) wrote:
>
> Hi Satyaprakash,
>
> We've reached out to the rest of our team to discuss this issue. We'll 
> update you immediately once we have information regarding this.
>
> Best regards,
> Peter
> AdWords API Team
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/efd8fe9e-fd35-4736-8ffb-cd992a9c1c3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't see Video Campaigns in Video Performance report

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Since this experimental campaign type is filtered out of all AdWords API 
requests, I don't see a way you can identify that type of campaign using 
the API.

>From the user interface, you can identify these campaigns by looking for 
>*Campaign 
subtype* of *Reach*. You *may* also be able to retrieve the campaign using 
AdWords 
Scripts <https://developers.google.com/adwords/scripts/> if you want to 
give that a try.

<https://lh3.googleusercontent.com/-qyIx6mGbG-M/WztxL8r6ENI/AEs/ZbJE4v9grvQWHruFewcEnR925hbjAxtGQCLcBGAs/s1600/rvYxxrEcgeM.png>

Cheers,
Josh, AdWords API Team

On Monday, July 2, 2018 at 4:45:29 PM UTC-4, Oksana Sulyma wrote:
>
> Thanks for checking this, Josh and AdWords API Team!
>
> How can I identify that campaign is of this experimental type? I mean how 
> can I check this in UI and if there is some API endpoint you could 
> recommend me to use for checking if campaign statistic is available by API? 
>
> Thanks again for your help!
>
> Oksana
> On 02.07.18 22:54, 'Josh Radcliff (AdWords API Team)' via AdWords API and 
> Google Ads API Forum wrote:
>
> Hi Oksana, 
>
> The campaign in question (campaign ID 1412356032) has an experimental 
> campaign type that's only supported in the AdWords user interface.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, July 2, 2018 at 8:29:53 AM UTC-4, Oksana Sulyma wrote: 
>>
>> Thanks Bharani,
>> Details sent!
>>
>> On Friday, June 29, 2018 at 6:44:09 PM UTC+3, Bharani Cherukuri (AdWords 
>> API Team) wrote: 
>>>
>>> Hi Oksana,  
>>>
>>> Could you share the specific client account CID along with the complete 
>>> report definition 
>>> <https://developers.google.com/adwords/api/docs/guides/reporting#create_a_report_definition>
>>>  for 
>>> which you're not seeing the video campaigns, so I can take a look? You can 
>>> reply back via *Reply privately to author* option. 
>>>
>>> Thanks,
>>> Bharani, AdWords API Team
>>>
>> -- 
> -- 
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog:
> https://googleadsdeveloper.blogspot.com/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>  
> You received this message because you are subscribed to the Google
> Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/adwords-api/AIx6xonx4NY/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/879f71ff-ad38-4cfc-a783-2d592566703e%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/adwords-api/879f71ff-ad38-4cfc-a783-2d592566703e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/b26ec8ac-f59c-48bf-92e0-11ef1e81c0b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't see Video Campaigns in Video Performance report

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Oksana,

The campaign in question (campaign ID 1412356032) has an experimental 
campaign type that's only supported in the AdWords user interface.

Thanks,
Josh, AdWords API Team

On Monday, July 2, 2018 at 8:29:53 AM UTC-4, Oksana Sulyma wrote:
>
> Thanks Bharani,
> Details sent!
>
> On Friday, June 29, 2018 at 6:44:09 PM UTC+3, Bharani Cherukuri (AdWords 
> API Team) wrote:
>>
>> Hi Oksana, 
>>
>> Could you share the specific client account CID along with the complete 
>> report definition 
>> 
>>  for 
>> which you're not seeing the video campaigns, so I can take a look? You can 
>> reply back via *Reply privately to author* option. 
>>
>> Thanks,
>> Bharani, AdWords API Team
>>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/879f71ff-ad38-4cfc-a783-2d592566703e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deleting "Removed" Entities

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sam,

The other accounts under the manager account should not impact the account 
limit.

I noticed that you deleted a large # of campaigns in this particular 
account on the 25th and 26th, and then submitted your batch job on the 
26th. I'm still investigating, but it's possible that the error you 
encountered in the batch job was a timing issue, where the account limits 
check had not "caught up" with all of the deletes you performed. To test 
this theory, could you retry your batch job and let me know if it succeeds 
this time?

Thanks,
Josh, AdWords API Team

On Friday, June 29, 2018 at 2:54:07 PM UTC-4, s...@feedonomics.com wrote:
>
> Hi Dannison,
>
> The Client Customer ID for which we received the campaign limit error has 
> 0 campaigns:
>
>
> 
>
> However, we do have many other linked accounts:
>
>
> 
>
> So is the limit coming from all the other connected accounts? That would 
> be extremely limiting if that's the case.
>
> Thanks,
> Sam
>
> On Thursday, June 28, 2018 at 7:55:12 PM UTC-7, Dannison Yao (AdWords API 
> Team) wrote:
>>
>> Hi Sam,
>>
>> Thank you for providing the requested information privately. Allow me to 
>> reply in the public thread for other developer's reference. Upon 
>> investigation of the logs you provided, you were over the system limit for 
>> the number of campaigns allowed which is 10,000 according to this guide 
>> . Based on your 
>> logs, you have reached a total of 10,031 campaigns already. I suggest you 
>> do a clean up to prevent this error from re-occurring.
>>
>> Let me know if you have further clarifications.
>>
>> Regards,
>> Dannison
>> AdWords API Team
>>
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/db6d77ed-c346-4c6a-8d57-2d9763074d2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ACTION_NOT_PERMITTED on BudgetOrderService

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Deepak and I discussed this in a private thread. My apologies for not 
posting back the info I provided here.

The question I asked Deepak to check was:

When you issued your request, did you use OAuth2 credentials from a user 
with access to the manager account that's whitelisted for 
*BudgetOrderService*? Per the guide 

:

A BudgetOrder can then be created for a client account so long as the manager 
> making an API request: 
> Has access to the manager account that owns a particular billing customer.
> Has access to the client account that should use the billing customer.
> Is whitelisted for BudgetOrderService.


Could you check the above and let me know if that doesn't resolve the 
problem?

Thanks,
Josh, AdWords API Team

On Tuesday, June 26, 2018 at 4:33:52 PM UTC-4, yueya...@163.com wrote:
>
> Hi Deepak,
>
> I met the same problem with you.I wonder if your problem is solved. If it 
> is, please tell me how to do. Thanks.
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/9b44729d-5be3-4491-9cb0-44625b7b932d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Dynamics Remarketing ads for retail

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Although the AdWords API does not support template ID 416, you can now 
create a ResponsiveDisplayAd 
<https://developers.google.com/adwords/api/docs/reference/v201806/AdGroupAdService.ResponsiveDisplayAd>
 for 
your dynamic remarketing campaigns. The process for doing so will be 
essentially the same as the *createAd* step of the Add a Shopping dynamic 
remarketing campaign example 
<https://developers.google.com/adwords/api/docs/samples/java/advanced-operations#add-a-shopping-dynamic-remarketing-campaign>
.

Thanks,
Josh, AdWords API Team

On Monday, June 18, 2018 at 4:19:40 PM UTC-4, Amit P Jivani wrote:
>
> Is this feature available now? 
>
>
> On Saturday, 19 December 2015 01:52:56 UTC+5:30, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> The AdWords API lets you manage the feed items for dynamic remarketing 
>> ads, but it does not support creating the dynamic display ads (with 
>> Template Ad ID 416) themselves. Therefore, you'll need to create the ads 
>> through the user interface first. After that, you'll be able to use the API 
>> to add/remove/update the dynamic data used for those ads.
>>
>> For more info on managing your feed items for dynamic remarketing ads, 
>> check out our Dynamic Remarketing guide 
>> <https://developers.google.com/adwords/api/docs/guides/dynamic-remarketing>
>> .
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, December 17, 2015 at 5:21:48 PM UTC-5, Ezequiel Murillo 
>> wrote:
>>>
>>> Sorry, I think I didn't explain myself as I should have. I want to 
>>> create an ad for a Dynamic Remarketing Campaign in the Display Network, not 
>>> a Shopping campaign.
>>> I would also like to have a many products in a single ad, so that's what 
>>> I thought I would need a Template ad, I guess an html5 template ad. 
>>> The type of ad I want to create using the API is like the one explained 
>>> here:
>>>
>>> https://support.google.com/adwords/answer/3265299?hl=en
>>>
>>> When I create them using the UI I just choose a template and the images 
>>> and everything are pulled from my Merchant Center. I'm just not sure how to 
>>> do that from the API. 
>>> I dont find the one in:
>>> https://developers.google.com/adwords/api/docs/guides/template-ads
>>> very informative.
>>>
>>> Thanks!
>>>
>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/2f8018e4-5a9e-40d4-a40c-2b5a9e1847f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Suddenly getting AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi James,

Thanks for the update. We rolled out a fix for this yesterday and the error 
rate returned to normal since then. If anyone else is still unexpectedly 
encountering this error, please reply back here.

Cheers,
Josh, AdWords API Team

On Wednesday, June 13, 2018 at 9:45:35 AM UTC-4, James Andrews wrote:
>
> These errors have disappeared.  Not sure what happened but wanted to 
> report what I am seeing in our environment.
>
> James
>
> On Jun 12, 2018, at 7:51 AM, Alon Diamant  wrote:
>
> Hey there Caihua,
>
> Mind sharing what you by "empty client customer ID"? I send in an empty 
> string or a null in clientCustomerId and I still get the same 
> AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED error.
>
> Thanks,
>
> Alon
>
> On Monday, June 11, 2018 at 9:21:11 PM UTC+3, Caihua Du wrote:
>>
>> This issue happened to us too. Lots of client have the same errors and it 
>> suddenly shows up from 6/8 and nothing has been changed from our side. 
>>
>> In our code, we will have to pass in an empty client customer id in order 
>> to get back all the accounts under this customer. Not sure what has been 
>> changed from API side. 
>>
>> Please help take a look, thanks!
>> Caihua.
>>
>>
>> On Monday, June 11, 2018 at 4:44:55 AM UTC-7, James Andrews wrote:
>>>
>>> I had left it alone over the weekend, to see if it fixed itself, and was 
>>> just digging into why it was happening, I’ll look there as well and confirm 
>>> that’s where the error is happening.
>>>
>>> Thanks
>>> James
>>>
>>> On Jun 11, 2018, at 7:44 PM, Ondřej P  wrote:
>>>
>>> Hi James,
>>>
>>> it happens intermittently during the getCustomers API call.
>>>
>>> Ondrej
>>>
>>> Dne pondělí 11. června 2018 12:17:22 UTC+2 James Andrews napsal(a):

 Well glad it's not just me, not glad that either of us have to deal 
 with this.  I am still getting these errors intermittently.  Are they 
 always called?  or do they show up intermittently for you as well?

 James

 On Monday, June 11, 2018 at 7:14:10 PM UTC+9, Ondřej P wrote:
>
> Hi,
>
> I have the same issue since 8.6.2018.
> 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/v201802; 
> soapenv:mustUnderstand="0">
> https://adwords.google.com/api/adwords/cm/v201802;>REDACTED
> 
> https://adwords.google.com/api/adwords/cm/v201802;>ROI-Hunter 
> (AwApi-Java, AdWords-Axis/3.12.0, Common-Java/3.12.0, Axis/1.4, 
> Java/1.8.0_91, maven)
> https://adwords.google.com/api/adwords/cm/v201802;>false
> 
> https://adwords.google.com/api/adwords/cm/v201802;>false
> 
> 
> 
> 
> https://adwords.google.com/api/adwords/mcm/v201802"/>
> 
> 
>
> Response:
> 
> http://schemas.xmlsoap.org/soap/envelope/;>
> 
> https://adwords.google.com/api/adwords/mcm/v201802; xmlns:ns2="
> https://adwords.google.com/api/adwords/cm/v201802;>
> 00056e5a331a8a1b6f439c090121
> 
> CustomerService
> getCustomers
> 1
> 225
> 
> 
> 
> 
> soap:Server
> 
> [AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED 
> @ ; trigger:'null']
> 
> https://adwords.google.com/api/adwords/mcm/v201802; xmlns:ns2="
> https://adwords.google.com/api/adwords/cm/v201802;>
> 
> [AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED 
> @ ; trigger:'null']
> ApiException
> 
> http://www.w3.org/2001/XMLSchema-instance; xsi:type=
> "ns2:AuthenticationError">
> 
> null
> 
> AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED
> AuthenticationError
> 
> CLIENT_CUSTOMER_ID_IS_REQUIRED
> 
> 
> 
> 
> 
> 
> 
>
>
>
> Dne pátek 8. června 2018 19:43:41 UTC+2 James Andrews napsal(a):
>>
>> Our software has been working for months with no issues, tonight 
>> suddenly all of our Adwords tokens throw this error.
>>
>> AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED
>>
>> Is something broken?  Is there a place we can go to see what the 
>> status of an API is if there are problems?
>>
>> Thanks,
>> James
>>
>
>>> -- 
>>> -- 
>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>> Also find us on our blog:
>>> https://googleadsdeveloper.blogspot.com/
>>> 

Re: Suddenly getting AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Thanks for reporting this. I've raised it and will provide an update as 
soon as I have more information.

Thanks,
Josh, AdWords API Team

On Monday, June 11, 2018 at 2:21:11 PM UTC-4, Caihua Du wrote:
>
> This issue happened to us too. Lots of client have the same errors and it 
> suddenly shows up from 6/8 and nothing has been changed from our side. 
>
> In our code, we will have to pass in an empty client customer id in order 
> to get back all the accounts under this customer. Not sure what has been 
> changed from API side. 
>
> Please help take a look, thanks!
> Caihua.
>
>
> On Monday, June 11, 2018 at 4:44:55 AM UTC-7, James Andrews wrote:
>>
>> I had left it alone over the weekend, to see if it fixed itself, and was 
>> just digging into why it was happening, I’ll look there as well and confirm 
>> that’s where the error is happening.
>>
>> Thanks
>> James
>>
>> On Jun 11, 2018, at 7:44 PM, Ondřej P  wrote:
>>
>> Hi James,
>>
>> it happens intermittently during the getCustomers API call.
>>
>> Ondrej
>>
>> Dne pondělí 11. června 2018 12:17:22 UTC+2 James Andrews napsal(a):
>>>
>>> Well glad it's not just me, not glad that either of us have to deal with 
>>> this.  I am still getting these errors intermittently.  Are they always 
>>> called?  or do they show up intermittently for you as well?
>>>
>>> James
>>>
>>> On Monday, June 11, 2018 at 7:14:10 PM UTC+9, Ondřej P wrote:

 Hi,

 I have the same issue since 8.6.2018.
 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/v201802; 
 soapenv:mustUnderstand="0">
 https://adwords.google.com/api/adwords/cm/v201802;>REDACTED
 
 https://adwords.google.com/api/adwords/cm/v201802;>ROI-Hunter 
 (AwApi-Java, AdWords-Axis/3.12.0, Common-Java/3.12.0, Axis/1.4, 
 Java/1.8.0_91, maven)
 https://adwords.google.com/api/adwords/cm/v201802;>false
 
 https://adwords.google.com/api/adwords/cm/v201802;>false
 
 
 
 
 https://adwords.google.com/api/adwords/mcm/v201802"/>
 
 

 Response:
 
 http://schemas.xmlsoap.org/soap/envelope/;>
 
 https://adwords.google.com/api/adwords/mcm/v201802; xmlns:ns2="
 https://adwords.google.com/api/adwords/cm/v201802;>
 00056e5a331a8a1b6f439c090121
 
 CustomerService
 getCustomers
 1
 225
 
 
 
 
 soap:Server
 
 [AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED 
 @ ; trigger:'null']
 
 https://adwords.google.com/api/adwords/mcm/v201802; xmlns:ns2="
 https://adwords.google.com/api/adwords/cm/v201802;>
 
 [AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED 
 @ ; trigger:'null']
 ApiException
 
 http://www.w3.org/2001/XMLSchema-instance; xsi:type=
 "ns2:AuthenticationError">
 
 null
 
 AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED
 AuthenticationError
 
 CLIENT_CUSTOMER_ID_IS_REQUIRED
 
 
 
 
 
 
 



 Dne pátek 8. června 2018 19:43:41 UTC+2 James Andrews napsal(a):
>
> Our software has been working for months with no issues, tonight 
> suddenly all of our Adwords tokens throw this error.
>
> AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED
>
> Is something broken?  Is there a place we can go to see what the 
> status of an API is if there are problems?
>
> Thanks,
> James
>

>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> Also find us on our blog:
>> https://googleadsdeveloper.blogspot.com/
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>  
>> You received this message because you are subscribed to the Google
>> Groups "AdWords API and Google Ads API Forum" group.
>> To post to this group, send email to adwor...@googlegroups.com
>> To unsubscribe from this group, send email to
>> adwords-api...@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 and Google Ads API Forum" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/adwords-api/4-ZyhkTQDnI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an 

Re: CustomerService CUSTOMER_NOT_FOUND error

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

I've contacted the engineers who are working on this. I'll provide an 
update once I hear back from them.

Thanks,
Josh, AdWords API Team

On Friday, June 8, 2018 at 4:21:43 AM UTC-4, Oksana Sulyma wrote:
>
> Hi guys, 
> Just wanted to let you know that we are still affected by this problem and 
> also await for solution. 
> Thanks!
>
> On Tuesday, June 5, 2018 at 4:06:28 PM UTC+3, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Tiana,
>>
>> Please follow the post that Timm mentioned 
>> <https://groups.google.com/d/msg/adwords-api/uSomm1x4nKw/FEqmXpdIAQAJ>. 
>> To avoid duplicating information, my colleague will be providing updates on 
>> the issue there.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, June 4, 2018 at 12:14:44 PM UTC-4, Timm Janssen wrote:
>>>
>>> Hi,
>>>
>>> I had the same issue using v201710, with v201802 it's a 
>>> CUSTOMER_NOT_ACTIVE error, see 
>>> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/adwords-api/uSomm1x4nKw/YhjSkLMbAQAJ
>>>
>>> Moreover the Java library doesn't seem to be affected.
>>>
>>> Thanks,
>>> Timm
>>>
>>> On Monday, June 4, 2018 at 5:59:53 PM UTC+2, Tiana S. wrote:
>>>>
>>>> Hi Josh,
>>>>
>>>> I'm having the same issue. Please let me know if you have an update. I 
>>>> can of course also provide more info on our requests privately.
>>>>
>>>> Kind regards,
>>>>
>>>> Tiana
>>>>
>>>> On Thursday, 5 April 2018 15:15:58 UTC+2, Josh Radcliff (AdWords API 
>>>> Team) wrote:
>>>>>
>>>>> Hi Oksana,
>>>>>
>>>>> We're still trying to track this one down. Do you happen to have an 
>>>>> example of a request where you encountered this error within the last 5 
>>>>> days? If so, could you *Reply privately to author* on this post and 
>>>>> provide me with the following?
>>>>>
>>>>>1. The date and time of the request, including timezone
>>>>>2. The user whose OAuth credentials were used for the request
>>>>>3. The client customer IDs you expected to receive for that user
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Tuesday, March 13, 2018 at 9:53:29 AM UTC-4, Josh Radcliff (AdWords 
>>>>> API Team) wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The engineering team is looking into this in more detail, and I hope 
>>>>>> to have an update soon. I'll post back here once that happens.
>>>>>>
>>>>>> Thanks,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Monday, March 12, 2018 at 8:17:14 AM UTC-4, Oksana Sulyma wrote:
>>>>>>>
>>>>>>> Hi guys, bumping this thread as mentioned issue still exist. We had 
>>>>>>> correspondence in private mode, please let me know if there are any 
>>>>>>> ideas 
>>>>>>> why we might get this error.. Thanks!
>>>>>>>
>>>>>>> On Friday, January 19, 2018 at 6:46:58 PM UTC+2, Bharani Cherukuri 
>>>>>>> (AdWords API Team) wrote:
>>>>>>>>
>>>>>>>> Hello Okasana, 
>>>>>>>>
>>>>>>>> The CUSTOMER_NOT_FOUND 
>>>>>>>> <https://developers.google.com/adwords/api/docs/common-errors#AuthenticationError.CUSTOMER_NOT_FOUND>
>>>>>>>>  error 
>>>>>>>> is received when the ID specified in the request header does not 
>>>>>>>> exist. I 
>>>>>>>> see that you're using the CustomerService.getCustomers() 
>>>>>>>> <https://developers.google.com/adwords/api/docs/reference/v201710/CustomerService#getCustomers>,
>>>>>>>>  
>>>>>>>> which will return all the customers directly accessible by the user 
>>>>>>>> authenticating the call. If the account specified is a new account, it 
>>>>>>>> is 
>>>>>>>> recommended that you wait a few minutes after the account is created 
>>>>>>>> before 
>>>>>>>> issuing requests against it. Could you please recheck the creden

Re: CustomerService CUSTOMER_NOT_FOUND error

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Tiana,

Please follow the post that Timm mentioned 
<https://groups.google.com/d/msg/adwords-api/uSomm1x4nKw/FEqmXpdIAQAJ>. To 
avoid duplicating information, my colleague will be providing updates on 
the issue there.

Thanks,
Josh, AdWords API Team

On Monday, June 4, 2018 at 12:14:44 PM UTC-4, Timm Janssen wrote:
>
> Hi,
>
> I had the same issue using v201710, with v201802 it's a 
> CUSTOMER_NOT_ACTIVE error, see 
> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/adwords-api/uSomm1x4nKw/YhjSkLMbAQAJ
>
> Moreover the Java library doesn't seem to be affected.
>
> Thanks,
> Timm
>
> On Monday, June 4, 2018 at 5:59:53 PM UTC+2, Tiana S. wrote:
>>
>> Hi Josh,
>>
>> I'm having the same issue. Please let me know if you have an update. I 
>> can of course also provide more info on our requests privately.
>>
>> Kind regards,
>>
>> Tiana
>>
>> On Thursday, 5 April 2018 15:15:58 UTC+2, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Oksana,
>>>
>>> We're still trying to track this one down. Do you happen to have an 
>>> example of a request where you encountered this error within the last 5 
>>> days? If so, could you *Reply privately to author* on this post and 
>>> provide me with the following?
>>>
>>>1. The date and time of the request, including timezone
>>>2. The user whose OAuth credentials were used for the request
>>>3. The client customer IDs you expected to receive for that user
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, March 13, 2018 at 9:53:29 AM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> The engineering team is looking into this in more detail, and I hope to 
>>>> have an update soon. I'll post back here once that happens.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, March 12, 2018 at 8:17:14 AM UTC-4, Oksana Sulyma wrote:
>>>>>
>>>>> Hi guys, bumping this thread as mentioned issue still exist. We had 
>>>>> correspondence in private mode, please let me know if there are any ideas 
>>>>> why we might get this error.. Thanks!
>>>>>
>>>>> On Friday, January 19, 2018 at 6:46:58 PM UTC+2, Bharani Cherukuri 
>>>>> (AdWords API Team) wrote:
>>>>>>
>>>>>> Hello Okasana, 
>>>>>>
>>>>>> The CUSTOMER_NOT_FOUND 
>>>>>> <https://developers.google.com/adwords/api/docs/common-errors#AuthenticationError.CUSTOMER_NOT_FOUND>
>>>>>>  error 
>>>>>> is received when the ID specified in the request header does not exist. 
>>>>>> I 
>>>>>> see that you're using the CustomerService.getCustomers() 
>>>>>> <https://developers.google.com/adwords/api/docs/reference/v201710/CustomerService#getCustomers>,
>>>>>>  
>>>>>> which will return all the customers directly accessible by the user 
>>>>>> authenticating the call. If the account specified is a new account, it 
>>>>>> is 
>>>>>> recommended that you wait a few minutes after the account is created 
>>>>>> before 
>>>>>> issuing requests against it. Could you please recheck the credentials 
>>>>>> used 
>>>>>> if they belong to the valid AdWords account user and try the request 
>>>>>> again? 
>>>>>> If you continue to have an issue with this, could you share us the email 
>>>>>> address used to authenticate the API call? Please use *Reply 
>>>>>> privately to author* option to provide the details. 
>>>>>>
>>>>>> Regards,
>>>>>> Bharani, AdWords API Team
>>>>>>
>>>>>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/d1d92f24-38c0-4270-85b7-f4a249a6c166%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot find AdWords API Center

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Is the account you are using a manager account? If you're not sure, you can 
send your client customer ID only to me by clicking *Reply privately to 
author *on this message.

Thanks,
Josh, AdWords API Team

On Tuesday, May 22, 2018 at 5:33:04 PM UTC-4, nikkyusatest...@gmail.com 
wrote:
>
> Hi,
>
> I'm having the same issue, I've tried the steps you suggested, but it 
> seems the account I'm using *is not* a test account, but still, I cannot 
> see from the menu AdWords API Center ( neither new interface nor old one).
>
> Any suggestions?
>
> Thanks
>
> On Wednesday, 14 March 2018 14:13:02 UTC, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi,
>>
>> You'll only see the AdWords API Center if your manager account is *not* a 
>> test manager account. Unfortunately, the only way to determine if the 
>> account is a test manager account is:
>>
>>1. Click on the wrench in the upper right corner
>>2. Click on *Return to previous AdWords* in the upper right corner of 
>>the menu that pops up
>>3. Look for a red banner with *This is a test account!*
>>
>> If you're still having trouble, please send your customer ID 
>> (xxx-xxx-) to me by clicking *Reply privately to author* and I'll 
>> take a look.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 14, 2018 at 5:04:12 AM UTC-4, Ryan wrote:
>>>
>>> I'm also not seeing the link to the Adwords API Center in what I'm 
>>> pretty sure is my manager account. I do see Accounts on the left side, and 
>>> under my profile where accounts are also listed there's a grey Manager 
>>> subheading under the account I'm presently logged into.
>>>
>>> Any help would be great, thanks!
>>>
>>>
>>> On Tuesday, March 13, 2018 at 7:00:21 AM UTC-7, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> Just so I'm clear on the first question, could you explain which issue 
>>>> you would like a clear solution for? There have been a couple of different 
>>>> issues discussed in this thread.
>>>>
>>>> To check if you email is a manager account, you have a few options:
>>>>
>>>>1. Log into adwords.google.com using the email address. If the 
>>>>account is a manager account, you will see *Accounts* in the list 
>>>>of pages on the left.
>>>>2. Issue a CustomerService.getCustomers 
>>>>
>>>> <https://developers.google.com/adwords/api/docs/reference/v201802/CustomerService#getcustomers>
>>>>  request 
>>>>using OAuth2 credentials for the account, and inspect the 
>>>> canManageClients 
>>>>field 
>>>>
>>>> <https://developers.google.com/adwords/api/docs/reference/v201802/CustomerService.Customer#canmanageclients>.
>>>>  
>>>>If your account is a manager account, *canManageClients* will be 
>>>>*true*.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, March 12, 2018 at 4:56:39 PM UTC-4, Osa Aimola wrote:
>>>>>
>>>>> Going by the number of people with this same issue, this is 
>>>>> obbbvvviiooouussslly a reoccurring problem and should hint at something 
>>>>> being wrong with the process.
>>>>>
>>>>> I've done several searches for how to get this fixed and it just 
>>>>> doesn't work. Can you please, break this down into a clear solution?
>>>>> Also how does one check if their email is a manager account or not? 
>>>>> because I used the steps and it is just not working.
>>>>>
>>>>> On Wednesday, May 7, 2014 at 7:39:45 PM UTC+8, 
>>>>> adwordsku...@ksk-media.de wrote:
>>>>>>
>>>>>> Dear All,
>>>>>>
>>>>>> Our company wants to develop a simple tool that generates AdWords 
>>>>>> reports to send to our customers and exports them to PDF.
>>>>>>
>>>>>> Now to use the API, I understand that I need an Developer Token, 
>>>>>> which I am supposed to find in the MCC Account Settings. But there is no 
>>>>>> link to the AdWords API center on the page referred to here 
>>>>>> <https://developers.google.com/adwords/api/docs/signingup?hl=en> (
>>>>>> https://developers.google.com/adwords/api/docs/signingup?hl=e

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Ron,

The engineering team is still digging into this. I'll be sure to update 
this thread as soon as I have more information.

In the meantime, please retry the requests as Dorian suggested earlier.

Thanks,
Josh, AdWords API Team

On Wednesday, May 16, 2018 at 4:34:19 PM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> are there any updates on this topic? We are eagerly awaiting your response 
> on this one.
>
> Best Regards,
> Ron
>
> Am Freitag, 4. Mai 2018 21:18:47 UTC+2 schrieb Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Dorian,
>>
>> Tracking down the root cause is proving quite challenging, so I don't 
>> have any news to report just yet. In the meantime, retrying failed requests 
>> (provided you're confident the request is valid) is a good approach.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:
>>>
>>> Hi Josh,
>>>
>>> any updates on this topic? Can we just retry downloads that fail with 
>>> this specific error condition (400 HTTP status code and no response 
>>> content) for the time being?
>>>
>>> Thanks for your feedback and best regards,
>>> Dorian
>>>
>>> On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi Ron,
>>>>
>>>> Thanks for getting back to me. I think we have enough examples now to 
>>>> track this down. The eng team is making progress, but I don't have any 
>>>> updates to report just yet. I'll reply back as soon as I have more info.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>>>>
>>>>> Taking into account the daylight savings we currently have UTC+2.
>>>>> Concerning the 502 unfortionately I don't have the logs at hand any 
>>>>> more -- but what I remember was an 502 which resulted in a 400 in our 
>>>>> usage 
>>>>> of the library.
>>>>>
>>>>> Best Regards,
>>>>> Ron
>>>>>
>>>>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff 
>>>>> (AdWords API Team):
>>>>>>
>>>>>> Also, I forgot to ask: is that timestamp in CST?
>>>>>>
>>>>>> Thanks,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
>>>>>> API Team) wrote:
>>>>>>>
>>>>>>> Hi Ron,
>>>>>>>
>>>>>>> I'm a little perplexed by the most recent example. I see it shows 
>>>>>>> both:
>>>>>>>
>>>>>>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
>>>>>>> Gateway
>>>>>>>
>>>>>>> and:
>>>>>>>
>>>>>>> Caused by: HTTP Response Code: *400*
>>>>>>>
>>>>>>> Was that a bad copy/paste, or are you actually seeing both 502 and 
>>>>>>> 400 mentioned within the same error?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Josh, AdWords API Team
>>>>>>>
>>>>>>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> After adding some more logging, another example that results in a 
>>>>>>>> 400 on our side:
>>>>>>>>
>>>>>>>>
>>>>>>>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>>>>>>>> Service: reportdownload Method: POST clientCustomerId: XXX URL: 
>>>>>>>> https://adwords.google.com//api/adwords/reportdownload/v201710 Request 
>>>>>>>> ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
>>>>>>>> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 
>>>>>>>> 502: 
>>>>>>>> Bad Gateway
>>>>>>>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>>>>>>>> request:
>>>>>>>> accept-encoding: [gzip]
>>>>>>>>

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Dorian,

Tracking down the root cause is proving quite challenging, so I don't have 
any news to report just yet. In the meantime, retrying failed requests 
(provided you're confident the request is valid) is a good approach.

Thanks,
Josh, AdWords API Team

On Friday, May 4, 2018 at 7:32:45 AM UTC-4, Dorian Kind wrote:
>
> Hi Josh,
>
> any updates on this topic? Can we just retry downloads that fail with this 
> specific error condition (400 HTTP status code and no response content) for 
> the time being?
>
> Thanks for your feedback and best regards,
> Dorian
>
> On Monday, 23 April 2018 14:52:50 UTC+2, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Ron,
>>
>> Thanks for getting back to me. I think we have enough examples now to 
>> track this down. The eng team is making progress, but I don't have any 
>> updates to report just yet. I'll reply back as soon as I have more info.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>>>
>>> Taking into account the daylight savings we currently have UTC+2.
>>> Concerning the 502 unfortionately I don't have the logs at hand any more 
>>> -- but what I remember was an 502 which resulted in a 400 in our usage of 
>>> the library.
>>>
>>> Best Regards,
>>> Ron
>>>
>>> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Also, I forgot to ask: is that timestamp in CST?
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords 
>>>> API Team) wrote:
>>>>>
>>>>> Hi Ron,
>>>>>
>>>>> I'm a little perplexed by the most recent example. I see it shows both:
>>>>>
>>>>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad 
>>>>> Gateway
>>>>>
>>>>> and:
>>>>>
>>>>> Caused by: HTTP Response Code: *400*
>>>>>
>>>>> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
>>>>> mentioned within the same error?
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>>>>>
>>>>>> After adding some more logging, another example that results in a 400 
>>>>>> on our side:
>>>>>>
>>>>>>
>>>>>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>>>>>> Service: reportdownload Method: POST clientCustomerId: XXX URL: 
>>>>>> https://adwords.google.com//api/adwords/reportdownload/v201710 Request 
>>>>>> ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
>>>>>> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 502: 
>>>>>> Bad Gateway
>>>>>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>>>>>> request:
>>>>>> accept-encoding: [gzip]
>>>>>> authorization: REDACTED
>>>>>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
>>>>>> maven, ReportDownloader)]
>>>>>> developertoken: REDACTED
>>>>>> clientcustomerid: XXX
>>>>>> includezeroimpressions: false
>>>>>>
>>>>>> Content:
>>>>>> __rdquery: SELECT Conversions,ConversionValue FROM 
>>>>>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>>>>>> 20180316,20180415
>>>>>> __fmt: XML
>>>>>>
>>>>>> Caused by: HTTP Response Code: 400 at 
>>>>>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>>>>>
>>>>>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff 
>>>>>> (AdWords API Team):
>>>>>>>
>>>>>>> Hi Ron,
>>>>>>>
>>>>>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>>>>>> Would you mind sending over the customer ID where your developer token 
>>>>>>> is 
>&

Re: Python support for new Ads API?

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Vladimir,

PHP is another one where we know there's significant interest. I don't have 
any news on that front just yet, though.

Thanks,
Josh, AdWords API Team

On Thursday, April 26, 2018 at 6:23:06 AM UTC-4, Vladimir Tatarsky wrote:
>
>
> Hi Josh, any thoughs about PHP support?
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/b2845b3f-4079-4d0b-be69-260730eb50d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Python support for new Ads API?

['Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Ian,

Thanks for starting this conversation! I'll be interested to hear what 
others in the group have to say.

Regarding Python support, we're definitely aware that there's a strong 
Python + AdWords API user base out there. I don't have details I can share 
at the moment, but please keep an eye on our blog 
 for 
updates over the coming weeks and months. We'll have lots to say there 
about the Google AdsAPI! :)

Cheers,
Josh, AdWords API Team

On Tuesday, April 24, 2018 at 6:08:39 AM UTC-4, i...@everquote.com wrote:
>
> Hi all,
>
> Broadly to the group: does anyone else here have a use case for a Python 
> SDK to the new Ads API? +1 here if so!
>
> For the Google team: is Python support on the roadmap, and if so, how are 
> you measuring demand? Would love to get some insight into how the three 
> supported languages (Java, C#, Ruby) were chosen and whether it makes sense 
> to start discussing specific timelines for Python. Happy to sync with our 
> team on what use cases EverQuote has that could be shared publicly or 
> potentially take some of the discussion offline under NDA (if that's 
> helpful). As a disclaimer, I cannot speak for or represent EverQuote. All 
> comments and opinions here and henceforth are my own.
>
> Please let me know if you need anything from me to answer or if it's too 
> early to say. :)
>
> Best,
> Ian
>

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

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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/f68f989f-4687-42fc-8534-446b3a5388e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron,

Thanks for getting back to me. I think we have enough examples now to track 
this down. The eng team is making progress, but I don't have any updates to 
report just yet. I'll reply back as soon as I have more info.

Cheers,
Josh, AdWords API Team

On Monday, April 23, 2018 at 4:16:20 AM UTC-4, Ronald Findling wrote:
>
> Taking into account the daylight savings we currently have UTC+2.
> Concerning the 502 unfortionately I don't have the logs at hand any more 
> -- but what I remember was an 502 which resulted in a 400 in our usage of 
> the library.
>
> Best Regards,
> Ron
>
> Am Montag, 16. April 2018 23:01:11 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Also, I forgot to ask: is that timestamp in CST?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Ron,
>>>
>>> I'm a little perplexed by the most recent example. I see it shows both:
>>>
>>> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway
>>>
>>> and:
>>>
>>> Caused by: HTTP Response Code: *400*
>>>
>>> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
>>> mentioned within the same error?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>>>
>>>> After adding some more logging, another example that results in a 400 
>>>> on our side:
>>>>
>>>>
>>>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>>>> Service: reportdownload Method: POST clientCustomerId: XXX URL: 
>>>> https://adwords.google.com//api/adwords/reportdownload/v201710 Request 
>>>> ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
>>>> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 502: 
>>>> Bad Gateway
>>>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>>>> request:
>>>> accept-encoding: [gzip]
>>>> authorization: REDACTED
>>>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, 
>>>> maven, ReportDownloader)]
>>>> developertoken: REDACTED
>>>> clientcustomerid: XXX
>>>> includezeroimpressions: false
>>>>
>>>> Content:
>>>> __rdquery: SELECT Conversions,ConversionValue FROM 
>>>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>>>> 20180316,20180415
>>>> __fmt: XML
>>>>
>>>> Caused by: HTTP Response Code: 400 at 
>>>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>>>
>>>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
>>>> API Team):
>>>>>
>>>>> Hi Ron,
>>>>>
>>>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>>>> Would you mind sending over the customer ID where your developer token is 
>>>>> registered? You can send it only to me by clicking *Reply privately 
>>>>> to author*.
>>>>>
>>>>> Regarding the timeout theory, the ReportDownloader won't automatically 
>>>>> retry requests. However, if you think timeouts are the root cause here, 
>>>>> you 
>>>>> can adjust the timeout for report downloads programmatically or in your 
>>>>> *ads.properties* file. Check out this section of the ads.properties 
>>>>> file 
>>>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
>>>>>  for 
>>>>> details.
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling 
>>>>> wrote:
>>>>>>
>>>>>> Hi Josh,
>>>>>>
>>>>>> I checked the request data that I provided you and they are exactly 
>>>>>> what I can see in my logs. Maybe I should mention that the provided time 
>>>>>> is 
>>>>>> the time at which the request failed not when it was sent to your 
>>>>>> servers 

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Also, I forgot to ask: is that timestamp in CST?

Thanks,
Josh, AdWords API Team

On Monday, April 16, 2018 at 4:59:35 PM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Ron,
>
> I'm a little perplexed by the most recent example. I see it shows both:
>
> com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway
>
> and:
>
> Caused by: HTTP Response Code: *400*
>
> Was that a bad copy/paste, or are you actually seeing both 502 and 400 
> mentioned within the same error?
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>>
>> After adding some more logging, another example that results in a 400 on 
>> our side:
>>
>>
>> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: 
>> Service: reportdownload Method: POST clientCustomerId: XXX URL: 
>> https://adwords.google.com//api/adwords/reportdownload/v201710 Request 
>> ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
>> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 502: 
>> Bad Gateway
>> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
>> request:
>> accept-encoding: [gzip]
>> authorization: REDACTED
>> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
>> ReportDownloader)]
>> developertoken: REDACTED
>> clientcustomerid: XXX
>> includezeroimpressions: false
>>
>> Content:
>> __rdquery: SELECT Conversions,ConversionValue FROM 
>> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
>> 20180316,20180415
>> __fmt: XML
>>
>> Caused by: HTTP Response Code: 400 at 
>> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>>
>> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Ron,
>>>
>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>> Would you mind sending over the customer ID where your developer token is 
>>> registered? You can send it only to me by clicking *Reply privately to 
>>> author*.
>>>
>>> Regarding the timeout theory, the ReportDownloader won't automatically 
>>> retry requests. However, if you think timeouts are the root cause here, you 
>>> can adjust the timeout for report downloads programmatically or in your 
>>> *ads.properties* file. Check out this section of the ads.properties file 
>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
>>>  for 
>>> details.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>>
>>>> Hi Josh,
>>>>
>>>> I checked the request data that I provided you and they are exactly 
>>>> what I can see in my logs. Maybe I should mention that the provided time 
>>>> is 
>>>> the time at which the request failed not when it was sent to your servers 
>>>> (that time is ~30-40 seconds before).
>>>>
>>>> Concerning the thread-safety recommendations I'm sure that the 
>>>> ReportDownloader and its Session are not used in multiple threads in our 
>>>> code.
>>>>
>>>> Further information: 
>>>> Checking our errors I found an interesting pattern, failing requests 
>>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>>> most likely to be around 1 second.
>>>>
>>>> Maybe a stupid thought but could it be a something like the 
>>>> java-library timing out after 30 seconds and retrying using the provided 
>>>> session/ReportDownloader again which then violates the threadSafety and 
>>>> results in invalid requests?
>>>>
>>>> Best Regards,
>>>> Ron
>>>>
>>>>
>>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff 
>>>> (AdWords API Team):
>>>>>
>>>>> Hi Ronald,
>>>>>
>>>>> I searched the logs on our side and could not find either of those 
>>>>> requests. Are you sure that they were submitted for the account ID you 
>>>>> mentioned?
>>>>>
>>>>> By the way, did you check if you're adhering to the thread saf

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron,

I'm a little perplexed by the most recent example. I see it shows both:

com.google.api.ads.adwords.lib.utils.ReportException: *502*: Bad Gateway

and:

Caused by: HTTP Response Code: *400*

Was that a bad copy/paste, or are you actually seeing both 502 and 400 
mentioned within the same error?

Thanks,
Josh, AdWords API Team

On Monday, April 16, 2018 at 11:27:53 AM UTC-4, Ronald Findling wrote:
>
> After adding some more logging, another example that results in a 400 on 
> our side:
>
>
> 19:07:52 [WARN] c.g.a.a.a.lib.utils.report_download Request made: Service: 
> reportdownload Method: POST clientCustomerId: XXX URL: 
> https://adwords.google.com//api/adwords/reportdownload/v201710 Request 
> ID: null ResponseTime(ms): null OperationsCount: null IsFault: true 
> FaultMessage: com.google.api.ads.adwords.lib.utils.ReportException: 502: 
> Bad Gateway
> 2018-04-15 19:07:52 [INFO] c.g.a.a.a.lib.utils.report_download HTTP 
> request:
> accept-encoding: [gzip]
> authorization: REDACTED
> user-agent: [XXX (AwApi-Java, Common-Java/3.12.0, Java/1.8.0_121, maven, 
> ReportDownloader)]
> developertoken: REDACTED
> clientcustomerid: XXX
> includezeroimpressions: false
>
> Content:
> __rdquery: SELECT Conversions,ConversionValue FROM 
> SHOPPING_PERFORMANCE_REPORT WHERE CountryCriteriaId = 2250 DURING 
> 20180316,20180415
> __fmt: XML
>
> Caused by: HTTP Response Code: 400 at 
> com.google.api.ads.adwords.lib.utils.v201710.DetailedReportDownloadResponseException$Builder.build(DetailedReportDownloadResponseException.java:35)
>
> Am Freitag, 30. März 2018 15:15:38 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token is 
>> registered? You can send it only to me by clicking *Reply privately to 
>> author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't automatically 
>> retry requests. However, if you think timeouts are the root cause here, you 
>> can adjust the timeout for report downloads programmatically or in your 
>> *ads.properties* file. Check out this section of the ads.properties file 
>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly what 
>>> I can see in my logs. Maybe I should mention that the provided time is the 
>>> time at which the request failed not when it was sent to your servers (that 
>>> time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the java-library 
>>> timing out after 30 seconds and retrying using the provided 
>>> session/ReportDownloader again which then violates the threadSafety and 
>>> results in invalid requests?
>>>
>>> Best Regards,
>>> Ron
>>>
>>>
>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Ronald,
>>>>
>>>> I searched the logs on our side and could not find either of those 
>>>> requests. Are you sure that they were submitted for the account ID you 
>>>> mentioned?
>>>>
>>>> By the way, did you check if you're adhering to the thread safety 
>>>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>>>> out as a possible cause of the errors.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>>>>
>>>>> Hi Josh,
>>>>>
>>>>> thx for the hints.
>>>>> Concerning the requested information I can give you 2 identical 
>>>>> request where one succeeded and the other one failed with a 400

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Thanks for providing the customer IDs and timestamps of the failed 
requests. I've passed those along to the reporting team for investigation 
and asked for an update.

Cheers,
Josh, AdWords API Team

On Thursday, April 12, 2018 at 6:11:34 AM UTC-4, Zweitze wrote:
>
> This topic was somehow below my radar, but I occasionally get this too. See 
> here 
> <https://groups.google.com/d/msg/adwords-api/zgGyRXYUF4k/eW8ub-asCAAJ> 
> for recent logs and the response headers that AdWordsAPI sent.
> This error occurred on:
> Dec 22
> Dec 25 (3 times)
> Dec 31
> Jan 1
> Jan 12
> Feb 1
> Feb 6 (2 times)
> Mar 17 (3 times)
> Mar 18
> Mar 23
> Mar 24
> Mar 25
> Mar 26
> Mar 30
> Apr 1
> Apr 3
> Apr 11 (3 times)
> (@Google: I have requests and response headers for each instance).
> We retrieve between 1,000 and 20,000 reports daily. Problems occur on 
> different report types, on different accounts - I can't find a pattern on 
> that.
>
> Like Dorian I wonder how to deal with that error, as a 400-error means a 
> serious error by the client.
>
> On Tuesday, April 3, 2018 at 5:12:12 PM UTC+2, Dorian Kind wrote:
>>
>> Hi all,
>>
>> I thought I posted previously in this thread, but it looks like my 
>> message has been deleted. I just wanted to chime in that we've also been 
>> seeing these sporadic report failures that return a HTTP 400 status code 
>> and no reponse content. They don't seem to be reproducible, from what we 
>> can tell and are most likely not the result of an expired OAuth token or a 
>> malformed report definition as both of these cases give detailed error 
>> messages.
>> We don't feel comfortable automatically retrying report download requests 
>> for error codes below 500, so it'd be great if the Adwords team could shed 
>> some light on the issue.
>>
>> Thanks and best regards,
>> Dorian
>>
>> On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
>> wrote:
>>>
>>> Hi Ron,
>>>
>>> Sorry, I'm still having trouble locating those requests in our logs. 
>>> Would you mind sending over the customer ID where your developer token is 
>>> registered? You can send it only to me by clicking *Reply privately to 
>>> author*.
>>>
>>> Regarding the timeout theory, the ReportDownloader won't automatically 
>>> retry requests. However, if you think timeouts are the root cause here, you 
>>> can adjust the timeout for report downloads programmatically or in your 
>>> *ads.properties* file. Check out this section of the ads.properties file 
>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
>>>  for 
>>> details.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>>
>>>> Hi Josh,
>>>>
>>>> I checked the request data that I provided you and they are exactly 
>>>> what I can see in my logs. Maybe I should mention that the provided time 
>>>> is 
>>>> the time at which the request failed not when it was sent to your servers 
>>>> (that time is ~30-40 seconds before).
>>>>
>>>> Concerning the thread-safety recommendations I'm sure that the 
>>>> ReportDownloader and its Session are not used in multiple threads in our 
>>>> code.
>>>>
>>>> Further information: 
>>>> Checking our errors I found an interesting pattern, failing requests 
>>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>>> most likely to be around 1 second.
>>>>
>>>> Maybe a stupid thought but could it be a something like the 
>>>> java-library timing out after 30 seconds and retrying using the provided 
>>>> session/ReportDownloader again which then violates the threadSafety and 
>>>> results in invalid requests?
>>>>
>>>> Best Regards,
>>>> Ron
>>>>
>>>>
>>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff 
>>>> (AdWords API Team):
>>>>>
>>>>> Hi Ronald,
>>>>>
>>>>> I searched the logs on our side and could not find either of those 
>>>>> requests. Are you sure that they were submitted for the account ID you 
>>>>> mentioned?
>>>>>
>>>>> By the way, did you check if you're adhering 

Re: CustomerService CUSTOMER_NOT_FOUND error

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Oksana,

We're still trying to track this one down. Do you happen to have an example 
of a request where you encountered this error within the last 5 days? If 
so, could you *Reply privately to author* on this post and provide me with 
the following?

   1. The date and time of the request, including timezone
   2. The user whose OAuth credentials were used for the request
   3. The client customer IDs you expected to receive for that user

Thanks,
Josh, AdWords API Team

On Tuesday, March 13, 2018 at 9:53:29 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> The engineering team is looking into this in more detail, and I hope to 
> have an update soon. I'll post back here once that happens.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, March 12, 2018 at 8:17:14 AM UTC-4, Oksana Sulyma wrote:
>>
>> Hi guys, bumping this thread as mentioned issue still exist. We had 
>> correspondence in private mode, please let me know if there are any ideas 
>> why we might get this error.. Thanks!
>>
>> On Friday, January 19, 2018 at 6:46:58 PM UTC+2, Bharani Cherukuri 
>> (AdWords API Team) wrote:
>>>
>>> Hello Okasana, 
>>>
>>> The CUSTOMER_NOT_FOUND 
>>> <https://developers.google.com/adwords/api/docs/common-errors#AuthenticationError.CUSTOMER_NOT_FOUND>
>>>  error 
>>> is received when the ID specified in the request header does not exist. I 
>>> see that you're using the CustomerService.getCustomers() 
>>> <https://developers.google.com/adwords/api/docs/reference/v201710/CustomerService#getCustomers>,
>>>  
>>> which will return all the customers directly accessible by the user 
>>> authenticating the call. If the account specified is a new account, it is 
>>> recommended that you wait a few minutes after the account is created before 
>>> issuing requests against it. Could you please recheck the credentials used 
>>> if they belong to the valid AdWords account user and try the request again? 
>>> If you continue to have an issue with this, could you share us the email 
>>> address used to authenticate the API call? Please use *Reply privately 
>>> to author* option to provide the details. 
>>>
>>> Regards,
>>> Bharani, 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/2e6cb5b0-5dc3-42c0-977a-4cc6c64d4bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi all,

Thanks for letting us know about these errors. I'm following up with our 
reporting team and will post back here when I have an update.

Cheers,
Josh, AdWords API Team

On Tuesday, April 3, 2018 at 11:12:12 AM UTC-4, Dorian Kind wrote:
>
> Hi all,
>
> I thought I posted previously in this thread, but it looks like my message 
> has been deleted. I just wanted to chime in that we've also been seeing 
> these sporadic report failures that return a HTTP 400 status code and no 
> reponse content. They don't seem to be reproducible, from what we can tell 
> and are most likely not the result of an expired OAuth token or a malformed 
> report definition as both of these cases give detailed error messages.
> We don't feel comfortable automatically retrying report download requests 
> for error codes below 500, so it'd be great if the Adwords team could shed 
> some light on the issue.
>
> Thanks and best regards,
> Dorian
>
> On Friday, 30 March 2018 15:15:38 UTC+2, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Ron,
>>
>> Sorry, I'm still having trouble locating those requests in our logs. 
>> Would you mind sending over the customer ID where your developer token is 
>> registered? You can send it only to me by clicking *Reply privately to 
>> author*.
>>
>> Regarding the timeout theory, the ReportDownloader won't automatically 
>> retry requests. However, if you think timeouts are the root cause here, you 
>> can adjust the timeout for report downloads programmatically or in your 
>> *ads.properties* file. Check out this section of the ads.properties file 
>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
>>  for 
>> details.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> I checked the request data that I provided you and they are exactly what 
>>> I can see in my logs. Maybe I should mention that the provided time is the 
>>> time at which the request failed not when it was sent to your servers (that 
>>> time is ~30-40 seconds before).
>>>
>>> Concerning the thread-safety recommendations I'm sure that the 
>>> ReportDownloader and its Session are not used in multiple threads in our 
>>> code.
>>>
>>> Further information: 
>>> Checking our errors I found an interesting pattern, failing requests 
>>> always take at least 30 seconds (usually 30-31) while successful ones are 
>>> most likely to be around 1 second.
>>>
>>> Maybe a stupid thought but could it be a something like the java-library 
>>> timing out after 30 seconds and retrying using the provided 
>>> session/ReportDownloader again which then violates the threadSafety and 
>>> results in invalid requests?
>>>
>>> Best Regards,
>>> Ron
>>>
>>>
>>> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Ronald,
>>>>
>>>> I searched the logs on our side and could not find either of those 
>>>> requests. Are you sure that they were submitted for the account ID you 
>>>> mentioned?
>>>>
>>>> By the way, did you check if you're adhering to the thread safety 
>>>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>>>> out as a possible cause of the errors.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>>>>
>>>>> Hi Josh,
>>>>>
>>>>> thx for the hints.
>>>>> Concerning the requested information I can give you 2 identical 
>>>>> request where one succeeded and the other one failed with a 400 as shown 
>>>>> in 
>>>>> my last message.
>>>>>
>>>>> failed:
>>>>> time: 27.03.18 01:06:08 CEST
>>>>> googleAdwordsAccountId: 685-366-2732
>>>>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>>>>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>>>>
>>>>> succeeded:
>>>>> time: 27.03.18 03:06:30 CEST
>>>>> googleAdwordsAccountId: 685-366-2732
>>>>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>>&g

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron,

Sorry, I'm still having trouble locating those requests in our logs. Would 
you mind sending over the customer ID where your developer token is 
registered? You can send it only to me by clicking *Reply privately to 
author*.

Regarding the timeout theory, the ReportDownloader won't automatically 
retry requests. However, if you think timeouts are the root cause here, you 
can adjust the timeout for report downloads programmatically or in your 
*ads.properties* file. Check out this section of the ads.properties file 
<https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/ads.properties#L47>
 for 
details.

Thanks,
Josh, AdWords API Team

On Wednesday, March 28, 2018 at 8:10:33 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> I checked the request data that I provided you and they are exactly what I 
> can see in my logs. Maybe I should mention that the provided time is the 
> time at which the request failed not when it was sent to your servers (that 
> time is ~30-40 seconds before).
>
> Concerning the thread-safety recommendations I'm sure that the 
> ReportDownloader and its Session are not used in multiple threads in our 
> code.
>
> Further information: 
> Checking our errors I found an interesting pattern, failing requests 
> always take at least 30 seconds (usually 30-31) while successful ones are 
> most likely to be around 1 second.
>
> Maybe a stupid thought but could it be a something like the java-library 
> timing out after 30 seconds and retrying using the provided 
> session/ReportDownloader again which then violates the threadSafety and 
> results in invalid requests?
>
> Best Regards,
> Ron
>
>
> Am Dienstag, 27. März 2018 23:05:31 UTC+2 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Ronald,
>>
>> I searched the logs on our side and could not find either of those 
>> requests. Are you sure that they were submitted for the account ID you 
>> mentioned?
>>
>> By the way, did you check if you're adhering to the thread safety 
>> guidelines I mentioned earlier? I just want to make sure we can rule that 
>> out as a possible cause of the errors.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>>>
>>> Hi Josh,
>>>
>>> thx for the hints.
>>> Concerning the requested information I can give you 2 identical request 
>>> where one succeeded and the other one failed with a 400 as shown in my last 
>>> message.
>>>
>>> failed:
>>> time: 27.03.18 01:06:08 CEST
>>> googleAdwordsAccountId: 685-366-2732
>>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>>
>>> succeeded:
>>> time: 27.03.18 03:06:30 CEST
>>> googleAdwordsAccountId: 685-366-2732
>>> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT 
>>> WHERE CountryCriteriaId = 2826 DURING 20180225,20180327;
>>>
>>> Best Regards, Ron
>>>
>>> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Raneen,
>>>>
>>>> From our logs, it appears that your requests are most frequently 
>>>> failing with the following errors:
>>>>
>>>>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>>>>- AuthorizationError.USER_PERMISSION_DENIED
>>>>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>>>>
>>>> Could you share a report request that failed, with any sensitive 
>>>> information removed (developer token, OAuth access token, etc.)?
>>>>
>>>> Also, I see that you are using the client library for Java. Are you 
>>>> adhering to the thread-safety recommendations 
>>>> <https://github.com/googleads/googleads-java-lib/wiki/Thread-Safety>? 
>>>> For example, you should not use a *ReportDownloader* instance within 
>>>> multiple threads. Doing so will produce unpredictable behavior, such as 
>>>> malformed requests or issues parsing responses.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
>>>> (AdWords API Team) wrote:
>>>>>
>>>>> Hi Ron, 
>>>>>
>>>>> The V201702 version of the API is deprecated and all calls made to 
>>>>

Re: CrmBasedUserList removeAllStatus not changing from IN_PROCESS

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The status for the remove all step and the upload step are maintained 
separately in removeAllStatus 

 and uploadStatus 
,
 
respectively. The two steps will operate in parallel, so in the example 
below, user3 will only be in the list once *uploadStatus* is *SUCCESS*, and 
user1 and user2 will be removed once the *removeAllStatus* is *SUCCESS*.

The remove all operation will only remove members added before the remove 
all operation was submitted. 

Cheers,
Josh, AdWords API Team

On Tuesday, March 27, 2018 at 10:28:49 PM UTC-4, lj...@chewy.com wrote:
>
>
> Can someone answer his second question here? 
>
> While the removeAllStatus is `IN_PROGRESS` is it still possible to update 
> the list? Or do one need to wait until this status has changed? To 
> exemplify:
>
> List contains:
> user1
> user2
>
> removeAll operand used
> user3 is added to the list while removeAllStatus is `IN_PROGRESS`
>
> when both uploadStatus and removeAllStatus changes to `SUCCESS` will the 
> list be empty or will user3 be in the list?
>
>
>
> On Thursday, July 13, 2017 at 4:33:21 AM UTC-4, Olof Nilsson wrote:
>>
>> Hi,
>>
>> I have an issue with clearing a UserList using the removeAll flag.
>>
>> Basically the flow we thought of using to update a list is:
>>
>> 1) remove all
>> 2) add members
>>
>> and repeat this with some iteration frequency. From what I've read I 
>> thought it would take at most 24 hours for an action to complete. But when 
>> testing this on a list (id: 486851326) the removeAllStatus has been 
>> `IN_PROGRESS` now for 48 hours. The list isn't even that big roughly 7k 
>> entries were pushed. do you know what may be causing this?
>>
>> Another question that I have is: while the removeAllStatus is 
>> `IN_PROGRESS` is it still possible to update the list? Or do one need to 
>> wait until this status has changed? To exemplify:
>>
>> List contains:
>> user1
>> user2
>>
>> removeAll operand used
>> user3 is added to the list while removeAllStatus is `IN_PROGRESS`
>>
>> when both uploadStatus and removeAllStatus changes to `SUCCESS` will the 
>> list be empty or will user3 be in the list?
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7b49daff-5e9b-4029-865f-2113f60344b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ronald,

I searched the logs on our side and could not find either of those 
requests. Are you sure that they were submitted for the account ID you 
mentioned?

By the way, did you check if you're adhering to the thread safety 
guidelines I mentioned earlier? I just want to make sure we can rule that 
out as a possible cause of the errors.

Thanks,
Josh, AdWords API Team

On Tuesday, March 27, 2018 at 9:53:11 AM UTC-4, Ronald Findling wrote:
>
> Hi Josh,
>
> thx for the hints.
> Concerning the requested information I can give you 2 identical request 
> where one succeeded and the other one failed with a 400 as shown in my last 
> message.
>
> failed:
> time: 27.03.18 01:06:08 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
> CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> succeeded:
> time: 27.03.18 03:06:30 CEST
> googleAdwordsAccountId: 685-366-2732
> SELECT Conversions,ConversionValue FROM SHOPPING_PERFORMANCE_REPORT WHERE 
> CountryCriteriaId = 2826 DURING 20180225,20180327;
>
> Best Regards, Ron
>
> Am Dienstag, 20. März 2018 21:54:13 UTC+1 schrieb Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Raneen,
>>
>> From our logs, it appears that your requests are most frequently failing 
>> with the following errors:
>>
>>- ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
>>- AuthorizationError.USER_PERMISSION_DENIED
>>- ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
>>
>> Could you share a report request that failed, with any sensitive 
>> information removed (developer token, OAuth access token, etc.)?
>>
>> Also, I see that you are using the client library for Java. Are you 
>> adhering to the thread-safety recommendations 
>> <https://github.com/googleads/googleads-java-lib/wiki/Thread-Safety>? 
>> For example, you should not use a *ReportDownloader* instance within 
>> multiple threads. Doing so will produce unpredictable behavior, such as 
>> malformed requests or issues parsing responses.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
>> (AdWords API Team) wrote:
>>>
>>> Hi Ron, 
>>>
>>> The V201702 version of the API is deprecated and all calls made to this 
>>> version of the API will return an error. v201802 
>>> <https://googleadsdeveloper.blogspot.com/2018/02/announcing-v201802-of-adwords-api.html>
>>>  is 
>>> the most recent version of the API currently available. We strongly 
>>> recommend that you migrate to this version. For future reference, please 
>>> find the deprecation schedule 
>>> <https://developers.google.com/adwords/api/docs/sunset-dates> for 
>>> various API versions. The resources given below might be helpful for you in 
>>> migration: 
>>>
>>>- v201802 migration guide 
>>><https://developers.google.com/adwords/api/docs/guides/migration/v201802>
>>>- v201710 migration guide 
>>><https://developers.google.com/adwords/api/docs/guides/migration/v201710>
>>>- v201708 migration guide 
>>>
>>> <https://developers.google.com/adwords/api/docs/guides/migration/v201708> 
>>> (useful 
>>>if you are migrating from v201705)
>>>- Release notes 
>>><https://developers.google.com/adwords/api/docs/reference/>
>>>
>>> You could follow our Google Ads Developer blog 
>>> <https://googleadsdeveloper.blogspot.com/search/label/adwords_api> or 
>>> the AdWords API Announcements forum 
>>> <https://groups.google.com/forum/#!forum/adwordsapi-announcements> to 
>>> make sure that you are not missing any announcements about the API in the 
>>> future. Please let me know if you have any further questions. 
>>>
>>> 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/b744e7f7-addf-4147-a185-6688e9ea9a12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: API migration, detect requests source

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Nicolò,

I just checked requests for the developer token you sent to Dhanya, and I 
still see v201708 reporting and TargetingIdeaService requests as recently 
as yesterday.

Thanks,
Josh, AdWords API Team

On Wednesday, March 21, 2018 at 12:08:52 PM UTC-4, Dhanya Sundararaju 
(AdWords API Team) wrote:
>
> Hi Nicolò,
>
> Yes, thanks for the information. I will update you as soon as we find out.
>
> 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/f03d5e1a-6470-428b-818d-bdbd64f94026%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Ron, Raneen,

In my previous post, I mistakenly said that the list of errors I provided 
was for Raneen, but I just realized that they were actually for you, Ron. 
Sorry about that!

*Ron*, could you check out my previous post and the questions/items I 
highlighted there?

Thanks,
Josh, AdWords API Team

On Wednesday, March 21, 2018 at 6:18:17 AM UTC-4, Ronald Findling wrote:
>
> Hi Sreelakshmi,
> sorry, I somehow mixed up versions here -- we are actually using `
> com.google.api.ads.adwords.axis.v201710`
>
>
> Am Dienstag, 20. März 2018 20:06:14 UTC+1 schrieb Sreelakshmi Sasidharan 
> (AdWords API Team):
>>
>> Hi Ron, 
>>
>> The V201702 version of the API is deprecated and all calls made to this 
>> version of the API will return an error. v201802 
>> 
>>  is 
>> the most recent version of the API currently available. We strongly 
>> recommend that you migrate to this version. For future reference, please 
>> find the deprecation schedule 
>>  for 
>> various API versions. The resources given below might be helpful for you in 
>> migration: 
>>
>>- v201802 migration guide 
>>
>>- v201710 migration guide 
>>
>>- v201708 migration guide 
>> 
>> (useful 
>>if you are migrating from v201705)
>>- Release notes 
>>
>>
>> You could follow our Google Ads Developer blog 
>>  or 
>> the AdWords API Announcements forum 
>>  to 
>> make sure that you are not missing any announcements about the API in the 
>> future. Please let me know if you have any further questions. 
>>
>> 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/c7249dd2-b47b-49fb-8af9-61d99595ee89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: throwing DetailedReportDownloadResponseException with 400 Response code.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Raneen,

>From our logs, it appears that your requests are most frequently failing 
with the following errors:

   - ReportDefinitionError.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH
   - AuthorizationError.USER_PERMISSION_DENIED
   - ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT
   
Could you share a report request that failed, with any sensitive 
information removed (developer token, OAuth access token, etc.)?

Also, I see that you are using the client library for Java. Are you 
adhering to the thread-safety recommendations 
? For 
example, you should not use a *ReportDownloader* instance within multiple 
threads. Doing so will produce unpredictable behavior, such as malformed 
requests or issues parsing responses.

Thanks,
Josh, AdWords API Team

On Tuesday, March 20, 2018 at 3:06:14 PM UTC-4, Sreelakshmi Sasidharan 
(AdWords API Team) wrote:
>
> Hi Ron, 
>
> The V201702 version of the API is deprecated and all calls made to this 
> version of the API will return an error. v201802 
> 
>  is 
> the most recent version of the API currently available. We strongly 
> recommend that you migrate to this version. For future reference, please 
> find the deprecation schedule 
>  for various 
> API versions. The resources given below might be helpful for you in 
> migration: 
>
>- v201802 migration guide 
>
>- v201710 migration guide 
>
>- v201708 migration guide 
> 
> (useful 
>if you are migrating from v201705)
>- Release notes 
>
>
> You could follow our Google Ads Developer blog 
>  or the 
> AdWords 
> API Announcements forum 
>  to 
> make sure that you are not missing any announcements about the API in the 
> future. Please let me know if you have any further questions. 
>
> 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/5a8332ee-7ba4-4ad1-9664-236e3bfaff35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Creating negative keyword in manager account using SharedSetService - validating migration from 201705 to 201802

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Matt,

Your theory sounds right to me. Prior to v201710, the AdWords API prevented 
users from creating a shared set in a manager account because the AdWords 
API did not perform some additional internal steps required for 
manager-level sets. At that time, the workaround was to create the 
manager-level set in the UI, after which you could maintain the *contents* of 
the manager-level set (negative keywords) using the AdWords API without 
issues. Starting with v201710, the AdWords API was updated to perform those 
additional internal steps, hence the expected difference in behavior 
between v201708 and v201710.

I'm still waiting on a response on the validation change you mentioned. 
I'll let you know as soon as I get that.

Cheers,
Josh, AdWords API Team

On Monday, March 19, 2018 at 5:42:54 PM UTC-4, Matthew Wawrin wrote:
>
> Thanks Josh.  
>
> Likely I created the manager level negative keyword list in the UI, then 
> populated it through the API.  We started using the manager negative 
> keyword list in May 2017.   By the sounds of it we may not have been able 
> to create it through the API itself until 201710?  Once created and 
> populated we managed the contents of the list and create CampaignSharedSet 
> links when creating new campaigns.  Also sounds like support for shared 
> lists are expanding in the API rather than being reduced which is very 
> encouraging.  We will be making use of negative placements at the manager 
> level in the future I'm sure. 
>
> Cheeris,
> Matt.
>
> On Monday, March 19, 2018 at 3:43:30 PM UTC-5, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Matt,
>>
>> I'll definitely get back to you once I have more info on the change you 
>> mentioned. However, I'd recommend holding off on abandoning manager-level 
>> shared sets. In fact, the v201710 release added support for 
>> manager-level shared sets 
>> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201710#shared_sets>,
>>  
>> so if you're already using them, I see no reason to change course.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, March 19, 2018 at 2:08:29 PM UTC-4, Matthew Wawrin wrote:
>>>
>>> Hi Josh, 
>>>
>>> Thank you for following up.  I look forward to hearing more details when 
>>> available.   I'm going to proceed with our API level update tomorrow and 
>>> get some code ready as a  contingency if we're no longer able to use the 
>>> MCC's neg. keyword shared set  for a managed customer account's 
>>> CampaignSharedSet.  We already maintain negative placements in each managed 
>>> customer account, so moving neg. keywords to this level won't be a huge 
>>> issue.  I liked being able to maintain these lists at the highest level and 
>>> reduce the duplication as much as possible.
>>>
>>> Cheers,
>>> Matt.
>>>
>>> On Monday, March 19, 2018 at 8:25:40 AM UTC-5, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi Matt,
>>>>
>>>> You've uncovered a mystery! :) I just confirmed that the validation did 
>>>> indeed change recently, but I'm not sure why. I'm following up with the 
>>>> engineer who made the change and will get back to you. Thanks for catching 
>>>> this and reporting it to us!
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Friday, March 16, 2018 at 1:06:53 PM UTC-4, Matthew Wawrin wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm working through the validation of our code base (PHP) from 201705 
>>>>> to 201802, and I noticed a change in the 201708 migration guide regarding 
>>>>> the SharedSetService mutate regarding creating shared set of Negative 
>>>>> keywords in a manager account:
>>>>>
>>>>> From 
>>>>> https://developers.google.com/adwords/api/docs/guides/migration/v201708
>>>>> : 
>>>>>
>>>>> *Requests that attempt to create a shared set 
>>>>> of NEGATIVE_KEYWORDS type 
>>>>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSet#type>
>>>>>  in 
>>>>> a manager account will now fail with a SharedSetError 
>>>>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSetError>
>>>>>  of MANAGER_CUSTOMER_CANNOT_CREATE_SHARED_SET_OF_THIS_TYPE. 
>>>>> This change does not impact client  (non-manager) accounts.*
>>>&g

Re: Creating negative keyword in manager account using SharedSetService - validating migration from 201705 to 201802

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Matt,

I'll definitely get back to you once I have more info on the change you 
mentioned. However, I'd recommend holding off on abandoning manager-level 
shared sets. In fact, the v201710 release added support for manager-level 
shared sets 
<https://developers.google.com/adwords/api/docs/reference/release-notes/v201710#shared_sets>,
 
so if you're already using them, I see no reason to change course.

Thanks,
Josh, AdWords API Team

On Monday, March 19, 2018 at 2:08:29 PM UTC-4, Matthew Wawrin wrote:
>
> Hi Josh, 
>
> Thank you for following up.  I look forward to hearing more details when 
> available.   I'm going to proceed with our API level update tomorrow and 
> get some code ready as a  contingency if we're no longer able to use the 
> MCC's neg. keyword shared set  for a managed customer account's 
> CampaignSharedSet.  We already maintain negative placements in each managed 
> customer account, so moving neg. keywords to this level won't be a huge 
> issue.  I liked being able to maintain these lists at the highest level and 
> reduce the duplication as much as possible.
>
> Cheers,
> Matt.
>
> On Monday, March 19, 2018 at 8:25:40 AM UTC-5, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Matt,
>>
>> You've uncovered a mystery! :) I just confirmed that the validation did 
>> indeed change recently, but I'm not sure why. I'm following up with the 
>> engineer who made the change and will get back to you. Thanks for catching 
>> this and reporting it to us!
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Friday, March 16, 2018 at 1:06:53 PM UTC-4, Matthew Wawrin wrote:
>>>
>>> Hi,
>>>
>>> I'm working through the validation of our code base (PHP) from 201705 to 
>>> 201802, and I noticed a change in the 201708 migration guide regarding the 
>>> SharedSetService mutate regarding creating shared set of Negative keywords 
>>> in a manager account:
>>>
>>> From 
>>> https://developers.google.com/adwords/api/docs/guides/migration/v201708
>>> : 
>>>
>>> *Requests that attempt to create a shared set of NEGATIVE_KEYWORDS type 
>>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSet#type>
>>>  in 
>>> a manager account will now fail with a SharedSetError 
>>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSetError>
>>>  of MANAGER_CUSTOMER_CANNOT_CREATE_SHARED_SET_OF_THIS_TYPE. 
>>> This change does not impact client  (non-manager) accounts.*
>>>
>>>
>>>  We manage a large number of sub-accounts under our manager, and all 
>>> campaigns in those sub-accounts use the same base negative keyword shared 
>>> in the manager account.   Currently there are > 19K campaigns linked to the 
>>> manager level negative keyword list.  
>>>
>>> In both our production MCC and test manager account I'm still able to 
>>> create a Negative Keyword shared set using the 201802 API level which 
>>> contradicts the change in 201708.  In my test manager I'm able to create a 
>>> campaign shared set association with the shared set that was created.
>>>
>>> I'd like to understand the impact of this change so I can properly 
>>> update our operations and code to the latest level.   Does the API enforce 
>>> the change in 201708 in a way that I'm overlooking?  
>>> To be honest I haven't tried using the 201708 API level to see if the 
>>> behaviour changed after, but the subsequent migration logs don't appear to 
>>> call out this change.
>>>
>>> Unrelated to the API, Are manager level negative keywords being phased 
>>> out in general (not limited to the API) and we should migrate to the client 
>>> customer accounts.  I can follow up on the Adwords users forum for this 
>>> question but I suspect the API would have to reflect this too.
>>>
>>> I plan to push the code to move up early next week, giving me a week or 
>>> so until the switch over to handle any issues.
>>>
>>> Thank you,
>>> Matt.
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

Re: Creating negative keyword in manager account using SharedSetService - validating migration from 201705 to 201802

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Matt,

You've uncovered a mystery! :) I just confirmed that the validation did 
indeed change recently, but I'm not sure why. I'm following up with the 
engineer who made the change and will get back to you. Thanks for catching 
this and reporting it to us!

Cheers,
Josh, AdWords API Team

On Friday, March 16, 2018 at 1:06:53 PM UTC-4, Matthew Wawrin wrote:
>
> Hi,
>
> I'm working through the validation of our code base (PHP) from 201705 to 
> 201802, and I noticed a change in the 201708 migration guide regarding the 
> SharedSetService mutate regarding creating shared set of Negative keywords 
> in a manager account:
>
> From 
> https://developers.google.com/adwords/api/docs/guides/migration/v201708: 
>
> *Requests that attempt to create a shared set of NEGATIVE_KEYWORDS type 
> 
>  in 
> a manager account will now fail with a SharedSetError 
> 
>  of MANAGER_CUSTOMER_CANNOT_CREATE_SHARED_SET_OF_THIS_TYPE. 
> This change does not impact client  (non-manager) accounts.*
>
>
>  We manage a large number of sub-accounts under our manager, and all 
> campaigns in those sub-accounts use the same base negative keyword shared 
> in the manager account.   Currently there are > 19K campaigns linked to the 
> manager level negative keyword list.  
>
> In both our production MCC and test manager account I'm still able to 
> create a Negative Keyword shared set using the 201802 API level which 
> contradicts the change in 201708.  In my test manager I'm able to create a 
> campaign shared set association with the shared set that was created.
>
> I'd like to understand the impact of this change so I can properly update 
> our operations and code to the latest level.   Does the API enforce the 
> change in 201708 in a way that I'm overlooking?  
> To be honest I haven't tried using the 201708 API level to see if the 
> behaviour changed after, but the subsequent migration logs don't appear to 
> call out this change.
>
> Unrelated to the API, Are manager level negative keywords being phased out 
> in general (not limited to the API) and we should migrate to the client 
> customer accounts.  I can follow up on the Adwords users forum for this 
> question but I suspect the API would have to reflect this too.
>
> I plan to push the code to move up early next week, giving me a week or so 
> until the switch over to handle any issues.
>
> Thank you,
> Matt.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/94b90218-a626-42ac-ab31-359c04007195%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The Gradle Maven Plugin 
<https://docs.gradle.org/current/userguide/maven_plugin.html> will generate 
a pom.xml for your project based on your Gradle configuration. Could you 
give that a try?

Another option is to use a Gradle plugin for Eclipse, such as Eclipse 
Buildship <https://projects.eclipse.org/projects/tools.buildship>.

Thanks,
Josh, AdWords API Team

On Tuesday, March 13, 2018 at 3:58:56 AM UTC-4, goldenmaza wrote:
>
> Hi Josh
>
> I tried both, no change. I'm trying to configure Eclipse to use my old 
> project files but the problems with dependencies are even worse in this
> environment. There is no convert project from Gradle/Android to 
> Maven/Eclipse functionality in Eclipse?
>
> Kind regards
> Richard
>
> Den måndag 12 mars 2018 kl. 17:37:46 UTC+1 skrev Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Richard,
>>
>> Could you try removing the line for *adwords-axis*? The idea is that 
>> you'll either use *adwords-axis* *or** adwords-appengine*, but not both.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, March 12, 2018 at 3:52:24 AM UTC-4, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> By having the following in the build.gradle file:
>>>
>>> implementation 'com.google.api-ads:ads-lib:3.12.0'
>>> implementation 'com.google.api-ads:adwords-axis:3.12.0'
>>> implementation 'com.google.api-ads:adwords-appengine:3.12.0'
>>>
>>> I get the classpath errors:
>>>
>>> Error:Unable to resolve dependency for ':app@release/compileClasspath': 
>>> Could not resolve com.google.api-ads:adwords-appengine:3.12.0.
>>>
>>> I even have the *adwords-appengine-3.12.0.jar* file under the app/libs 
>>> folder...
>>>
>>> I have even invalided cache and done a restart, no luck...
>>>
>>> I miss the day of front-end development where I didn't have these 
>>> problems...
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den fredag 9 mars 2018 kl. 16:42:08 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> The RMI package is needed because the objects generated for the Axis 
>>>> SOAP toolkit are all based on that package. For example, *ApiException* 
>>>> in the library ultimately extends *java.rmi.RemoteException* via the 
>>>> inheritance hierarchy of *ApiException -> ApplicationException -> 
>>>> AxisFault -> RemoteException*.
>>>>
>>>> One thing you could try would be to use the JAX-WS (AppEngine) modules 
>>>> instead of the Axis modules. Those would be:
>>>>
>>>> 
>>>>   com.google.api-ads
>>>>   ads-lib
>>>>   *RELEASE*
>>>> 
>>>> 
>>>>   com.google.api-ads
>>>>   adwords-appengine
>>>>   *RELEASE*
>>>> 
>>>>
>>>> I suspect you'll run into similar RMI dependencies there, but it's 
>>>> worth a shot. :)
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>>
>>>> On Thursday, March 8, 2018 at 4:39:14 PM UTC-5, goldenmaza wrote:
>>>>>
>>>>> Hi Josh
>>>>>
>>>>> Wonderful, that would set me back alittle...
>>>>>
>>>>> Yes, I'm using Android Studio for my first Android app. It uses not 
>>>>> only Google AdWords API but also Google Maps API. I felt like Android 
>>>>> Studio would
>>>>> be a good starting point. Do I need to get Eclipse with Maven just for 
>>>>> AdWords and develop everything else in Android Studio? Currently, my 
>>>>> problem to make
>>>>> my code run is this ApiException class that seem to need 
>>>>> RemoteException. If there is no default way of getting RMI for Android 
>>>>> Studio, then I don't have
>>>>> much options left.
>>>>>
>>>>> Why is it needed for ApiException with AdWords?
>>>>>
>>>>> Kind regards
>>>>> Richard
>>>>>
>>>>> Den torsdag 8 mars 2018 kl. 15:28:34 UTC+1 skrev Josh Radcliff 
>>>>> (AdWords API Team):
>>>>>>
>>>>>> Hi Richard,
>>>>>>
>>>>>> This StackOverflow post 
>>>>>> <https://stackoverflow.com/questions/12091791/eclipse-cannot-find-java-r

Re: Cannot find AdWords API Center

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

You'll only see the AdWords API Center if your manager account is *not* a 
test manager account. Unfortunately, the only way to determine if the 
account is a test manager account is:

   1. Click on the wrench in the upper right corner
   2. Click on *Return to previous AdWords* in the upper right corner of 
   the menu that pops up
   3. Look for a red banner with *This is a test account!*

If you're still having trouble, please send your customer ID (xxx-xxx-) 
to me by clicking *Reply privately to author* and I'll take a look.

Thanks,
Josh, AdWords API Team

On Wednesday, March 14, 2018 at 5:04:12 AM UTC-4, Ryan wrote:
>
> I'm also not seeing the link to the Adwords API Center in what I'm pretty 
> sure is my manager account. I do see Accounts on the left side, and under 
> my profile where accounts are also listed there's a grey Manager subheading 
> under the account I'm presently logged into.
>
> Any help would be great, thanks!
>
>
> On Tuesday, March 13, 2018 at 7:00:21 AM UTC-7, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Just so I'm clear on the first question, could you explain which issue 
>> you would like a clear solution for? There have been a couple of different 
>> issues discussed in this thread.
>>
>> To check if you email is a manager account, you have a few options:
>>
>>1. Log into adwords.google.com using the email address. If the 
>>account is a manager account, you will see *Accounts* in the list of 
>>pages on the left.
>>2. Issue a CustomerService.getCustomers 
>>
>> <https://developers.google.com/adwords/api/docs/reference/v201802/CustomerService#getcustomers>
>>  request 
>>using OAuth2 credentials for the account, and inspect the 
>> canManageClients 
>>field 
>>
>> <https://developers.google.com/adwords/api/docs/reference/v201802/CustomerService.Customer#canmanageclients>.
>>  
>>If your account is a manager account, *canManageClients* will be 
>>*true*.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, March 12, 2018 at 4:56:39 PM UTC-4, Osa Aimola wrote:
>>>
>>> Going by the number of people with this same issue, this is 
>>> obbbvvviiooouussslly a reoccurring problem and should hint at something 
>>> being wrong with the process.
>>>
>>> I've done several searches for how to get this fixed and it just doesn't 
>>> work. Can you please, break this down into a clear solution?
>>> Also how does one check if their email is a manager account or not? 
>>> because I used the steps and it is just not working.
>>>
>>> On Wednesday, May 7, 2014 at 7:39:45 PM UTC+8, adwordsku...@ksk-media.de 
>>> wrote:
>>>>
>>>> Dear All,
>>>>
>>>> Our company wants to develop a simple tool that generates AdWords 
>>>> reports to send to our customers and exports them to PDF.
>>>>
>>>> Now to use the API, I understand that I need an Developer Token, which 
>>>> I am supposed to find in the MCC Account Settings. But there is no link to 
>>>> the AdWords API center on the page referred to here 
>>>> <https://developers.google.com/adwords/api/docs/signingup?hl=en> (
>>>> https://developers.google.com/adwords/api/docs/signingup?hl=en). As 
>>>> advised I have created a completely new AdWords MCC Account. 
>>>>
>>>> Help would be greatly appreciated.
>>>>
>>>> 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/73304a8b-99a8-49d7-ace5-f6178f328439%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot find AdWords API Center

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Just so I'm clear on the first question, could you explain which issue you 
would like a clear solution for? There have been a couple of different 
issues discussed in this thread.

To check if you email is a manager account, you have a few options:

   1. Log into adwords.google.com using the email address. If the account 
   is a manager account, you will see *Accounts* in the list of pages on 
   the left.
   2. Issue a CustomerService.getCustomers 
   

 request 
   using OAuth2 credentials for the account, and inspect the canManageClients 
   field 
   
.
 
   If your account is a manager account, *canManageClients* will be *true*.

Thanks,
Josh, AdWords API Team

On Monday, March 12, 2018 at 4:56:39 PM UTC-4, Osa Aimola wrote:
>
> Going by the number of people with this same issue, this is 
> obbbvvviiooouussslly a reoccurring problem and should hint at something 
> being wrong with the process.
>
> I've done several searches for how to get this fixed and it just doesn't 
> work. Can you please, break this down into a clear solution?
> Also how does one check if their email is a manager account or not? 
> because I used the steps and it is just not working.
>
> On Wednesday, May 7, 2014 at 7:39:45 PM UTC+8, adwordsku...@ksk-media.de 
> wrote:
>>
>> Dear All,
>>
>> Our company wants to develop a simple tool that generates AdWords reports 
>> to send to our customers and exports them to PDF.
>>
>> Now to use the API, I understand that I need an Developer Token, which I 
>> am supposed to find in the MCC Account Settings. But there is no link to 
>> the AdWords API center on the page referred to here 
>>  (
>> https://developers.google.com/adwords/api/docs/signingup?hl=en). As 
>> advised I have created a completely new AdWords MCC Account. 
>>
>> Help would be greatly appreciated.
>>
>> 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/79a20f63-2808-436a-9854-203e1ba58080%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CustomerService CUSTOMER_NOT_FOUND error

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The engineering team is looking into this in more detail, and I hope to 
have an update soon. I'll post back here once that happens.

Thanks,
Josh, AdWords API Team

On Monday, March 12, 2018 at 8:17:14 AM UTC-4, Oksana Sulyma wrote:
>
> Hi guys, bumping this thread as mentioned issue still exist. We had 
> correspondence in private mode, please let me know if there are any ideas 
> why we might get this error.. Thanks!
>
> On Friday, January 19, 2018 at 6:46:58 PM UTC+2, Bharani Cherukuri 
> (AdWords API Team) wrote:
>>
>> Hello Okasana, 
>>
>> The CUSTOMER_NOT_FOUND 
>> 
>>  error 
>> is received when the ID specified in the request header does not exist. I 
>> see that you're using the CustomerService.getCustomers() 
>> ,
>>  
>> which will return all the customers directly accessible by the user 
>> authenticating the call. If the account specified is a new account, it is 
>> recommended that you wait a few minutes after the account is created before 
>> issuing requests against it. Could you please recheck the credentials used 
>> if they belong to the valid AdWords account user and try the request again? 
>> If you continue to have an issue with this, could you share us the email 
>> address used to authenticate the API call? Please use *Reply privately 
>> to author* option to provide the details. 
>>
>> Regards,
>> Bharani, 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/cbaef09c-f62e-403a-a087-09db7cdfecfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

Could you try removing the line for *adwords-axis*? The idea is that you'll 
either use *adwords-axis* *or** adwords-appengine*, but not both.

Thanks,
Josh, AdWords API Team

On Monday, March 12, 2018 at 3:52:24 AM UTC-4, goldenmaza wrote:
>
> Hi Josh
>
> By having the following in the build.gradle file:
>
> implementation 'com.google.api-ads:ads-lib:3.12.0'
> implementation 'com.google.api-ads:adwords-axis:3.12.0'
> implementation 'com.google.api-ads:adwords-appengine:3.12.0'
>
> I get the classpath errors:
>
> Error:Unable to resolve dependency for ':app@release/compileClasspath': 
> Could not resolve com.google.api-ads:adwords-appengine:3.12.0.
>
> I even have the *adwords-appengine-3.12.0.jar* file under the app/libs 
> folder...
>
> I have even invalided cache and done a restart, no luck...
>
> I miss the day of front-end development where I didn't have these 
> problems...
>
> Kind regards
> Richard
>
> Den fredag 9 mars 2018 kl. 16:42:08 UTC+1 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Richard,
>>
>> The RMI package is needed because the objects generated for the Axis SOAP 
>> toolkit are all based on that package. For example, *ApiException* in 
>> the library ultimately extends *java.rmi.RemoteException* via the 
>> inheritance hierarchy of *ApiException -> ApplicationException -> 
>> AxisFault -> RemoteException*.
>>
>> One thing you could try would be to use the JAX-WS (AppEngine) modules 
>> instead of the Axis modules. Those would be:
>>
>> 
>>   com.google.api-ads
>>   ads-lib
>>   *RELEASE*
>> 
>> 
>>   com.google.api-ads
>>   adwords-appengine
>>   *RELEASE*
>> 
>>
>> I suspect you'll run into similar RMI dependencies there, but it's worth 
>> a shot. :)
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>>
>> On Thursday, March 8, 2018 at 4:39:14 PM UTC-5, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> Wonderful, that would set me back alittle...
>>>
>>> Yes, I'm using Android Studio for my first Android app. It uses not only 
>>> Google AdWords API but also Google Maps API. I felt like Android Studio 
>>> would
>>> be a good starting point. Do I need to get Eclipse with Maven just for 
>>> AdWords and develop everything else in Android Studio? Currently, my 
>>> problem to make
>>> my code run is this ApiException class that seem to need 
>>> RemoteException. If there is no default way of getting RMI for Android 
>>> Studio, then I don't have
>>> much options left.
>>>
>>> Why is it needed for ApiException with AdWords?
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den torsdag 8 mars 2018 kl. 15:28:34 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> This StackOverflow post 
>>>> <https://stackoverflow.com/questions/12091791/eclipse-cannot-find-java-rmi-remote-class>
>>>>  suggests 
>>>> that RMI may not be packaged with Android. Are you developing an Android 
>>>> application, or are you just using Android Developer Studio as your IDE?
>>>>
>>>> Regarding jCenter, you're absolutely correct. :)
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Thursday, March 8, 2018 at 3:23:26 AM UTC-5, goldenmaza wrote:
>>>>>
>>>>> Hi Josh
>>>>>
>>>>> Wasn't jcenter replacing mavenCentral?
>>>>>
>>>>> But why do I still get RemoteException and why is the ApiException 
>>>>> still a problem (underlined red and something about Throwable)?
>>>>>
>>>>> Kind regards
>>>>> Richard
>>>>>
>>>>> Den onsdag 7 mars 2018 kl. 21:26:10 UTC+1 skrev Josh Radcliff (AdWords 
>>>>> API Team):
>>>>>>
>>>>>> Hi Richard,
>>>>>>
>>>>>> My knowledge of Gradle is pretty limited, I'm afraid, but did you try 
>>>>>> adding *mavenCentral()* to your list of *repositories* as shown here 
>>>>>> <https://docs.gradle.org/current/userguide/declaring_dependencies.html#sub:declaring_dependency_with_version>
>>>>>> ?
>>>>>>
>>>>>> Thanks,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> O

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

The RMI package is needed because the objects generated for the Axis SOAP 
toolkit are all based on that package. For example, *ApiException* in the 
library ultimately extends *java.rmi.RemoteException* via the inheritance 
hierarchy of *ApiException -> ApplicationException -> AxisFault -> 
RemoteException*.

One thing you could try would be to use the JAX-WS (AppEngine) modules 
instead of the Axis modules. Those would be:


  com.google.api-ads
  ads-lib
  *RELEASE*


  com.google.api-ads
  adwords-appengine
  *RELEASE*


I suspect you'll run into similar RMI dependencies there, but it's worth a 
shot. :)

Cheers,
Josh, AdWords API Team


On Thursday, March 8, 2018 at 4:39:14 PM UTC-5, goldenmaza wrote:
>
> Hi Josh
>
> Wonderful, that would set me back alittle...
>
> Yes, I'm using Android Studio for my first Android app. It uses not only 
> Google AdWords API but also Google Maps API. I felt like Android Studio 
> would
> be a good starting point. Do I need to get Eclipse with Maven just for 
> AdWords and develop everything else in Android Studio? Currently, my 
> problem to make
> my code run is this ApiException class that seem to need RemoteException. 
> If there is no default way of getting RMI for Android Studio, then I don't 
> have
> much options left.
>
> Why is it needed for ApiException with AdWords?
>
> Kind regards
> Richard
>
> Den torsdag 8 mars 2018 kl. 15:28:34 UTC+1 skrev Josh Radcliff (AdWords 
> API Team):
>>
>> Hi Richard,
>>
>> This StackOverflow post 
>> <https://stackoverflow.com/questions/12091791/eclipse-cannot-find-java-rmi-remote-class>
>>  suggests 
>> that RMI may not be packaged with Android. Are you developing an Android 
>> application, or are you just using Android Developer Studio as your IDE?
>>
>> Regarding jCenter, you're absolutely correct. :)
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, March 8, 2018 at 3:23:26 AM UTC-5, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> Wasn't jcenter replacing mavenCentral?
>>>
>>> But why do I still get RemoteException and why is the ApiException still 
>>> a problem (underlined red and something about Throwable)?
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den onsdag 7 mars 2018 kl. 21:26:10 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> My knowledge of Gradle is pretty limited, I'm afraid, but did you try 
>>>> adding *mavenCentral()* to your list of *repositories* as shown here 
>>>> <https://docs.gradle.org/current/userguide/declaring_dependencies.html#sub:declaring_dependency_with_version>
>>>> ?
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Wednesday, March 7, 2018 at 1:15:57 PM UTC-5, goldenmaza wrote:
>>>>>
>>>>> Hi Josh
>>>>>
>>>>> 1) Yes, it is intentional as I first believed that by placing the jar 
>>>>> files under the libs folder that they would get their respective 
>>>>> classpath 
>>>>> automatically.
>>>>>
>>>>> 2) I've updated the build file as follows:
>>>>>
>>>>> implementation 'com.google.api-ads:ads-lib:3.12.0'
>>>>> implementation 'com.google.api-ads:adwords-axis:3.12.0'
>>>>>
>>>>> I still have the RemoteException problem..
>>>>>
>>>>> Kind regards
>>>>> Richard
>>>>>
>>>>> Den onsdag 7 mars 2018 kl. 15:10:42 UTC+1 skrev Josh Radcliff (AdWords 
>>>>> API Team):
>>>>>>
>>>>>> Hi Richard,
>>>>>>
>>>>>> Thanks for sending over that info. I noticed two things about your 
>>>>>> *dependencies* section:
>>>>>>
>>>>>> 1. The dependencies for the Google Ads APIs Client Library for Java 
>>>>>> are commented out:
>>>>>>
>>>>>> //implementation 'com.google.api-ads:ads-lib:3.10.0'
>>>>>> //implementation 'com.google.api-ads:adwords-axis:1.38.0'
>>>>>>
>>>>>> Was that intentional, and was that the state of the config when you 
>>>>>> tried to run the example? With those two lines commented out, none of 
>>>>>> the 
>>>>>> library's classes will be on the classpath.
>>&g

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

This StackOverflow post 
<https://stackoverflow.com/questions/12091791/eclipse-cannot-find-java-rmi-remote-class>
 suggests 
that RMI may not be packaged with Android. Are you developing an Android 
application, or are you just using Android Developer Studio as your IDE?

Regarding jCenter, you're absolutely correct. :)

Thanks,
Josh, AdWords API Team

On Thursday, March 8, 2018 at 3:23:26 AM UTC-5, goldenmaza wrote:
>
> Hi Josh
>
> Wasn't jcenter replacing mavenCentral?
>
> But why do I still get RemoteException and why is the ApiException still a 
> problem (underlined red and something about Throwable)?
>
> Kind regards
> Richard
>
> Den onsdag 7 mars 2018 kl. 21:26:10 UTC+1 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Richard,
>>
>> My knowledge of Gradle is pretty limited, I'm afraid, but did you try 
>> adding *mavenCentral()* to your list of *repositories* as shown here 
>> <https://docs.gradle.org/current/userguide/declaring_dependencies.html#sub:declaring_dependency_with_version>
>> ?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 7, 2018 at 1:15:57 PM UTC-5, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> 1) Yes, it is intentional as I first believed that by placing the jar 
>>> files under the libs folder that they would get their respective classpath 
>>> automatically.
>>>
>>> 2) I've updated the build file as follows:
>>>
>>> implementation 'com.google.api-ads:ads-lib:3.12.0'
>>> implementation 'com.google.api-ads:adwords-axis:3.12.0'
>>>
>>> I still have the RemoteException problem..
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den onsdag 7 mars 2018 kl. 15:10:42 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> Thanks for sending over that info. I noticed two things about your 
>>>> *dependencies* section:
>>>>
>>>> 1. The dependencies for the Google Ads APIs Client Library for Java are 
>>>> commented out:
>>>>
>>>> //implementation 'com.google.api-ads:ads-lib:3.10.0'
>>>> //implementation 'com.google.api-ads:adwords-axis:1.38.0'
>>>>
>>>> Was that intentional, and was that the state of the config when you 
>>>> tried to run the example? With those two lines commented out, none of the 
>>>> library's classes will be on the classpath.
>>>>
>>>> 2. The versions specified for the two Google Ads APIs Client Library 
>>>> for Java do not match. For example, if you're using *3.10.0* for 
>>>> *ads-lib*, you should also use *3.10.0* for *adwords-axis*. Although 
>>>> Maven requires separate versions for each dependency, in practice we 
>>>> always 
>>>> keep all of our Maven artifacts on the same version. The latest version 
>>>> for 
>>>> the library is 3.12.0 
>>>> <https://github.com/googleads/googleads-java-lib/releases>.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Wednesday, March 7, 2018 at 3:07:15 AM UTC-5, goldenmaza wrote:
>>>>>
>>>>> Hi Josh
>>>>>
>>>>> According to the controlpanel I have Java 8 Update 162.
>>>>>
>>>>> build.gradle under app folder:
>>>>> apply plugin: 'com.android.application'
>>>>>
>>>>> android {
>>>>> compileSdkVersion 26
>>>>> buildToolsVersion "26.0.2"
>>>>> defaultConfig {
>>>>> applicationId "yada.yada"
>>>>> minSdkVersion 23
>>>>> targetSdkVersion 26
>>>>> versionCode 1
>>>>> versionName "1.0"
>>>>> testInstrumentationRunner 
>>>>> "android.support.test.runner.AndroidJUnitRunner"
>>>>> }
>>>>> buildTypes {
>>>>> debug {
>>>>> minifyEnabled false
>>>>> proguardFiles getDefaultProguardFile(
>>>>> 'proguard-android.txt'), 'proguard-rules.pro'
>>>>>     }
>>>>> release {
>>>>> minifyEnabled false
>>>>> proguardFiles getDefaultProguardFile(
>>>>> 'proguard-android.txt'), 'proguard-rules.pro'
>>>>> 

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

My knowledge of Gradle is pretty limited, I'm afraid, but did you try 
adding *mavenCentral()* to your list of *repositories* as shown here 
<https://docs.gradle.org/current/userguide/declaring_dependencies.html#sub:declaring_dependency_with_version>
?

Thanks,
Josh, AdWords API Team

On Wednesday, March 7, 2018 at 1:15:57 PM UTC-5, goldenmaza wrote:
>
> Hi Josh
>
> 1) Yes, it is intentional as I first believed that by placing the jar 
> files under the libs folder that they would get their respective classpath 
> automatically.
>
> 2) I've updated the build file as follows:
>
> implementation 'com.google.api-ads:ads-lib:3.12.0'
> implementation 'com.google.api-ads:adwords-axis:3.12.0'
>
> I still have the RemoteException problem..
>
> Kind regards
> Richard
>
> Den onsdag 7 mars 2018 kl. 15:10:42 UTC+1 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Richard,
>>
>> Thanks for sending over that info. I noticed two things about your 
>> *dependencies* section:
>>
>> 1. The dependencies for the Google Ads APIs Client Library for Java are 
>> commented out:
>>
>> //implementation 'com.google.api-ads:ads-lib:3.10.0'
>> //implementation 'com.google.api-ads:adwords-axis:1.38.0'
>>
>> Was that intentional, and was that the state of the config when you tried 
>> to run the example? With those two lines commented out, none of the 
>> library's classes will be on the classpath.
>>
>> 2. The versions specified for the two Google Ads APIs Client Library for 
>> Java do not match. For example, if you're using *3.10.0* for *ads-lib*, 
>> you should also use *3.10.0* for *adwords-axis*. Although Maven requires 
>> separate versions for each dependency, in practice we always keep all of 
>> our Maven artifacts on the same version. The latest version for the library 
>> is 3.12.0 <https://github.com/googleads/googleads-java-lib/releases>.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Wednesday, March 7, 2018 at 3:07:15 AM UTC-5, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> According to the controlpanel I have Java 8 Update 162.
>>>
>>> build.gradle under app folder:
>>> apply plugin: 'com.android.application'
>>>
>>> android {
>>> compileSdkVersion 26
>>> buildToolsVersion "26.0.2"
>>> defaultConfig {
>>> applicationId "yada.yada"
>>> minSdkVersion 23
>>> targetSdkVersion 26
>>> versionCode 1
>>> versionName "1.0"
>>> testInstrumentationRunner 
>>> "android.support.test.runner.AndroidJUnitRunner"
>>> }
>>> buildTypes {
>>> debug {
>>> minifyEnabled false
>>> proguardFiles getDefaultProguardFile('proguard-android.txt'
>>> ), 'proguard-rules.pro'
>>> }
>>> release {
>>> minifyEnabled false
>>> proguardFiles getDefaultProguardFile('proguard-android.txt'
>>> ), 'proguard-rules.pro'
>>> }
>>> }
>>> }
>>>
>>> repositories {
>>> jcenter()
>>> google()
>>> }
>>>
>>>
>>> dependencies {
>>> implementation fileTree(include: ['*.jar'], dir: 'libs')
>>> implementation 'com.android.support:design:26.0.2'
>>> implementation 'com.android.support:appcompat-v7:26.0.2'
>>> implementation 'com.google.android.gms:play-services-maps:11.8.0'
>>> //implementation 'com.google.api-ads:ads-lib:3.10.0'
>>> //implementation 'com.google.api-ads:adwords-axis:1.38.0'
>>> implementation 'com.android.support:appcompat-v7:26.0.2'
>>> implementation 
>>> 'com.android.support.constraint:constraint-layout:1.0.2'
>>> testImplementation 'junit:junit:4.12'
>>> }
>>>
>>> Thank you for your time! :)
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den tisdag 6 mars 2018 kl. 22:36:16 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> Would you mind sharing your Gradle config so I can see how you're 
>>>> bringing in the library dependencies? Also, just to rule certain things 
>>>> out, could you let me know which version of Java you're using?
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>>

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

Thanks for sending over that info. I noticed two things about your 
*dependencies* section:

1. The dependencies for the Google Ads APIs Client Library for Java are 
commented out:

//implementation 'com.google.api-ads:ads-lib:3.10.0'
//implementation 'com.google.api-ads:adwords-axis:1.38.0'

Was that intentional, and was that the state of the config when you tried 
to run the example? With those two lines commented out, none of the 
library's classes will be on the classpath.

2. The versions specified for the two Google Ads APIs Client Library for 
Java do not match. For example, if you're using *3.10.0* for *ads-lib*, you 
should also use *3.10.0* for *adwords-axis*. Although Maven requires 
separate versions for each dependency, in practice we always keep all of 
our Maven artifacts on the same version. The latest version for the library 
is 3.12.0 <https://github.com/googleads/googleads-java-lib/releases>.

Thanks,
Josh, AdWords API Team

On Wednesday, March 7, 2018 at 3:07:15 AM UTC-5, goldenmaza wrote:
>
> Hi Josh
>
> According to the controlpanel I have Java 8 Update 162.
>
> build.gradle under app folder:
> apply plugin: 'com.android.application'
>
> android {
> compileSdkVersion 26
> buildToolsVersion "26.0.2"
> defaultConfig {
> applicationId "yada.yada"
> minSdkVersion 23
> targetSdkVersion 26
> versionCode 1
> versionName "1.0"
> testInstrumentationRunner 
> "android.support.test.runner.AndroidJUnitRunner"
> }
> buildTypes {
> debug {
> minifyEnabled false
> proguardFiles getDefaultProguardFile('proguard-android.txt'), 
> 'proguard-rules.pro'
> }
> release {
> minifyEnabled false
> proguardFiles getDefaultProguardFile('proguard-android.txt'), 
> 'proguard-rules.pro'
> }
> }
> }
>
> repositories {
> jcenter()
> google()
> }
>
>
> dependencies {
> implementation fileTree(include: ['*.jar'], dir: 'libs')
> implementation 'com.android.support:design:26.0.2'
> implementation 'com.android.support:appcompat-v7:26.0.2'
> implementation 'com.google.android.gms:play-services-maps:11.8.0'
> //implementation 'com.google.api-ads:ads-lib:3.10.0'
> //implementation 'com.google.api-ads:adwords-axis:1.38.0'
> implementation 'com.android.support:appcompat-v7:26.0.2'
> implementation 
> 'com.android.support.constraint:constraint-layout:1.0.2'
> testImplementation 'junit:junit:4.12'
> }
>
> Thank you for your time! :)
>
> Kind regards
> Richard
>
> Den tisdag 6 mars 2018 kl. 22:36:16 UTC+1 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Richard,
>>
>> Would you mind sharing your Gradle config so I can see how you're 
>> bringing in the library dependencies? Also, just to rule certain things 
>> out, could you let me know which version of Java you're using?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, March 6, 2018 at 3:26:52 AM UTC-5, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> As I currently sit with Android Studio/Gradle, I would prefer continuing 
>>> using these, I can skip Gradle for the next project but for now I would 
>>> like to learn how to solve this Gradle issue.
>>>
>>> Oh, by placing the files under the libs folder you set the classpath(s) 
>>> manually?
>>>
>>> The part about the archive I have done already (my other forum post with 
>>> Dhanya Sundararaju (AdWords API Team) as he suggested the same). But that 
>>> does not solve the issue I got
>>> as a result of this inclusion of jar files.
>>>
>>> Thank you for your time! :)
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den måndag 5 mars 2018 kl. 17:57:57 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> Thanks - that definitely helps! Could you let me know how you're 
>>>> managing your dependencies? For example, are you using Maven, Gradle, or 
>>>> just setting your classpath manually (e.g., by copying dependencies to a 
>>>> lib folder)?
>>>>
>>>> I ask because the error that java.rmi.RemoteException is not in your 
>>>> classpath indicates that you are missing some key dependencies. If it 
>>>> helps, you can see the list of dependencies to add for Maven here in 
>>>> the README 
>>>> <https://github.com/googleads/googleads-java-lib#maven-art

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

Would you mind sharing your Gradle config so I can see how you're bringing 
in the library dependencies? Also, just to rule certain things out, could 
you let me know which version of Java you're using?

Thanks,
Josh, AdWords API Team

On Tuesday, March 6, 2018 at 3:26:52 AM UTC-5, goldenmaza wrote:
>
> Hi Josh
>
> As I currently sit with Android Studio/Gradle, I would prefer continuing 
> using these, I can skip Gradle for the next project but for now I would 
> like to learn how to solve this Gradle issue.
>
> Oh, by placing the files under the libs folder you set the classpath(s) 
> manually?
>
> The part about the archive I have done already (my other forum post with 
> Dhanya Sundararaju (AdWords API Team) as he suggested the same). But that 
> does not solve the issue I got
> as a result of this inclusion of jar files.
>
> Thank you for your time! :)
>
> Kind regards
> Richard
>
> Den måndag 5 mars 2018 kl. 17:57:57 UTC+1 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Richard,
>>
>> Thanks - that definitely helps! Could you let me know how you're managing 
>> your dependencies? For example, are you using Maven, Gradle, or just 
>> setting your classpath manually (e.g., by copying dependencies to a lib 
>> folder)?
>>
>> I ask because the error that java.rmi.RemoteException is not in your 
>> classpath indicates that you are missing some key dependencies. If it 
>> helps, you can see the list of dependencies to add for Maven here in the 
>> README <https://github.com/googleads/googleads-java-lib#maven-artifacts>. 
>> If you aren't using Maven, you can download the 
>> *adwords-axis-jars-and-examples *archive on the releases page 
>> <https://github.com/googleads/googleads-java-lib/releases>, which 
>> contains a *lib* folder with all required dependencies.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, March 5, 2018 at 9:41:33 AM UTC-5, goldenmaza wrote:
>>>
>>> Hi Josh
>>>
>>> Thank you for your time! :)
>>>
>>> Code and errors are as follows:
>>>
>>> try {
>>> adWordsHandler = new AdWordsHandler(context);
>>> adWordsHandler.callAdWordsAPI();
>>> sales = adWordsHandler.getEntries();
>>> resourceHandler.addResources(Sale.class.getName(), sales);
>>> } catch (RemoteException e) {
>>> e.printStackTrace();
>>> } catch (ApiException e) {
>>> e.printStackTrace();
>>> } catch (Exception e) {
>>> e.printStackTrace();
>>> }
>>>
>>> public void callAdWordsAPI() throws Exception, ApiException {
>>> ...
>>> AdGroupAdPage entries = adService.get(selector);
>>> ...
>>> }
>>>
>>> Error:(104, 9) error: cannot access RemoteException
>>> class file for java.rmi.RemoteException not found
>>>
>>> Error:(61, 52) error: incompatible types: ApiException cannot be 
>>> converted to Throwable
>>>
>>> Error:(89, 46) error: cannot access Remote
>>> class file for java.rmi.Remote not found
>>>
>>> Take care! :)
>>>
>>> Kind regards
>>> Richard
>>>
>>>
>>> Den måndag 5 mars 2018 kl. 15:06:46 UTC+1 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi Richard,
>>>>
>>>> Could you share the error you're getting from the compiler? I want to 
>>>> make sure this is the same issue as mentioned below, so it would be 
>>>> helpful 
>>>> to have more details for your particular case.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Sunday, March 4, 2018 at 5:03:59 PM UTC-5, goldenmaza wrote:
>>>>>
>>>>> Hello Josh
>>>>>
>>>>> I know you answered this a while ago but I have the same problem. I've 
>>>>> read 
>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html
>>>>>  
>>>>> and even if this page explains
>>>>> what a classpath is, it was not written for Google AdWords API. So 
>>>>> what do I need to do regarding this classpath issue? What file(s)? I also 
>>>>> sit with Android Studio.
>>>>>
>>>>> Kind regards
>>>>> Richard
>>>>>
>>>>> Den tisdag 12 maj 2015 kl. 15:47:23 UTC+2 skrev Josh Radcliff (AdWords 
>>>>> API Team):
>>>>>>
>>&g

Re: Error while trying to add a LogicalUserList

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

I'm not much of a Python expert, so please bear with me on formatting and 
style, but the following snippet worked for me:

  rule = {
  'operator': 'ALL',
  'ruleOperands': [
  {
  'UserList': {
  'xsi_type': 'BasicUserList',
  'id': *INSERT_USER_LIST_ID_A_HERE*,
  }
  },
  {
  'UserList': {
  'xsi_type': 'BasicUserList',
  'id': *INSERT_USER_LIST_ID_B_HERE*,
  }
  }
  ]
  }

  # Construct operations and add a user list.
  operations = [
  {
  'operator': 'ADD',
  'operand': {
  'xsi_type': 'LogicalUserList',
  'name': 'Logical #%s' % uuid.uuid4(),
  'description': 'Logical test',
  'rules': [rule],
  }
  }
  ]


Could you give that a try and let me know if you still encounter issues?

Thanks,
Josh, AdWords API Team

On Monday, March 5, 2018 at 9:35:01 AM UTC-5, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> Sorry, I just realized I sent you an example for rule based user lists. 
> I'll look into this and try to provide you with some Python snippets to 
> help.
>
> In the meantime, Damien, if you have a snippet that could help, please 
> share it here.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, March 5, 2018 at 9:00:46 AM UTC-5, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Could you check out the add_rule_based_user_lists.py example 
>> <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201802/remarketing/add_rule_based_user_lists.py>
>>  and 
>> then let me know if that doesn't clear up your question?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, March 2, 2018 at 7:15:13 PM UTC-5, iukhnovy...@gmail.com 
>> wrote:
>>>
>>> hi, what you exactly changed in your pythone code?
>>>
>>> W dniu poniedziałek, 20 lipca 2015 19:50:01 UTC+2 użytkownik Damien 
>>> napisał:
>>>>
>>>> Hi Josh,
>>>>
>>>> Thank you very much, this solved my problem and I've been able to 
>>>> successfully create my LogicalUserList.
>>>>
>>>> Damien
>>>>
>>>> On Monday, July 20, 2015 at 10:24:21 AM UTC-4, Josh Radcliff (AdWords 
>>>> API Team) wrote:
>>>>>
>>>>> Hi Damien,
>>>>>
>>>>> I think the issue here is your ruleOperands 
>>>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdwordsUserListService.UserListLogicalRule#ruleOperands>.
>>>>>  
>>>>> This attribute should be a list of LogicalUserListOperand 
>>>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdwordsUserListService.LogicalUserListOperand>s,
>>>>>  
>>>>> each of which in turn has a *child* UserList element.
>>>>>
>>>>> So instead of:
>>>>>   
>>>>> ALL
>>>>> 
>>>>>   102489659
>>>>>
>>>>> your request should look like:
>>>>>   
>>>>> ALL
>>>>> 
>>>>>   
>>>>> 102489659
>>>>> 
>>>>> Please give that a try and let me know if you run into any other 
>>>>> issues.
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Friday, July 17, 2015 at 2:36:37 PM UTC-4, Damien wrote:
>>>>>>
>>>>>> Hi Josh,
>>>>>>
>>>>>> Here is the Python logger output, you can find the XML request below 
>>>>>> (all sensitive information replaced by "[removed]"):
>>>>>>
>>>>>> DEBUG:suds.transport.http:opening (https://
>>>>>> adwords.google.com/api/adwords/rm/v201502/AdwordsUserListService?wsdl
>>>>>> )
>>>>>> DEBUG:suds.transport.http:sending:
>>>>>> URL: https://
>>>>>> adwords.google.com/api/adwords/rm/v201502/AdwordsUserListService
>>>>>> HEADERS: {'Content-Type': 'text/xml; charset=utf-8', 'Authorization': 
>>>>>> 'Bearer 
>>>>>> [removed]', 'SOAPAction': b'""', 'Content-type': 'text/xml; 
>>>>>> charset=utf-8', 'Soapaction': b'""'}
>>>&g

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

Thanks - that definitely helps! Could you let me know how you're managing 
your dependencies? For example, are you using Maven, Gradle, or just 
setting your classpath manually (e.g., by copying dependencies to a lib 
folder)?

I ask because the error that java.rmi.RemoteException is not in your 
classpath indicates that you are missing some key dependencies. If it 
helps, you can see the list of dependencies to add for Maven here in the 
README <https://github.com/googleads/googleads-java-lib#maven-artifacts>. 
If you aren't using Maven, you can download the 
*adwords-axis-jars-and-examples *archive on the releases page 
<https://github.com/googleads/googleads-java-lib/releases>, which contains 
a *lib* folder with all required dependencies.

Thanks,
Josh, AdWords API Team

On Monday, March 5, 2018 at 9:41:33 AM UTC-5, goldenmaza wrote:
>
> Hi Josh
>
> Thank you for your time! :)
>
> Code and errors are as follows:
>
> try {
> adWordsHandler = new AdWordsHandler(context);
> adWordsHandler.callAdWordsAPI();
> sales = adWordsHandler.getEntries();
> resourceHandler.addResources(Sale.class.getName(), sales);
> } catch (RemoteException e) {
> e.printStackTrace();
> } catch (ApiException e) {
> e.printStackTrace();
> } catch (Exception e) {
> e.printStackTrace();
> }
>
> public void callAdWordsAPI() throws Exception, ApiException {
> ...
> AdGroupAdPage entries = adService.get(selector);
> ...
> }
>
> Error:(104, 9) error: cannot access RemoteException
> class file for java.rmi.RemoteException not found
>
> Error:(61, 52) error: incompatible types: ApiException cannot be 
> converted to Throwable
>
> Error:(89, 46) error: cannot access Remote
> class file for java.rmi.Remote not found
>
> Take care! :)
>
> Kind regards
> Richard
>
>
> Den måndag 5 mars 2018 kl. 15:06:46 UTC+1 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi Richard,
>>
>> Could you share the error you're getting from the compiler? I want to 
>> make sure this is the same issue as mentioned below, so it would be helpful 
>> to have more details for your particular case.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Sunday, March 4, 2018 at 5:03:59 PM UTC-5, goldenmaza wrote:
>>>
>>> Hello Josh
>>>
>>> I know you answered this a while ago but I have the same problem. I've 
>>> read 
>>> https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html
>>>  
>>> and even if this page explains
>>> what a classpath is, it was not written for Google AdWords API. So what 
>>> do I need to do regarding this classpath issue? What file(s)? I also sit 
>>> with Android Studio.
>>>
>>> Kind regards
>>> Richard
>>>
>>> Den tisdag 12 maj 2015 kl. 15:47:23 UTC+2 skrev Josh Radcliff (AdWords 
>>> API Team):
>>>>
>>>> Hi,
>>>>
>>>> That error suggests that your classpath is not configured correctly. 
>>>> Please check out the section of our README on configuring dependencies 
>>>> <https://github.com/googleads/googleads-java-lib#for-using-jars> and 
>>>> let me know if you still have questions.
>>>>
>>>> Thanks,
>>>> Josh, 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/3b32beaa-28fc-42f0-85e3-c36f4e2e50aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error while trying to add a LogicalUserList

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Sorry, I just realized I sent you an example for rule based user lists. 
I'll look into this and try to provide you with some Python snippets to 
help.

In the meantime, Damien, if you have a snippet that could help, please 
share it here.

Thanks,
Josh, AdWords API Team

On Monday, March 5, 2018 at 9:00:46 AM UTC-5, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> Could you check out the add_rule_based_user_lists.py example 
> <https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201802/remarketing/add_rule_based_user_lists.py>
>  and 
> then let me know if that doesn't clear up your question?
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, March 2, 2018 at 7:15:13 PM UTC-5, iukhnovy...@gmail.com wrote:
>>
>> hi, what you exactly changed in your pythone code?
>>
>> W dniu poniedziałek, 20 lipca 2015 19:50:01 UTC+2 użytkownik Damien 
>> napisał:
>>>
>>> Hi Josh,
>>>
>>> Thank you very much, this solved my problem and I've been able to 
>>> successfully create my LogicalUserList.
>>>
>>> Damien
>>>
>>> On Monday, July 20, 2015 at 10:24:21 AM UTC-4, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi Damien,
>>>>
>>>> I think the issue here is your ruleOperands 
>>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdwordsUserListService.UserListLogicalRule#ruleOperands>.
>>>>  
>>>> This attribute should be a list of LogicalUserListOperand 
>>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdwordsUserListService.LogicalUserListOperand>s,
>>>>  
>>>> each of which in turn has a *child* UserList element.
>>>>
>>>> So instead of:
>>>>   
>>>> ALL
>>>> 
>>>>   102489659
>>>>
>>>> your request should look like:
>>>>   
>>>> ALL
>>>> 
>>>>   
>>>> 102489659
>>>> 
>>>> Please give that a try and let me know if you run into any other issues.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Friday, July 17, 2015 at 2:36:37 PM UTC-4, Damien wrote:
>>>>>
>>>>> Hi Josh,
>>>>>
>>>>> Here is the Python logger output, you can find the XML request below 
>>>>> (all sensitive information replaced by "[removed]"):
>>>>>
>>>>> DEBUG:suds.transport.http:opening (https://
>>>>> adwords.google.com/api/adwords/rm/v201502/AdwordsUserListService?wsdl)
>>>>> DEBUG:suds.transport.http:sending:
>>>>> URL: https://
>>>>> adwords.google.com/api/adwords/rm/v201502/AdwordsUserListService
>>>>> HEADERS: {'Content-Type': 'text/xml; charset=utf-8', 'Authorization': 
>>>>> 'Bearer 
>>>>> [removed]', 'SOAPAction': b'""', 'Content-type': 'text/xml; 
>>>>> charset=utf-8', 'Soapaction': b'""'}
>>>>> MESSAGE:
>>>>> b'>>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/; xmlns:tns="
>>>>> https://adwords.google.com/api/adwords/rm/v201502; xmlns:ns2="
>>>>> https://adwords.google.com/api/adwords/cm/v201502; xmlns:ns0="
>>>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>>>>> https://adwords.google.com/api/adwords/rm/v201502; xmlns:xsi="
>>>>> http://www.w3.org/2001/XMLSchema-instance;>>>>>  
>>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>[removed]>>>>  
>>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>[removed]>>>>  
>>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>[removed] 
>>>>> (AwApi-Python, googleads/3.5.0, 
>>>>> Python/3.4.3)https://adwords.google.com/api/adwords/cm/v201502;>false>>>>  
>>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>falseADD>>>>  
>>>>> xsi:type="ns1:LogicalUserList">[removed] list created at 
>>>>> 20150717 
>>>>> 14:18:00Users who visited list A but not B, C 
>>>>> and 
>>>>> DLogicalUserListALL>>>>  
>>>>>

Re: GetIdeas example - ApiException not instance of Throwable?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Richard,

Could you share the error you're getting from the compiler? I want to make 
sure this is the same issue as mentioned below, so it would be helpful to 
have more details for your particular case.

Thanks,
Josh, AdWords API Team

On Sunday, March 4, 2018 at 5:03:59 PM UTC-5, goldenmaza wrote:
>
> Hello Josh
>
> I know you answered this a while ago but I have the same problem. I've 
> read 
> https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html 
> and even if this page explains
> what a classpath is, it was not written for Google AdWords API. So what do 
> I need to do regarding this classpath issue? What file(s)? I also sit with 
> Android Studio.
>
> Kind regards
> Richard
>
> Den tisdag 12 maj 2015 kl. 15:47:23 UTC+2 skrev Josh Radcliff (AdWords API 
> Team):
>>
>> Hi,
>>
>> That error suggests that your classpath is not configured correctly. 
>> Please check out the section of our README on configuring dependencies 
>> <https://github.com/googleads/googleads-java-lib#for-using-jars> and let 
>> me know if you still have questions.
>>
>> Thanks,
>> Josh, 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/ef78a407-9902-48a3-a7b0-c43858e360d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error while trying to add a LogicalUserList

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Could you check out the add_rule_based_user_lists.py example 
<https://github.com/googleads/googleads-python-lib/blob/master/examples/adwords/v201802/remarketing/add_rule_based_user_lists.py>
 and 
then let me know if that doesn't clear up your question?

Thanks,
Josh, AdWords API Team

On Friday, March 2, 2018 at 7:15:13 PM UTC-5, iukhnovy...@gmail.com wrote:
>
> hi, what you exactly changed in your pythone code?
>
> W dniu poniedziałek, 20 lipca 2015 19:50:01 UTC+2 użytkownik Damien 
> napisał:
>>
>> Hi Josh,
>>
>> Thank you very much, this solved my problem and I've been able to 
>> successfully create my LogicalUserList.
>>
>> Damien
>>
>> On Monday, July 20, 2015 at 10:24:21 AM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Damien,
>>>
>>> I think the issue here is your ruleOperands 
>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdwordsUserListService.UserListLogicalRule#ruleOperands>.
>>>  
>>> This attribute should be a list of LogicalUserListOperand 
>>> <https://developers.google.com/adwords/api/docs/reference/v201506/AdwordsUserListService.LogicalUserListOperand>s,
>>>  
>>> each of which in turn has a *child* UserList element.
>>>
>>> So instead of:
>>>   
>>> ALL
>>> 
>>>   102489659
>>>
>>> your request should look like:
>>>   
>>> ALL
>>> 
>>>   
>>> 102489659
>>> 
>>> Please give that a try and let me know if you run into any other issues.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, July 17, 2015 at 2:36:37 PM UTC-4, Damien wrote:
>>>>
>>>> Hi Josh,
>>>>
>>>> Here is the Python logger output, you can find the XML request below 
>>>> (all sensitive information replaced by "[removed]"):
>>>>
>>>> DEBUG:suds.transport.http:opening (https://
>>>> adwords.google.com/api/adwords/rm/v201502/AdwordsUserListService?wsdl)
>>>> DEBUG:suds.transport.http:sending:
>>>> URL: https://
>>>> adwords.google.com/api/adwords/rm/v201502/AdwordsUserListService
>>>> HEADERS: {'Content-Type': 'text/xml; charset=utf-8', 'Authorization': 
>>>> 'Bearer 
>>>> [removed]', 'SOAPAction': b'""', 'Content-type': 'text/xml; 
>>>> charset=utf-8', 'Soapaction': b'""'}
>>>> MESSAGE:
>>>> b'>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/; xmlns:tns="
>>>> https://adwords.google.com/api/adwords/rm/v201502; xmlns:ns2="
>>>> https://adwords.google.com/api/adwords/cm/v201502; xmlns:ns0="
>>>> http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns1="
>>>> https://adwords.google.com/api/adwords/rm/v201502; xmlns:xsi="
>>>> http://www.w3.org/2001/XMLSchema-instance;>>>>  
>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>[removed]>>>  
>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>[removed]>>>  
>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>[removed] 
>>>> (AwApi-Python, googleads/3.5.0, 
>>>> Python/3.4.3)https://adwords.google.com/api/adwords/cm/v201502;>false>>>  
>>>> xmlns:tns="https://adwords.google.com/api/adwords/cm/v201502;>falseADD>>>  
>>>> xsi:type="ns1:LogicalUserList">[removed] list created at 
>>>> 20150717 
>>>> 14:18:00Users who visited list A but not B, C 
>>>> and 
>>>> DLogicalUserListALL>>>  
>>>> xsi:type="ns1:ExpressionRuleUserList">102489659falseList
>>>>  
>>>> A created at 20150717 14:17:57Users who 
>>>> visited 
>>>> a page where URL contains 
>>>> [removed]OPENOWNEDACTIVE30RULE_BASEDExpressionRuleUserListurl__CONTAINS[removed]NONE>>>  
>>>> xsi:type="ns1:ExpressionRuleUserList">102489779falseList
>>>>  
>>>> B created at 20150717 14:17:58Users who 
>>>> visited 
>>>> a page where URL contains 
>>>> [removed]OPENOWNEDACTIVE30RULE_BASEDExpressionRuleUserListurl__CONTAINS[removed]>>>  
>>>> xsi:type="ns1:ExpressionRuleUserList">102489899falseList
>

Re: TargetingIdeaService range of dates

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

No updates to report at this time. We'll be sure to announce any changes in 
release 
notes 
<https://developers.google.com/adwords/api/docs/reference/release-notes/v201802>
 and 
on our blog 
<http://googleadsdeveloper.blogspot.com/search/label/adwords_api> if this 
happens.

Thanks,
Josh, AdWords API Team

On Friday, March 2, 2018 at 1:23:47 AM UTC-5, ta...@evolvedigitallabs.com 
wrote:
>
> Hi,
>
> Any update in this topic again? Do we have option to give custom date 
> range in TargetingIdeaService in version vv201705? Specifically, with 
> python.
> Thanks!
>
> On Tuesday, November 24, 2015 at 8:21:33 AM UTC-6, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> There have not been any changes to *TargetingIdeaService* around dates. 
>> The service still only returns *TARGETED_MONTHLY_SEARCHES* for the last 
>> 12 months.
>>
>> Best regards,
>> Josh, AdWords API Team
>>
>> On Tuesday, November 24, 2015 at 8:44:28 AM UTC-5, Deepa Varma wrote:
>>>
>>> Hi,
>>>
>>>
>>>  Any update in this topic ? Do we have option to give date range 
>>> in TargetingIdeaService in version v201509 ? Please help 
>>>
>>>
>>>
>>> On Wednesday, 3 September 2014 01:59:15 UTC+5:30, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> The API does not support custom date ranges. The closest you can get to 
>>>> approximating that functionality is to include the 
>>>> *TARGETED_MONTHLY_SEARCHES* attribute type you mentioned in your 
>>>> request.
>>>>
>>>> Best regards,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, September 2, 2014 4:55:29 AM UTC-4, Alex wrote:
>>>>>
>>>>> Hello
>>>>>
>>>>> I am trying to use PHP TargetingIdeaService (v201402) to get 
>>>>> TARGETED_MONTHLY_SEARCHES. 
>>>>> Is it possible to restrict the result of a range of dates, as it 
>>>>> happens in KeywordPlanner ( 
>>>>> http://gyazo.com/568f5499d1096ba05e776a05c135b4f9 )? 
>>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/881b7891-7735-41d3-8e06-b6e4948c5c1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't set DYNAMIC_IMAGE MediaType when uploading animated GIF image via MediaService

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Glad to hear the animated gif is working for you. Regarding VIDEO, you can 
only *retrieve* videos from *MediaService*. You cannot upload videos. This 
is mentioned in the documentation for the upload method 
<https://developers.google.com/adwords/api/docs/reference/v201710/MediaService#upload>,
 
but we're about to improve the documentation at the service level to help 
clarify this point. If you want to upload videos, you will have to use the 
user interface.

Thanks,
Josh, AdWords API Team

On Tuesday, February 27, 2018 at 6:12:39 PM UTC-5, Layne Shepherd wrote:
>
> Yes, it works as expected when we upload with IMAGE.  
>
> If you can't use VIDEO when uploading an actual video, then what MediaType 
> do you use?  Documentation says it is required for an ADD operation using 
> MediaService.upload.
>
> On Tuesday, February 27, 2018 at 8:32:59 AM UTC-8, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> While I look into this, are your ads working as expected when you upload 
>> the animated gifs as IMAGE?
>>
>> The MediaService 
>> <https://developers.google.com/adwords/api/docs/reference/v201710/MediaService>
>>  documentation 
>> lists all media types, but some of those types are only supported in 
>> *get* or *query* requests, such as *VIDEO*. It may be that 
>> *DYNAMIC_IMAGE* falls into the read-only category as well. I'll find out 
>> if that's the case, and if so, have our documentation updated accordingly.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, February 26, 2018 at 12:15:08 PM UTC-5, Layne Shepherd wrote:
>>>
>>> I'm uploading new images, inlining image data, and it still gets 
>>> rejected when using DYNAMIC_IMAGE.  The only way I can upload is to use 
>>> IMAGE for MediaType.  These were animated gifs, so I'm wondering what 
>>> DYNAMIC_IMAGE is even used for (has it ever worked?) if I can't upload an 
>>> animated gif to MediaService -- it certainly doesn't work as advertised in 
>>> the API documentation.
>>>
>>> DYNAMIC_IMAGE Animated image, such as animated GIF.
>>> IMAGE Static image; for image ad.
>>> On Sunday, February 25, 2018 at 6:05:27 AM UTC-8, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> My other post 
>>>> <https://groups.google.com/forum/#!msg/adwords-api/JW9EPgtuGek/xagyMMjFBWEJ>
>>>>  from 
>>>> around the same time sheds some light on this and suggests inlining the 
>>>> image data instead of passing a *mediaId*. Have you tried that 
>>>> approach?
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Thursday, February 22, 2018 at 6:47:24 PM UTC-5, Layne Shepherd 
>>>> wrote:
>>>>>
>>>>> I'm getting the same error, 3+ years later.  Would be nice if you guys 
>>>>> posted the solution here instead of just let me take a look at your 
>>>>> account 
>>>>> with no information posted thereafter...
>>>>>
>>>>> On Wednesday, June 11, 2014 at 11:09:47 AM UTC-7, Josh Radcliff 
>>>>> (AdWords API Team) wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Please see my reply to your other post 
>>>>>> <https://groups.google.com/d/msg/adwords-api/JW9EPgtuGek/xagyMMjFBWEJ>. 
>>>>>> Let's continue the discussion on that post if you have further questions.
>>>>>>
>>>>>> Cheers,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Tuesday, June 10, 2014 9:35:36 AM UTC-4, Josh Radcliff (AdWords 
>>>>>> API Team) wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Thanks for clarifying. At this point I think it would be best if I 
>>>>>>> could look at your particular account. Could you send the following 
>>>>>>> *only 
>>>>>>> to me *by clicking *Reply to Author*?
>>>>>>>
>>>>>>> 1. Your customer ID
>>>>>>> 2. The mediaIds of the images you've uploaded
>>>>>>> 3. The image file you uploaded
>>>>>>> 4. Any request/response logs that may be helpful
>>>>>>>
>>>>>>> Also, how do you ultimately want to use the image? In a template ad 
>>>>>>> or in an image ad?
>>>>>>>

Re: Can't set DYNAMIC_IMAGE MediaType when uploading animated GIF image via MediaService

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

While I look into this, are your ads working as expected when you upload 
the animated gifs as IMAGE?

The MediaService 
<https://developers.google.com/adwords/api/docs/reference/v201710/MediaService> 
documentation 
lists all media types, but some of those types are only supported in *get* or 
*query* requests, such as *VIDEO*. It may be that *DYNAMIC_IMAGE* falls 
into the read-only category as well. I'll find out if that's the case, and 
if so, have our documentation updated accordingly.

Thanks,
Josh, AdWords API Team

On Monday, February 26, 2018 at 12:15:08 PM UTC-5, Layne Shepherd wrote:
>
> I'm uploading new images, inlining image data, and it still gets rejected 
> when using DYNAMIC_IMAGE.  The only way I can upload is to use IMAGE for 
> MediaType.  These were animated gifs, so I'm wondering what DYNAMIC_IMAGE 
> is even used for (has it ever worked?) if I can't upload an animated gif to 
> MediaService -- it certainly doesn't work as advertised in the API 
> documentation.
>
> DYNAMIC_IMAGE Animated image, such as animated GIF.
> IMAGE Static image; for image ad.
> On Sunday, February 25, 2018 at 6:05:27 AM UTC-8, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> My other post 
>> <https://groups.google.com/forum/#!msg/adwords-api/JW9EPgtuGek/xagyMMjFBWEJ> 
>> from 
>> around the same time sheds some light on this and suggests inlining the 
>> image data instead of passing a *mediaId*. Have you tried that approach?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, February 22, 2018 at 6:47:24 PM UTC-5, Layne Shepherd wrote:
>>>
>>> I'm getting the same error, 3+ years later.  Would be nice if you guys 
>>> posted the solution here instead of just let me take a look at your account 
>>> with no information posted thereafter...
>>>
>>> On Wednesday, June 11, 2014 at 11:09:47 AM UTC-7, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> Please see my reply to your other post 
>>>> <https://groups.google.com/d/msg/adwords-api/JW9EPgtuGek/xagyMMjFBWEJ>. 
>>>> Let's continue the discussion on that post if you have further questions.
>>>>
>>>> Cheers,
>>>> Josh, AdWords API Team
>>>>
>>>> On Tuesday, June 10, 2014 9:35:36 AM UTC-4, Josh Radcliff (AdWords API 
>>>> Team) wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for clarifying. At this point I think it would be best if I 
>>>>> could look at your particular account. Could you send the following *only 
>>>>> to me *by clicking *Reply to Author*?
>>>>>
>>>>> 1. Your customer ID
>>>>> 2. The mediaIds of the images you've uploaded
>>>>> 3. The image file you uploaded
>>>>> 4. Any request/response logs that may be helpful
>>>>>
>>>>> Also, how do you ultimately want to use the image? In a template ad or 
>>>>> in an image ad?
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Tuesday, June 10, 2014 9:29:50 AM UTC-4, Chingiz Aitkul wrote:
>>>>>>
>>>>>> Hi, yes I can create the ad using UI with the very same animated gif 
>>>>>> Image.
>>>>>>
>>>>>> Actually I can upload the Image via MediaService, and get a generated 
>>>>>> mediaId. The problem is that the Image media is not retrievable after 
>>>>>> that. 
>>>>>> On the other hand, when I upload a static GIF or JPEG Image, it is 
>>>>>> always 
>>>>>> retrievable via MediaService after that. The Java example code from 
>>>>>> google sets the media type as MediaMediaType.IMAGE, before uploading via 
>>>>>> MediaService, so I tried to set MediaMediaType.DYNAMIC_IMAGE instead, 
>>>>>> which 
>>>>>> generated an error I posted above.
>>>>>>
>>>>>> The question is, why does MediaService reply with ok when I upload an 
>>>>>> animated GIF Image by specifying media type IMAGE, but then somehow 
>>>>>> "forget" it? If it is media type DYNAMIC_IMAGE, i should use when 
>>>>>> uploading 
>>>>>> animated GIFs, why do I get error from MediaService?
>>>>>>
>>>>>>
>>>>>> On Monday, June 9, 2014 8:26:32 PM UTC+2, Josh Radcliff (AdWord

Re: Creating a MCC test account.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Thanks for sending me your customer ID. I'm responding here in case it's 
helpful to others.

The new AdWords Experience doesn't show the red banner, but if you log into 
your account and click on the wrench icon and *Return to previous AdWords*, 
you will see the banner.

<https://lh3.googleusercontent.com/-79SaVvYH6mo/WpQVPKngXnI/AEY/1R9MWIh8jbYLYvFCujg6T7_sXq6f-mlCQCLcBGAs/s1600/GgWMmtwFMuN.png>

I'll follow up with the UI team to see if they will add a similar banner to 
the new AdWords Experience. Sorry for the confusion this caused.

Cheers,
Josh, AdWords API Team

On Sunday, February 25, 2018 at 9:11:41 AM UTC-5, Josh Radcliff (AdWords 
API Team) wrote:
>
> Hi,
>
> That link looks correct. Could you send the client customer ID of the 
> account you created only to me by clicking *Reply privately to author* on 
> this message?
>
> Thank you,
> Josh, AdWords API Team
>
> On Friday, February 23, 2018 at 5:12:32 AM UTC-5, dwchg...@gmail.com 
> wrote:
>>
>> Hi,
>>
>> I'm having an issue creating test Google Adwords account. I'm using the 
>> link https://adwords.google.com/um/Welcome/Home?sf=mt=0=1#ta
>> and I don't see the red notice on the top that it is a test account. 
>>
>> Thanks,
>>
>> On Monday, November 27, 2017 at 9:47:42 PM UTC+8, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi,
>>>
>>> When clicking on that link do you:
>>>
>>>1. Open the link in an incongito window?
>>>2. See *Test Account* on the form as mentioned in my earlier post 
>>>
>>> <https://groups.google.com/forum/#!msg/adwords-api/k-4aaBX_hBU/P1tYVCqEKQAJ>
>>>?
>>>
>>> If you'd like me to take a look at the accounts you created, you can 
>>> send the client customer IDs (xxx-xxx-) of those accounts only to me by 
>>> clicking *Reply privately to author* on this post.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, November 27, 2017 at 5:27:09 AM UTC-5, Dominique Star wrote:
>>>>
>>>> I'm having the same issue. Any account created with the 
>>>> https://adwords.google.com/um/Welcome/Home?a=1=mt=0#ta 
>>>> link is not showing as a test ad account.
>>>>
>>>> On Friday, June 16, 2017 at 8:02:02 AM UTC-7, Josh Radcliff (AdWords 
>>>> API Team) wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> We recently made a change to address this issue. Please try creating 
>>>>> an account again and post back here if you still encounter problems.
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Monday, June 5, 2017 at 10:22:59 AM UTC-4, Josh Radcliff (AdWords 
>>>>> API Team) wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> If you actually created an account, could you send the email address 
>>>>>> of that account *only to me* by clicking *Reply privately to author* on 
>>>>>> this message? Also, please let me know your physical locale, as that 
>>>>>> will 
>>>>>> help us determine if this is locale-related.
>>>>>>
>>>>>> Thanks,
>>>>>> Josh, AdWords API Team
>>>>>>
>>>>>> On Monday, June 5, 2017 at 1:57:43 AM UTC-4, Samuel Gjabel wrote:
>>>>>>>
>>>>>>> Same here! Trying to create a test ad account and nothing happened. 
>>>>>>> IDK, but i think thats test accounts in a google and FB are the 
>>>>>>> problem. 
>>>>>>> Couse on the FB i got same result! :p 
>>>>>>>
>>>>>>> Dňa streda, 22. februára 2017 16:22:46 UTC+1 Peter Olvecký 
>>>>>>> napísal(-a):
>>>>>>>>
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>> I've just spent about an hour trying to setup the test account. It 
>>>>>>>> doesn't work.
>>>>>>>>
>>>>>>>> Even though the page says it's for the creation of test accounts 
>>>>>>>> ("Welcome to AdWords manager accounts (Test Account)") and the button 
>>>>>>>> at 
>>>>>>>> the bottom of the page also reads "Create a test account", two things 
>>>>>>>> happen when I hit the button:
>>>>>&

Re: Creating a MCC test account.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

That link looks correct. Could you send the client customer ID of the 
account you created only to me by clicking *Reply privately to author* on 
this message?

Thank you,
Josh, AdWords API Team

On Friday, February 23, 2018 at 5:12:32 AM UTC-5, dwchg...@gmail.com wrote:
>
> Hi,
>
> I'm having an issue creating test Google Adwords account. I'm using the 
> link https://adwords.google.com/um/Welcome/Home?sf=mt=0=1#ta
> and I don't see the red notice on the top that it is a test account. 
>
> Thanks,
>
> On Monday, November 27, 2017 at 9:47:42 PM UTC+8, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> When clicking on that link do you:
>>
>>1. Open the link in an incongito window?
>>2. See *Test Account* on the form as mentioned in my earlier post 
>>
>> <https://groups.google.com/forum/#!msg/adwords-api/k-4aaBX_hBU/P1tYVCqEKQAJ>
>>?
>>
>> If you'd like me to take a look at the accounts you created, you can send 
>> the client customer IDs (xxx-xxx-) of those accounts only to me by 
>> clicking *Reply privately to author* on this post.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, November 27, 2017 at 5:27:09 AM UTC-5, Dominique Star wrote:
>>>
>>> I'm having the same issue. Any account created with the 
>>> https://adwords.google.com/um/Welcome/Home?a=1=mt=0#ta link 
>>> is not showing as a test ad account.
>>>
>>> On Friday, June 16, 2017 at 8:02:02 AM UTC-7, Josh Radcliff (AdWords API 
>>> Team) wrote:
>>>>
>>>> Hi all,
>>>>
>>>> We recently made a change to address this issue. Please try creating an 
>>>> account again and post back here if you still encounter problems.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Monday, June 5, 2017 at 10:22:59 AM UTC-4, Josh Radcliff (AdWords 
>>>> API Team) wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> If you actually created an account, could you send the email address 
>>>>> of that account *only to me* by clicking *Reply privately to author* on 
>>>>> this message? Also, please let me know your physical locale, as that will 
>>>>> help us determine if this is locale-related.
>>>>>
>>>>> Thanks,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Monday, June 5, 2017 at 1:57:43 AM UTC-4, Samuel Gjabel wrote:
>>>>>>
>>>>>> Same here! Trying to create a test ad account and nothing happened. 
>>>>>> IDK, but i think thats test accounts in a google and FB are the problem. 
>>>>>> Couse on the FB i got same result! :p 
>>>>>>
>>>>>> Dňa streda, 22. februára 2017 16:22:46 UTC+1 Peter Olvecký 
>>>>>> napísal(-a):
>>>>>>>
>>>>>>> Hi guys,
>>>>>>>
>>>>>>> I've just spent about an hour trying to setup the test account. It 
>>>>>>> doesn't work.
>>>>>>>
>>>>>>> Even though the page says it's for the creation of test accounts 
>>>>>>> ("Welcome to AdWords manager accounts (Test Account)") and the button 
>>>>>>> at 
>>>>>>> the bottom of the page also reads "Create a test account", two things 
>>>>>>> happen when I hit the button:
>>>>>>>
>>>>>>> 1. The same form loads again (
>>>>>>> https://adwords.google.com/um/Welcome/Home?a=1=mt=0#ta)
>>>>>>> 2. I am being redirected to page for creation of production client 
>>>>>>> account (
>>>>>>> https://adwords.google.com/um/Welcome/Home?a=1=0=bb#ac)
>>>>>>>
>>>>>>> Can you please help me?
>>>>>>>
>>>>>>> Thank you,
>>>>>>> Peter
>>>>>>>
>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/e360a175-89f4-4d68-a2de-bb910bca75e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pause Adwords Express campaign via API

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

I don't expect this to change in the near future, although we'll continue 
to support AdWords Express campaigns in reports.

Thanks,
Josh, AdWords API Team

On Thursday, February 22, 2018 at 11:42:42 PM UTC-5, Nick Harris wrote:
>
> Any idea if this will change at some point? I'd like to be able to perform 
> MUTATE actions on AdWords Express accounts via the API.
>
> I had never even heard about this lack of API functionality until I kept 
> getting this error when attempting to PAUSE/ENABLE AdGroups via API in an 
> Express account:
>
> https://developers.google.com/adwords/api/docs/common-errors#OperationAccessDenied.MUTATE_ACTION_NOT_PERMITTED_FOR_CLIENT
>
>
> On Tuesday, July 11, 2017 at 6:01:48 AM UTC-7, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Diego,
>>
>> Unfortunately, you can only pause AdWords Express campaigns through the 
>> AdWords Express user interface. If you pause the promotion in the user 
>> interface, the underlying campaigns will switch to paused shortly 
>> thereafter.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Tuesday, July 11, 2017 at 3:28:10 AM UTC-4, Thanet Knack Praneenararat 
>> (AdWords API Team) wrote:
>>>
>>> Hello Diego,
>>>
>>> I'm checking with my colleague and will get back to you soon.
>>>
>>> Cheers,
>>> Thanet, AdWords API Team
>>>
>>> On Tuesday, July 11, 2017 at 3:57:18 AM UTC+9, Diego wrote:
>>>>
>>>> Hi,
>>>>
>>>> is it possible to pause an Adwords Express campaign via API? If not, is 
>>>> there any workaround we might do to do so?
>>>>
>>>> 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/27bb2e9a-cfd9-478c-9819-84953dfb2894%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't set DYNAMIC_IMAGE MediaType when uploading animated GIF image via MediaService

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

My other post 
<https://groups.google.com/forum/#!msg/adwords-api/JW9EPgtuGek/xagyMMjFBWEJ> 
from 
around the same time sheds some light on this and suggests inlining the 
image data instead of passing a *mediaId*. Have you tried that approach?

Thanks,
Josh, AdWords API Team

On Thursday, February 22, 2018 at 6:47:24 PM UTC-5, Layne Shepherd wrote:
>
> I'm getting the same error, 3+ years later.  Would be nice if you guys 
> posted the solution here instead of just let me take a look at your account 
> with no information posted thereafter...
>
> On Wednesday, June 11, 2014 at 11:09:47 AM UTC-7, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> Please see my reply to your other post 
>> <https://groups.google.com/d/msg/adwords-api/JW9EPgtuGek/xagyMMjFBWEJ>. 
>> Let's continue the discussion on that post if you have further questions.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Tuesday, June 10, 2014 9:35:36 AM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi,
>>>
>>> Thanks for clarifying. At this point I think it would be best if I could 
>>> look at your particular account. Could you send the following *only to 
>>> me *by clicking *Reply to Author*?
>>>
>>> 1. Your customer ID
>>> 2. The mediaIds of the images you've uploaded
>>> 3. The image file you uploaded
>>> 4. Any request/response logs that may be helpful
>>>
>>> Also, how do you ultimately want to use the image? In a template ad or 
>>> in an image ad?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, June 10, 2014 9:29:50 AM UTC-4, Chingiz Aitkul wrote:
>>>>
>>>> Hi, yes I can create the ad using UI with the very same animated gif 
>>>> Image.
>>>>
>>>> Actually I can upload the Image via MediaService, and get a generated 
>>>> mediaId. The problem is that the Image media is not retrievable after 
>>>> that. 
>>>> On the other hand, when I upload a static GIF or JPEG Image, it is always 
>>>> retrievable via MediaService after that. The Java example code from 
>>>> google sets the media type as MediaMediaType.IMAGE, before uploading via 
>>>> MediaService, so I tried to set MediaMediaType.DYNAMIC_IMAGE instead, 
>>>> which 
>>>> generated an error I posted above.
>>>>
>>>> The question is, why does MediaService reply with ok when I upload an 
>>>> animated GIF Image by specifying media type IMAGE, but then somehow 
>>>> "forget" it? If it is media type DYNAMIC_IMAGE, i should use when 
>>>> uploading 
>>>> animated GIFs, why do I get error from MediaService?
>>>>
>>>>
>>>> On Monday, June 9, 2014 8:26:32 PM UTC+2, Josh Radcliff (AdWords API 
>>>> Team) wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> The UI supports a wide variety of ads, but the API may not necessarily 
>>>>> support every one of these formats. As a starting point, have you tried 
>>>>> creating the ad through the UI using the image in question? If the UI 
>>>>> won't 
>>>>> create the ad, then the API will not either.
>>>>>
>>>>> Also, the MediaService is meant for usage with template ads 
>>>>> <https://developers.google.com/adwords/api/docs/appendix/templateads>, 
>>>>> which does *not* include ImageAd 
>>>>> <https://developers.google.com/adwords/api/docs/reference/v201402/AdGroupAdService.ImageAd>s.
>>>>>  
>>>>> If you want to create an *ImageAd* you'll have to skip *MediaService* 
>>>>> altogether and pass the image data directly on the ImageAd.image.data 
>>>>> <https://developers.google.com/adwords/api/docs/reference/v201402/AdGroupAdService.Image#data>
>>>>>  field in 
>>>>> your *AdGroupAdService* request.
>>>>>
>>>>> Cheers,
>>>>> Josh, AdWords API Team
>>>>>
>>>>> On Friday, June 6, 2014 12:08:42 PM UTC-4, Chingiz Aitkul wrote:
>>>>>>
>>>>>> Hi there, I am trying to upload an animated GIF Image via upload() 
>>>>>> method of MediaService using example code provided with Java library for 
>>>>>> AdWords API. When I upload a static GIF or JPEG file it works ok.
>>>>>>
>>>>>> When I try to upload an a

Re: Unable to get refresh Token

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The client ID and client secret you used are for the *Web application* flow. 
The *GetRefreshToken.php* example will only work if the client ID and 
client secret specified are for credentials with *Application type = Other* 
(the 
installed application flow). Please see the *Create a client ID and secret* 
section 
of the AdWords API OAuth guide 

 for 
instructions on how to create this type of credential.

Thanks,
Josh, AdWords API Team

On Tuesday, January 23, 2018 at 5:12:45 PM UTC-5, 
trinath.esano...@gmail.com wrote:
>
> How do i generate the authorization code?
> here is the link to what i done : http://prntscr.com/i4f455
> after Running the url, the result is : http://prntscr.com/i4f7hy
>
>
>
>
> On Wednesday, 3 September 2014 14:42:18 UTC+5:30, Shukla Abhinav wrote:
>>
>> *I am trying to run my adwords but everytime I try to execute the 
>> GetRefreshToken.php file on my server I get the following error*
>>
>> Warning: Error parsing 
>>  ../googleads-php-lib-master/src/Google/Api/Ads/AdWords/Lib/api.properties 
>> on line 14 in .. 
>> /googleads-php-lib-master/src/Google/Api/Ads/Common/Util/ApiPropertiesUtils.php
>>  
>> on line 40  Notice: Use of undefined constant WSDL_CACHE_NONE - assumed 
>> WSDL_CACHE_NONE in  .. 
>> /googleads-php-lib-master/src/Google/Api/Ads/Common/Lib/AdsUser.php on line 
>> 231 Log in to your AdWords account and open the following URL:
>> https://accounts.google.com/o/oauth2/auth?response_type=codeclient_id=529713113834-pcltkti85cv8...
>>  
>> 
>>  After 
>> approving the token enter the authorization code here: Your OAuth2 
>> Credentials are incorrect. Please see the GetRefreshToken.php example. { 
>> error : invalid_request, 
>> error_description : Missing required parameter: 
>> code }
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/516923fa-7cf2-4cf1-a39e-98f6dceea961%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Conservative Targeting in AdWords API

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

There have not been any changes since my previous post, but if this 
functionality is added to the AdWords API, we'll announce it on our blog 
<http://googleadsdeveloper.blogspot.com/search/label/adwords_api> or in the 
release 
notes 
<https://developers.google.com/adwords/api/docs/reference/release-notes>.

Thanks,
Josh, AdWords API Team

On Tuesday, January 16, 2018 at 11:59:53 AM UTC-5, juche...@ppcguru.cz 
wrote:
>
> Hello,
>
> is there still no way to distinguish Disabled Targeting optimization and 
> Conservative mode via API? 
>
> Thank you.
>
> On Friday, September 29, 2017 at 2:30:31 PM UTC+2, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Tim,
>>
>> Unfortunately, the AdWords API doesn't expose the "conservative" setting, 
>> so this information will have to be retrieved using the UI.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, September 28, 2017 at 2:48:44 PM UTC-4, Tim Tsai wrote:
>>>
>>> Hi there,
>>>
>>> Is it possible to use the API to determine of a campaign has checked 
>>> "conservative targeting?" 
>>>
>>> I know that we can use the ExplorerAutoOptimizerSetting 
>>> <https://developers.google.com/adwords/api/docs/reference/v201705/AdGroupService.ExplorerAutoOptimizerSetting>
>>>  field 
>>> to find if a campaign has "aggressive targeting" set, but what about 
>>> conservative?
>>>
>>>
>>> Thanks,
>>> Tim
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c7eaa394-cb8d-4447-a0b9-e9856069dac4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Adwords API java -> Exception in thread "main" AxisFault

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

There are tools for updating your certificate store, but I would definitely 
check with your system administrator before doing so. Chances are that they 
have a process in place for keeping certificates up to date that's more 
reliable than manually importing specific certificates.

Thanks,
Josh, AdWords API Team

On Wednesday, January 10, 2018 at 7:27:51 PM UTC-5, kcaua...@gmail.com 
wrote:
>
> Hi there,
>
> We have had the same issue and we don;t know where to download the 
> certificates from. Can you please share a link to the latest Google AdWords 
> certificate to resolve this issue?
>
> Thanks,
>
> On Friday, February 12, 2016 at 11:14:53 AM UTC+11, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Saravanan,
>>
>> I would talk to your system administrator to see why your cert store is 
>> missing the certificate for adwords.google.com. My guess is that you had 
>> to download it again the next day because there's some automated process 
>> (from your sys admin) that refreshes your cert store each night.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, February 11, 2016 at 3:09:25 PM UTC-5, saravana...@ihg.com 
>> wrote:
>>>
>>> Hi,
>>>
>>> I am getting the same error and I infact downloaded the certificate for "
>>> adwords.google.com" and things worked fine afterwards. However, the 
>>> very next day it started coming again and so had to download the 
>>> certificate again. May I know why do I need to download it daily OR is 
>>> there any resolution available?
>>>
>>> Below is the code snippet to get AdwordsSession:
>>>
>>>  HttpTransport httpTransport = new 
>>> NetHttpTransport.Builder().doNotValidateCertificate().build();
>>> JsonFactory jsonFactory = JacksonFactory.getDefaultInstance();
>>> InputStreamReader propStream = new 
>>> InputStreamReader(AdwordsSessionFactory.class.getClassLoader().getResourceAsStream("conf/credentials.json"),
>>>  
>>> "UTF-8");
>>> GoogleClientSecrets clientSecrets = 
>>> GoogleClientSecrets.load(jsonFactory, propStream);
>>> GoogleCredential credential = new 
>>> GoogleCredential.Builder().setTransport(httpTransport).setJsonFactory(jsonFactory).setClientSecrets(clientSecrets).build();
>>>
>>> AdWordsSession adWordsSession = new 
>>> AdWordsSession.Builder().from(this.adwordsPropConfiguration).withOAuth2Credential(credential).build();
>>> return adWordsSession;
>>>
>>> Thanks,
>>> Saravanan
>>>
>>> On Friday, January 2, 2015 at 10:13:25 AM UTC-5, Josh Radcliff (AdWords 
>>> API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> Could you share the code you are using to create your *AdWordsSession*?
>>>>
>>>> Also, the error suggests that you are using a service account, but as 
>>>> mentioned in our Service Accounts guide 
>>>> <https://developers.google.com/adwords/api/docs/guides/service-accounts>
>>>> :
>>>>
>>>> OAuth2 offline and web flows require user interaction only once: when 
>>>>> access to the account is granted. From that point, all operations can be 
>>>>> executed with no manual steps until the access token is revoked. We 
>>>>> strongly recommend using offline or web flows instead of service accounts
>>>>>  *unless you need domain-specific features* (e.g. impersonation).
>>>>
>>>>
>>>> Please make sure you remove any sensitive information when posting.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Friday, January 2, 2015 4:26:43 AM UTC-5, Rajalakshmi Thangavelu 
>>>> wrote:
>>>>>
>>>>>
>>>>> Hi Team,
>>>>>
>>>>> I have connected the Google Adwords through the java and have set all 
>>>>> the properties including the client secret,clientid,etc.
>>>>>
>>>>> I m getting the below error...
>>>>>
>>>>>
>>>>>
>>>>> log4j:WARN No appenders could be found for logger 
>>>>> (org.apache.commons.configuration.PropertiesConfiguration).
>>>>> log4j:WARN Please initialize the log4j system properly.
>>>>> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig 
>>>>> for more info.
>>>>> Exc

Re: Error handling for Ad Text

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

If you have *partialFailure=true*, then each operation without errors will 
be applied, but operations with errors will be returned. With 
*partialFailure=false* (or not specified), all operations in a request will 
fail if *any* operation in the request has errors.

The basic validation checks on operations occur before any policy violation 
checks, so if you have fields that hit basic validation issues, you'll only 
get back those errors in the response. If all of an ad's fields pass the 
basic validation checks, then I would expect you to get back all of the 
policy violation errors for each ad in the error response. One reason for 
this is that performing more complex validation checks when there are basic 
validation issues could produce confusing or meaningless errors. For 
example, if a final URL has an invalid protocol, it wouldn't be very 
helpful if the AdWords API also returned an error to indicate that the 
final URL was unreachable.

In the particular case you mentioned, the missing protocol in the final URL 
falls into the basic validation category, so you'd have to correct that 
before you'll get back policy violation errors. If you frequently encounter 
specific basic validation errors, then you may want to add validation 
within your application to avoid submitting those operations.

As an alternative, you could submit your request with validateOnly=true 
,
 
which will perform most of the validation steps for your request, but won't 
actually apply the changes. This would allow you to identify problematic 
operations, fix them, and then send the corrected operations in a second 
request with *validateOnly=false*.

Thanks,
Josh, AdWords API Team

On Wednesday, January 10, 2018 at 7:13:27 AM UTC-5, cv wrote:
>
> Hello Vincent,
>
> Thanks for your reply.
>
> I am assuming that partial failure is not giving me errors for those ads 
> who fails. But without error ads will be submitted to Adwords. Right?
> what about when I do not wants to post all the ads when any of the Ads 
> with error?
>
> That is why I tried using validate adtext before posting.
>
> Anyway I can get those ads also which has policy violation error along 
> with basic errors?
>
> Thanks,
>
> On Wednesday, 10 January 2018 13:34:05 UTC+5:30, Vincent Racaza (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> You can set the partialFailure 
>> 
>>  to 
>> true to commit all the successful operations and get/handle all the errors 
>> from the failed operations in one request. You can check in the link the 
>> supported services for this feature. You can also see the code examples 
>> here 
>> 
>> .
>>
>> Please try this and let me know if this works for you.
>>
>> 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/673b8eab-e97b-482a-9890-01b398e786d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PHP pass credentials dynamically (not through adsapi_php.ini)

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Jean,

I'm going to send this over to our PHP client library expert. Since your 
questions revolve around the details of that library, you may want to open 
an issue on Github  so 
we can track this under the library's issue tracker.

Thanks,
Josh, AdWords API Team

On Monday, January 8, 2018 at 12:34:36 AM UTC-5, Jean-Fabrice Rabaute wrote:
>
> Hi Vincent,
>
> Thank you for your answer.
> I have added more questions inline.
> For info, I'm using the public google adwords php library 
> .
>
> Le dimanche 7 janvier 2018 21:00:59 UTC-8, Vincent Racaza (AdWords API 
> Team) a écrit :
>>
>> Hi Jean,
>>
>> If you are using our client libraries, you don't need to manually set the 
>> access token in your request as the library itself is generating an access 
>> token in the background using your refresh token. 
>>
>
> What does "generating" means here? I've tried, and in my case, it means an 
> http request to get a new access token. It means that it's slow because 
> almost every query to the adwords api is from a newly instantiated 
> AdwordsSessionBuilder so there is no access token. So every time my web app 
> is getting a client call and instantiating the object, and querying adwords 
> api on behalft of the client, two synchronous calls will be done: one to 
> get a valid access token, one for the real query.
>
>
>  
>
>> If your access token is about to expire or has already expired, the 
>> client library will automatically generate a new access token using the 
>> refresh token.
>>
>> About setting or reusing the access token, this is already incorporated 
>> in the client libraries, and you don't need to do this manually. 
>>
>
> How can the library do this when it does not know anything about the 
> environment it's working on? When a system is distributed (having multiple 
> instances of the web app running on different machines and load-balanced), 
> how can the php library itself share and synchronize a common resource 
> between the instances?
>
> The Google Adwords doc is talking about this problem here: 
> https://developers.google.com/adwords/api/docs/guides/authentication#optimizing_oauth2_requests
>
> It seems pretty clear to me that it's the application responsibility to 
> cache/share/synchronize the token on a distributed app design.
>
> Am I missing something? If so, can you point me to the code in the adwords 
> php library which takes care of caching the access_token on distributed 
> environments?
>  
>
>> There is also no method currently that would manually set the access 
>> token in your request. If you want to reuse your access token for your 
>> separate requests, then you can use the refresh token instead as this is 
>> linked to your access token at a time.
>>
>
> Yes, that works, but it's means adding a preliminary http request every 
> time, which is not optimal.
>  
>
>>
>> Also, if you are not using our client libraries, you can refer to the 
>> generic OAuth2 guide 
>> . The guide 
>> provides a step by step instructions on how to authenticate via the 
>> authentication type of your choice. For example, if you will be 
>> authenticating via the "Installed application" type 
>> , 
>> it provides the whole steps on how to generate the refresh and access 
>> tokens and how to call an API method 
>> 
>>  via 
>> HTTP or CURL request.
>>
>> If you have further clarifications on this, I suggest that you create a 
>> new forum thread so we can better track your concern.
>>
>> Thanks,
>>
>
> 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/b84cf109-a6fb-4e97-af69-90a31fcdb0b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to check current keyword position

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Pierre,

When you ran your experiment, did you set any of the fields of 
PageOnePromotedBiddingScheme 
,
 
such as the following?

   1. *bidCeiling*
   2. *bidModifier*
   3. *bidChangesForRaisesOnly*
   4. *raiseBidWhenLowQualityScore*
   
For example, if you had *bidChangesForRaisesOnly* set to *true*, then the 
strategy might be lowering your bids, which in turn could lead to fewer 
impressions. If you had *raiseBidWhenLowQualityScore* set to *true*, you 
could see increased costs from keywords that need improvement. Check out 
the Help Center article on the bidding scheme 
 for more details.

Also, you mentioned fewer clicks. Did you also see fewer *impressions*, and 
was your AveragePosition 

 better 
or worse than when you manually manage bids?

Thanks,
Josh, AdWords API Team

On Saturday, December 23, 2017 at 4:07:40 AM UTC-5, Pierre Augereau wrote:
>
> Hello Josh and thank you for your answer.
>
> Yes, I already tried to use automated bidding for few days. 
> 20% more expensive and 10% less clics on all keywords by using 
> PAGE_ONE_PROMOTED option.
>
>
> 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 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/b5ce3488-af49-4da3-984d-c0aa6782ac0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to check current keyword position

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Pierre,

Have you considered using automated bidding strategies to accomplish your 
goals? For example, the PageOnePromotedBiddingScheme 

 ("Target 
search page location") will automatically adjust your bids with the goal of 
showing your ad on the top of the page or on the first page of Google 
search results. You can read more details about the strategy in this 
AdWords Help Center article 
.

Cheers,
Josh, AdWords API Team

On Friday, December 22, 2017 at 2:53:06 AM UTC-5, Pierre Augereau wrote:
>
> It is not about predicting. It is more if you can check your position 
> periodicly, you can react as fast as you can. With a good home made sofware 
> using the API to update bid, it is not so hard !! 
> For the average position at 0, I agree, that might be considering as 
> predicting but it is not. More you check your position, faster you can 
> react.
> However, as you said in previous message, competitors can use bid 
> modifiers with time / day / gender / ... But, with good datas, good 
> historics datas, good software and a way to check anytime you want, I think 
> you can predict when some competitors starting their campaign. Anyway, it 
> is an another subject.
>
> In a period where markets act really fast, I don't understand why we do 
> not have any tools (or the possibiliy to make one) who can 'analyse' and 
> react as fast as possible ??!!! 
>
> I agree with your exemple but, and it is certainly because my english is 
> really bad, there is no targeting at all inside...
> Take 'property sale', in Paris on one spécific district, targeting end 
> user inside this location and those who make interest for this location, + 
> 10% bid on smartphone, and of course the money... Et Voila !!! You are 
> first and it's working.
>
> Obviously, we don't have the same method to work with AdWords. I'm sure 
> your method works but mine too. 
> So yes, I want to be #1 the most of time (again, with a good and specific 
> targeting) and if I can have a tool or a way to check my positions in real 
> time, I'm pretty sure to reach my goal.
>
> However, we are moving away from the original topic : 
> - Datas from MCM and API are wrong (delayed time and, for example, 
> estimated cost for top positions totaly wrong) and not accurate (average)
> - Adpreview which is working fine but, it's humainly impossible to check 
> all your keywords and your IP get blocked after, more or less, 60 calls 
> more or less
> - No way to control where your money go
>
> 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 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/7d754bf2-cdf6-48ca-8ba4-1998bb9b2e6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Final URL / Final URLs- how to you get the same value as the UI?

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Timna,

The AD_PERFORMANCE_REPORT will show you the *static* attributes of each ad, 
so it won't reflect the actual effective URLs (with parameter values filled 
in) for each impression. To get that information, use the FINAL_URL_REPORT 

 instead 
and include the EffectiveFinalUrl 

 field 
in your report request.

Thanks,
Josh, AdWords API Team

On Wednesday, December 20, 2017 at 9:24:40 AM UTC-5, Timna Carmel wrote:
>
> Hi Peter, 
>
> I used the reply privately. please let me know if you got it or not as I 
> can't see it here :) so not sure it was posted successfully 
>
>
> Thanks,
>
> Timna
>
> On Thursday, November 23, 2017 at 9:41:52 AM UTC+2, Peter Oliquino wrote:
>>
>> Hi Timna,
>>
>> In order to better investigate your concern, could you provide the 
>> AdWords UI screenshot where you viewed your final URLs, your 
>> clientCustomerId, and the complete report definition 
>> 
>>  you 
>> used when generating the Ad Performance Report? You may reply using 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/a95b7e93-3e89-4c46-8d12-708369caa8d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FeedItem service returns invalid characters.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

Yes, I think that's the best approach. If they export their feed items to a 
CSV, it should be pretty easy to see the unprintable characters, and then 
they can fix those through the user interface.

Thanks,
Josh, AdWords API Team

On Friday, December 8, 2017 at 7:06:36 PM UTC-5, Caihua Du wrote:
>
> Got it. In our case, customer is using our tool to get FeedItem data, and 
> we are not able to modify the invalid data for them without their 
> permission and hence mutate operation may not be an option for us. It seems 
> to me there is no other way to fix unless customer update their data 
> specifically. 
>
> On Friday, December 8, 2017 at 1:53:09 PM UTC-8, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> You could exclude the problematic feed item ID(s) via a *FeedItemId 
>> NOT_IN [..., ..., ...]* predicate. That would allow you to retrieve all 
>> of the other feed items in your feeds. To fix the problematic feed items, 
>> you can update or remove them via the AdWords user interface or through a 
>> *FeedItemService.mutate* request.
>>
>> Note that when I've seen data like this in the past, it's been due to 
>> users somehow adding the invalid values *outside* of the AdWords API 
>> (for example, through AdWords Editor, Bulk uploads, or the AdWords user 
>> interface). I don't foresee us adding special encoding rules to the AdWords 
>> API for these cases, since that would mean all clients would have to 
>> understand how to interpret those rules.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Friday, December 8, 2017 at 3:37:19 PM UTC-5, Caihua Du wrote:
>>>
>>> Thank you Josh for looking into it. Is that possible we skip sending the 
>>> invalid character to the response or we convert to some encoded format? We 
>>> had similar issue last year from AdWords and I believe the solved it early 
>>> this year. Not sure if we can use the same pattern here. 
>>>
>>> On Thursday, December 7, 2017 at 11:29:26 AM UTC-8, Josh Radcliff 
>>> (AdWords API Team) wrote:
>>>>
>>>> Hi,
>>>>
>>>> The reason that error is being thrown is that the underlying data in 
>>>> (at least) one particular feed item is invalid. Specifically, the string 
>>>> value for attribute ID 3 in feed ID 23642780/feed item ID 957498860 
>>>> contains unicode character 031. If you update that feed item through the 
>>>> UI 
>>>> or the AdWords API so it contains valid characters, you should be all set.
>>>>
>>>> Thanks,
>>>> Josh, AdWords API Team
>>>>
>>>> On Thursday, December 7, 2017 at 12:52:29 PM UTC-5, Caihua Du wrote:
>>>>>
>>>>> Hi Vincent,
>>>>>
>>>>> I haven sent you the SOAP requestID privately, can you please take a 
>>>>> look? We have two new instance of this failure again today. Thank you 
>>>>> very 
>>>>> much!
>>>>>
>>>>> On Wednesday, December 6, 2017 at 12:52:07 AM UTC-8, Vincent Racaza 
>>>>> (AdWords API Team) wrote:
>>>>>>
>>>>>> Hi Caihua,
>>>>>>
>>>>>> Could you provide the SOAP request and response logs instead with the 
>>>>>> clientCustomerId so I can investigate further? To get all the success 
>>>>>> and 
>>>>>> failed SOAP request and response, you can change all the INFO 
>>>>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/log4j.properties#L31>
>>>>>>  level 
>>>>>> to DEBUG in the log4j.properties 
>>>>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/log4j.properties>
>>>>>>  file 
>>>>>> (in Java). If you are using other client libraries, you can also do the 
>>>>>> same in their log property file. Please use the *Reply privately to 
>>>>>> author* option when replying.
>>>>>>
>>>>>> 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/0cd53c7c-c780-4472-bd4e-a4295014679b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FeedItem service returns invalid characters.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

You could exclude the problematic feed item ID(s) via a *FeedItemId NOT_IN 
[..., ..., ...]* predicate. That would allow you to retrieve all of the 
other feed items in your feeds. To fix the problematic feed items, you can 
update or remove them via the AdWords user interface or through a 
*FeedItemService.mutate* request.

Note that when I've seen data like this in the past, it's been due to users 
somehow adding the invalid values *outside* of the AdWords API (for 
example, through AdWords Editor, Bulk uploads, or the AdWords user 
interface). I don't foresee us adding special encoding rules to the AdWords 
API for these cases, since that would mean all clients would have to 
understand how to interpret those rules.

Thanks,
Josh, AdWords API Team

On Friday, December 8, 2017 at 3:37:19 PM UTC-5, Caihua Du wrote:
>
> Thank you Josh for looking into it. Is that possible we skip sending the 
> invalid character to the response or we convert to some encoded format? We 
> had similar issue last year from AdWords and I believe the solved it early 
> this year. Not sure if we can use the same pattern here. 
>
> On Thursday, December 7, 2017 at 11:29:26 AM UTC-8, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> The reason that error is being thrown is that the underlying data in (at 
>> least) one particular feed item is invalid. Specifically, the string value 
>> for attribute ID 3 in feed ID 23642780/feed item ID 957498860 contains 
>> unicode character 031. If you update that feed item through the UI or the 
>> AdWords API so it contains valid characters, you should be all set.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, December 7, 2017 at 12:52:29 PM UTC-5, Caihua Du wrote:
>>>
>>> Hi Vincent,
>>>
>>> I haven sent you the SOAP requestID privately, can you please take a 
>>> look? We have two new instance of this failure again today. Thank you very 
>>> much!
>>>
>>> On Wednesday, December 6, 2017 at 12:52:07 AM UTC-8, Vincent Racaza 
>>> (AdWords API Team) wrote:
>>>>
>>>> Hi Caihua,
>>>>
>>>> Could you provide the SOAP request and response logs instead with the 
>>>> clientCustomerId so I can investigate further? To get all the success and 
>>>> failed SOAP request and response, you can change all the INFO 
>>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/log4j.properties#L31>
>>>>  level 
>>>> to DEBUG in the log4j.properties 
>>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/log4j.properties>
>>>>  file 
>>>> (in Java). If you are using other client libraries, you can also do the 
>>>> same in their log property file. Please use the *Reply privately to 
>>>> author* option when replying.
>>>>
>>>> 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/713430ee-4b1a-4b58-bd41-cc448733e69f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FeedItem service returns invalid characters.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The reason that error is being thrown is that the underlying data in (at 
least) one particular feed item is invalid. Specifically, the string value 
for attribute ID 3 in feed ID 23642780/feed item ID 957498860 contains 
unicode character 031. If you update that feed item through the UI or the 
AdWords API so it contains valid characters, you should be all set.

Thanks,
Josh, AdWords API Team

On Thursday, December 7, 2017 at 12:52:29 PM UTC-5, Caihua Du wrote:
>
> Hi Vincent,
>
> I haven sent you the SOAP requestID privately, can you please take a look? 
> We have two new instance of this failure again today. Thank you very much!
>
> On Wednesday, December 6, 2017 at 12:52:07 AM UTC-8, Vincent Racaza 
> (AdWords API Team) wrote:
>>
>> Hi Caihua,
>>
>> Could you provide the SOAP request and response logs instead with the 
>> clientCustomerId so I can investigate further? To get all the success and 
>> failed SOAP request and response, you can change all the INFO 
>> 
>>  level 
>> to DEBUG in the log4j.properties 
>> 
>>  file 
>> (in Java). If you are using other client libraries, you can also do the 
>> same in their log property file. Please use the *Reply privately to 
>> author* option when replying.
>>
>> 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/c095c7f6-0e5e-4b12-ae6e-beb1c121c23e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upload and download via API

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

The AdWords API doesn't specifically include uploads from CSV or Google 
Drive. However, you could certainly read a file in your application and use 
that data to construct your AdWords API requests. If your files are in 
Google Drive, then you can use the Google Drive API 
<https://developers.google.com/drive/> for the first step.

Thanks,
Josh, AdWords API Team

On Wednesday, November 29, 2017 at 4:32:09 AM UTC-5, Alessandro Improta 
wrote:
>
> I see Adwords Scripts allows you to upload .csv files directly from your 
> google drive. Is it still the case that this kind of thing cannot be done 
> through the API? If not, is there any kind of similar solution?
>
> On Friday, January 23, 2015 at 3:37:42 PM UTC-7, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi Michelle,
>>
>> The API does not directly support importing from Excel. A better fit for 
>> that use case is the AdWords Editor 
>> <http://www.google.com/intl/en_US/adwordseditor/> or AdWords Scripts 
>> <https://developers.google.com/adwords/scripts/>.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Friday, January 23, 2015 at 10:13:02 AM UTC-5, 
>> michell...@schooloutfitters.com wrote:
>>>
>>> I have a similar question. I want to upload an excel spreadsheet with ad 
>>> group and keyword bid changes. Does the API support this today? If so, what 
>>> format does the spreadsheet require?
>>>
>>> Thanks,
>>> Michelle
>>>
>>> On Thursday, August 20, 2009 at 2:41:18 PM UTC-4, AdWords API Advisor 
>>> wrote:
>>>>
>>>> Hi John, 
>>>>
>>>> Unfortunately there isn't the ability to upload a list of changes in a 
>>>> spreadsheet directly via the API, you would need to write a program 
>>>> that will parse the spreadsheet and make API calls to modify the 
>>>> keywords.  There are a number of client libraries available that make 
>>>> it simpler to call API methods, which are listed here: 
>>>> http://code.google.com/apis/adwords/docs/clients.html. 
>>>>
>>>> You may also want to investigate using the AdWords Editor, a free 
>>>> program provided by Google that allows you to work with your AdWords 
>>>> account.  It supports the upload of CSV files, and this may be a 
>>>> simpler way to achieve your goals.  You can download it here: 
>>>> http://www.google.com/intl/en/adwordseditor/. 
>>>>
>>>> At this time the report data can only be returned in XML format, but 
>>>> thanks for letting us know about your interest in other formats. 
>>>>
>>>> Best, 
>>>> - Eric Koleda, AdWords API Team 
>>>>
>>>> On Aug 19, 11:12 am, John <chenshu...@gmail.com> wrote: 
>>>> > I have requirements to delete keywords from AdWords accounts based on 
>>>> > an excel spreadsheet which contains a list of 
>>>> > account,adgroup,campaign, keywords. What would be best way to do 
>>>> this? 
>>>> > Does AdWords API accept an upload file like this for deleting 
>>>> > keywords? 
>>>> > 
>>>> > Second question, when using ReportService, is xml is only format for 
>>>> a 
>>>> > download report? Is it possible to get an excel report like from the 
>>>> > Google AdWords user web interface? 
>>>> > 
>>>> > Thanks, 
>>>> > John
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/fdbc0e86-6cab-47db-a09b-6b017da31263%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Creating a MCC test account.

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

When clicking on that link do you:

   1. Open the link in an incongito window?
   2. See *Test Account* on the form as mentioned in my earlier post 
   <https://groups.google.com/forum/#!msg/adwords-api/k-4aaBX_hBU/P1tYVCqEKQAJ>
   ?

If you'd like me to take a look at the accounts you created, you can send 
the client customer IDs (xxx-xxx-) of those accounts only to me by 
clicking *Reply privately to author* on this post.

Thanks,
Josh, AdWords API Team

On Monday, November 27, 2017 at 5:27:09 AM UTC-5, Dominique Star wrote:
>
> I'm having the same issue. Any account created with the 
> https://adwords.google.com/um/Welcome/Home?a=1=mt=0#ta link 
> is not showing as a test ad account.
>
> On Friday, June 16, 2017 at 8:02:02 AM UTC-7, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi all,
>>
>> We recently made a change to address this issue. Please try creating an 
>> account again and post back here if you still encounter problems.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Monday, June 5, 2017 at 10:22:59 AM UTC-4, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi,
>>>
>>> If you actually created an account, could you send the email address of 
>>> that account *only to me* by clicking *Reply privately to author* on 
>>> this message? Also, please let me know your physical locale, as that will 
>>> help us determine if this is locale-related.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, June 5, 2017 at 1:57:43 AM UTC-4, Samuel Gjabel wrote:
>>>>
>>>> Same here! Trying to create a test ad account and nothing happened. 
>>>> IDK, but i think thats test accounts in a google and FB are the problem. 
>>>> Couse on the FB i got same result! :p 
>>>>
>>>> Dňa streda, 22. februára 2017 16:22:46 UTC+1 Peter Olvecký napísal(-a):
>>>>>
>>>>> Hi guys,
>>>>>
>>>>> I've just spent about an hour trying to setup the test account. It 
>>>>> doesn't work.
>>>>>
>>>>> Even though the page says it's for the creation of test accounts 
>>>>> ("Welcome to AdWords manager accounts (Test Account)") and the button at 
>>>>> the bottom of the page also reads "Create a test account", two things 
>>>>> happen when I hit the button:
>>>>>
>>>>> 1. The same form loads again (
>>>>> https://adwords.google.com/um/Welcome/Home?a=1=mt=0#ta)
>>>>> 2. I am being redirected to page for creation of production client 
>>>>> account (
>>>>> https://adwords.google.com/um/Welcome/Home?a=1=0=bb#ac)
>>>>>
>>>>> Can you please help me?
>>>>>
>>>>> Thank you,
>>>>> Peter
>>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/1f131982-d2cc-4d54-a82e-921dd707feb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Alejandro,

Sorry, my mistake. :) What I was thinking was that there's not much point 
to setting *numberResults = 0 *in most cases, but I completely forgot about 
the use case of simply getting the count of objects that match the 
predicate you specified (e.g., from totalNumEntries 
<https://developers.google.com/adwords/api/docs/reference/latest/AdGroupService.AdGroupPage#totalnumentries>),
 
where *numberResults=0* makes sense.

The underlying error on those requests are timeouts while reading data from 
your account. This can happen for a variety of reasons, including if there 
is a particularly high volume of requests against a particular account 
within a short time window. For example, on Nov 16, I see that anywhere 
from 200 to 9,000 requests per hour were issued against that account 
between 13:00 and 18:00 Pacific time.

In this situation, your best bet is to simply retry the request using some 
sort of retry policy (e.g., exponential backoff).

Thanks,
Josh, AdWords API Team

On Thursday, November 16, 2017 at 4:31:20 PM UTC-5, 
alejandro.grinb...@quanticmind.com wrote:
>
> Hi,
>
> According to the link you sent, the field (numberResults) must be greater 
> than* or equal *to 0. 
> Beyond that, i changed the value to use 100 (instead of 0) and i still get 
> the same error.
>
> Thanks,
> Alejandro
>
> On Thursday, November 16, 2017 at 11:49:12 AM UTC-3, Josh Radcliff 
> (AdWords API Team) wrote:
>>
>> Hi,
>>
>> I noticed that in your request, you are specifying the following in the 
>> *paging* element:
>>
>> 0
>> > xsi:type="xsd:int">0
>>
>> The numberResults 
>> <https://developers.google.com/adwords/api/docs/reference/v201710/CampaignService.Paging#numberresults>
>>  should 
>> be a value > 0, as it indicates how many results you want returned in each 
>> response (page). Could you try changing that value and let me know if you 
>> still encounter the error?
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, November 9, 2017 at 1:21:18 PM UTC-5, Shwetha Vastrad 
>> (AdWords API Team) wrote:
>>>
>>> Hi,
>>>
>>> Do you consistently encounter the InternalApiError 
>>> <https://developers.google.com/adwords/api/docs/common-errors#InternalApiError.UNEXPECTED_INTERNAL_API_ERROR>?
>>>  
>>> Could you tell me if this error is seen with just this service or other 
>>> services as well? This error is usually related to temporary resource 
>>> related issues in the AdWords API server and retrying the request should 
>>> help in getting a successful response. Could you also send over the 
>>> clientCustomerIds for which you encountered this error? Please use the 
>>> *Reply 
>>> privately to author* option 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/06c13f4a-7529-494d-bc6f-2541fc2159bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UNEXPECTED_INTERNAL_API_ERROR

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi,

I noticed that in your request, you are specifying the following in the 
*paging* element:

0
0

The numberResults 

 should 
be a value > 0, as it indicates how many results you want returned in each 
response (page). Could you try changing that value and let me know if you 
still encounter the error?

Thanks,
Josh, AdWords API Team

On Thursday, November 9, 2017 at 1:21:18 PM UTC-5, Shwetha Vastrad (AdWords 
API Team) wrote:
>
> Hi,
>
> Do you consistently encounter the InternalApiError 
> ?
>  
> Could you tell me if this error is seen with just this service or other 
> services as well? This error is usually related to temporary resource 
> related issues in the AdWords API server and retrying the request should 
> help in getting a successful response. Could you also send over the 
> clientCustomerIds for which you encountered this error? Please use the *Reply 
> privately to author* option 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/841d5e5e-9418-4595-a578-ef6c62ab3d57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords Express Data Discrepancies

['Josh Radcliff (AdWords API Team)' via AdWords API Forum]

Hi Joseph,

Please see my comments inline below.

Thanks,
Josh, AdWords API Team

On Tuesday, November 14, 2017 at 2:33:48 PM UTC-5, Joseph Collins wrote:
>
> Josh,
>
> Any update to this issue? I read the blog post about the AWX campaign 
> migration, but there is no mention of when this migration begins (perhaps 
> this issue is a symptom of an ongoing migration?) or when it is expected to 
> be completed.
>

The migration began a few weeks ago and is ongoing. I would expect it to 
continue as campaigns created by AWX (including *new* campaigns created by 
AWX) are moved to the new structure.

Do we need a specific version of the AdWords API to see these additional 
> campaigns in the campaign performance report? 
>

The change to expose the new EXPRESS/UNKNOWN campaigns in the AdWords API 
will apply to *all* available versions of the AdWords API (currently, 
versions >= v201702).
 

> There is also no mention of a migration cutover delay to help explain the 
> missing AWX performance as reported by our users. 
>

The change above is specifically to address the missing AWX performance 
data. Since the EXPRESS/UNKNOWN campaigns are not exposed in the AdWords 
API, users are currently unable to get performance data for the migrated 
campaigns. Once the fix is rolled out, you will be able to retrieve 
performance data for the entire history of the migrated campaigns to fill 
in the gaps you're currently seeing.


>
> On Monday, November 6, 2017 at 2:00:08 PM UTC-5, Josh Radcliff (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> We're aware of this issue and I'm actively looking into it. I'll provide 
>> an update as soon as I have more information.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Sunday, November 5, 2017 at 1:36:16 PM UTC-5, Joseph Collins wrote:
>>>
>>> A user of our system is seeing a significant disagreement between our 
>>> data and the AdWords Express interface. Below are user-provided screenshots 
>>> of the AdWords Express CID in question, its dashboard and our API request / 
>>> response.
>>>
>>>
>>> The mismatch between the 'Hayworth Equipment AWX' account description 
>>> and the 'Hayworth Equipment Sales' account label on the dashboard suggests 
>>> that this issue is due to user error (navigating to the wrong Express 
>>> dashboard), but the user is confident they are not making a mistake and 
>>> they report that these issues affect several of their Express accounts.
>>>
>>>
>>> For this specific account, you will notice that the API claims activity 
>>> stopped on October 6th, yet the dashboard shows ongoing activity. On the 
>>> days where both the dashboard and API show activity, the numbers do not 
>>> come close to agreeing.
>>>
>>>
>>> Any help in explaining or resolving this discrepancy would be greatly 
>>> appreciated.
>>>
>>>
>>>
>>> 
>>>
>>>
>>> *User-Provided Evidence*
>>>
>>>
>>>
>>> <https://lh3.googleusercontent.com/-lEfynuUWwxQ/Wf9V-2k-i6I/BlU/_Zs3wc2U6vEq4l407n_DTxWk1Aq8fTEzQCLcBGAs/s1600/CID.png>
>>>
>>>
>>> <https://lh3.googleusercontent.com/-9OIS42wKucA/Wf9WA0BamEI/BlY/M_QAFWJdfaQ4FOrS9kD9Oj1YOOuL8p5lwCLcBGAs/s1600/UI.png>
>>>
>>>
>>>
>>> 
>>>
>>> *Request*
>>>
>>> Headers
>>> (
>>> [0] => Authorization: Bearer X
>>> [1] => developerToken: X
>>> [2] => clientCustomerId: 5571930852
>>> [3] => includeZeroImpressions: true
>>> )
>>> 
>>> 
>>> Date
>>> Impressions
>>> Clicks
>>> Ctr
>>> Cost
>>> ConversionValue
>>> AverageCpc
>>> Conversions
>>> ConversionRate
>>> CostPerConversion
>>> ValuePerConversion
>>> AveragePosition
>>> 
>>> 20170906
>>> 20171104
>>> 
>>> 
>>> Report
>>> ACCOUNT_PERFORMANCE_REPORT
>>> CUSTOM_DATE
>>> GZIPPED_CSV
>>> 
>>>
>>>
>>> 
>>>
>>> *Response*
>>>