Re: Refresh token usage for downloading adhoc reports

[AMAR NAYAK]

Hi Josh,
Thanks for your reply.
I want to download an adgroup performance report for multiple client 
accounts under the MCC account.
Using client library I saw an example for downloading a report for a 
particular client account.
Is there an example somewhere that shows how to pull reports for multiple 
client accounts.
I am planning to use Java API .
Thanks,
-Amar


On Friday, August 29, 2014 6:23:19 AM UTC-7, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Amar,
>
> You need an OAuth *access token* for any API request, including reporting 
> requests -- see the OAuth2 Guide 
>  for an 
> overview of the basic steps for OAuth.
>
> If you want to construct reporting requests without a client library, 
> check out our Reporting Basics Guide 
> , 
> which includes information about the required headers and parameters for 
> reports.
>
> I'd encourage you to use one of our client libraries, if possible. They 
> handle all of the OAuth requests and responses for you and make using the 
> API much easier all around.
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, August 29, 2014 1:06:10 AM UTC-4, AMAR NAYAK wrote:
>>
>> Hi ,
>> I need to download couple of performance reports : Adgroup and Campaign 
>> performance report using adhoc reports.
>> I am going through the v201406 documentation and getting confuse over the 
>> usage of refresh token .
>> Do we need to use refresh token in adhoc reports ? If yes ,where should I 
>> use it?
>> Are there any examples of adhoc report downloads not using the client 
>> library ?
>>
>> Thanks,
>> -Amar
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/2e44892b-757d-4896-b03f-0e9fb47cfadd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Get Revenue PPC Report from API

[Oscar Martinez]

Hi,

I would like to know if it's possible to get the Revenue PPC Report from 
API. In this moment the person in charge need to login into AdWords and 
export it from there. But it would be useful to get it programatically 
through AdWords API.

I have seen the reports list, but I haven't found what report is the 
Revenue PPC.

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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/bb0858ef-9288-4dfe-b7a0-f3efbc49a7c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Keyword ID with no information in Keywords Performance Report

[Oscar Martinez M.]

Hi Josh,

Thank you for the information. Now it's clear. I'm not sure what is an User
List and I'm not sure if we need to retrieve information from it. I will
ask to marketing person, he should know.

Thank you for your help.


2014-08-29 6:53 GMT-06:00 Josh Radcliff (AdWords API Team) <
adwordsapiadvisor+j...@google.com>:

> Hi Oscar,
>
> Thanks for sending the info. The criteria ID you provided from the Click
> Performance Report is for a *UserList* criterion. You can see this is if
> you add the *CriteriaType* column to the Criteria Performance Report
>  and
> filter by (criterion) ID:
>
> SELECT Date, CampaignId, AdGroupId,* Id, CriteriaType* FROM
> CRITERIA_PERFORMANCE_REPORT WHERE *Id = xxx* DURING 20140827,20140827
>
> Keyword ID  Criteria Type  Impressions
> 789...  User List  6233
>
> The reason the *Click Performance Report* and the *Criteria Performance
> Report* both return this criterion ID instead of a keyword ID is that
> these reports are both single attribution reports
> ,
> so AdWords picks the most relevant criterion for each impression on those
> reports. Impressions in a *Display Network* campaign can be triggered by
> various criteria, not just keywords, which is why the API offers criterion
> type-specific reports such as the *Display Keywords Performance Report*,
> the *Age Range Performance Report*, etc.
>
> For user lists, there's the Audience Performance Report
> ,
> which returns the following for your campaign and ad group for that day.
>
> AudienceImpressions
> boomuserlist::6978660   179
> boomuserlist::8113860   6233
> boomuserlist::8113980   28
> Total   6440
>
> So for you particular use case, you'll have to keep in mind that the
> *CriteriaId* returned in the *Click Performance Report* is not going to
> always be for a keyword. To determine the type of criteria, you could:
>
>1. Run the *Click Performance Report* and capture the *CriteriaId*
>2. Run a *Criteria Performance Report*, filtered by your *CampaignId,
>AdGroupId, *and *Id* (criterion), and include *CriteriaType* in the
>list of selected fields. This report should use the same single attribution
>logic as the *Click Performance Report*.
>3. For each *Id/CriteriaType* pair returned in step 2, run the multiple
>attribution report
>
> 
>  that
>corresponds to the *CriteriaType* to gather more criterion
>type-specific information, if desired.
>
> Cheers,
> Josh, AdWords API Team
>
> On Thursday, August 28, 2014 3:07:36 PM UTC-4, Oscar Martinez wrote:
>>
>> Hi Josh,
>>
>> I sent you privately the information of the Google Click ID, Campaign
>> ID, Ad group ID, Keyword ID.
>>
>> Thank you,
>>
>> On Thursday, August 28, 2014 11:07:14 AM UTC-6, Oscar Martinez wrote:
>>>
>>> Hi,
>>>
>>> We are creating a small report for my company. We need to get Campaign
>>> Name, AdGroup Name and Keywords for a gclid. We have these steps:
>>>
>>> 1. Capture and save gclid.
>>> 2. CLICK_PERFORMANCE_REPORT to get CampaignId, AdGroupId and CriteriaId
>>> (Keyword ID) filtering by gclid and DateRange=TODAY (or Yesterday, if we
>>> saved the gclid yesterday).
>>> 3. KEYWORD_PERFORMANCE_REPORT to get KeywordText, CampaignName and
>>> AdGroupName, filtering by Id (Keyword ID) and DateRange=ALL_TIME.
>>>
>>> If we test using gclid from today, we get data on steps 2 and 3 (Good).
>>> If we test using gclid from yesterday we get results only on step 2, but
>>> step 3 is empty (Bad).
>>> We have 2 saved gclid from today and 1 saved gclid from yesterday. I can
>>> post the gclid information, but I'm not sure if it's a good idea to do it
>>> public.
>>>
>>> Pdata: The documentation in spanish is different to english version. In
>>> spanish we don't have the Click Report. We had to use a browser in English
>>> to see it.
>>>
>>> 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/fYd0H1KW98A/

Re: [4-6874000004292] Google Product Taxonomy vs Product Bidding Category

[Jonathan Wu]

This doesn't really help us since our customers are dictating what they
what their feed to look like and how to bid on it. We have to execute as
they specify.
We already made our own mapping between the taxonomies, but again, it's not
ideal since any change on either side will break it. If you guys could
provide a service that returns the product bidding category id based on a
google_product_category string, that would probably be ideal...


Regards,
Jonathan Wu


On Fri, Aug 29, 2014 at 7:12 AM,  wrote:

> Hi Jonathan,
>
> We have an idea for a work-around to this problem and I was wondering if
> you would be willing to give it a shot. The idea is to use ProductType
> -based
> bidding instead of ProductBiddingCategory
> -based
> bidding.
>
> *ProductType* is not tied to a predefined category taxonomy -- the
> categories are completely defined by the user when uploading his products
> to Merchant Center. As a result, bidding based on *ProductType* does not
> have the same category mismatch issues as *ProductBiddingCategory*-based
> bidding.
>
> The work-around is as follows:
>
>1. Update your existing Merchant Center products
> (either
>through the API or the UI), copying the Merchant Center
>*google_product_category* into the *product_type* for each product.
>For new products and ongoing changes to existing products, modify your feed
>upload so that you populate *product_type* with the same values that
>you use for *google_product_category*.
>2. Create your ProductPartitions
>
> 
> using ProductType
>
> 
>  dimensions
>that correspond to the *product_type* values in your feed.
>
> If you are relying on Merchant Center to automatically populate
> *google_product_category* based on the other attributes of your products,
> then step 1 above could be somewhat difficult, as you'll have to first
> upload your feed, then retrieve the products to find each one's
> *google_product_category*, and then upload your feed again with those
> values copied to the *product_type* field. On the other hand, if you are
> already specifying the *google_product_category* in your feeds, then this
> work-around should be relatively straightforward.
>
> If you're willing to give this a shot, please let me know. I would
> recommend trying this on a small Merchant Center account or a small subset
> of products in your Merchant Center account first just as a
> proof-of-concept. If all goes well then you can expand the approach to a
> larger set of products.
>
> Thanks,
> Josh, AdWords API Team
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and discussion group:
> http://googleadsdeveloper.blogspot.com/search/label/adwords_api
> https://developers.google.com/adwords/api/community/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> On 08/14/14 16:17:09 jonathan...@datapop.com wrote:
>
> Any update on this?
>
>
> Regards,
> Jonathan Wu
>
>
> On Fri, Aug 1, 2014 at 11:42 AM, Josh Radcliff (AdWords API Team) <
> adwordsapiadvisor+j...@google.com> wrote:
>
> Thanks for clarifying. I'm still waiting for some people to get back to me
> on the differences between the two category sets. I'll post an update as
> soon as I have more information.
>
> 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 a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/adwords-api/TwU51hJw8PE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> adwords-api+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

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

Re: Any plans for a JavaScript library?

[Jerome Wagner]

OK thanks for the input. "CPU bound" can indeed be a difficulty here.

Thanks for the link.

Le vendredi 29 août 2014 19:56:26 UTC+2, Jason Stedman a écrit :
>
> Let's not turn this into a debate about node, but to provide specific 
> examples of what I refer to:
>
> For some good advice describing the challenges read this stackexchange 
> thread all the way through(it's only 5 posts): 
> http://programmers.stackexchange.com/questions/205232/is-node-js-a-good-fit-for-background-processing
>
> For an example use case that node probably wouldn't be great for, consider 
> a bidding or budgeting algorithm being processed for each campaign, 
> adgroup, placement, device target, location target, keyword, and ad every 
> night for hundreds of accounts, some of them with over 100 campaigns and 
> thousands of keywords. This is necessarily concurrent(likely distributed), 
> otherwise you will never finish in time. It is not necessarily synchronous, 
> that would depend on the algorithm itself, but it will be CPU bound(heavy). 
>
>
> On Friday, August 29, 2014 11:48:31 AM UTC-4, Jerome Wagner wrote:
>>
>> Hello,
>>
>> by "it seems people have lots of headaches any time they want to do 
>> heavy, necessarily concurrent processing" you mean heavy *synchronous* 
>> processing ? otherwise can you explain to me a bit more the use case you 
>> mention ?
>>
>> I still don't know if I want to push something google has more or less 
>> abandoned for the adwords API ("no plans at the moment since 2011")
>>
>> Starting from the google code base from 2011 could maybe help such a 
>> project become a first class client one day ; at least it seem to have a 
>> lot of google code requirements in it (using google closure for example). 
>> The fact that it is browser compatible is a + I think even if it is only 
>> through a proxy because of crossdomain issues.
>>
>> It is hard to decide if and how to start such a project while at the same 
>> time avoiding the "official javascript client doom", meaning that 
>>
>> 1/ you invest a lot of time and effort into putting up such a non 
>> official client 
>> 2/ google decides to publish an official javascript client on its own 
>> which has nothing to do with your now "rogue" client
>> 3/ you duplicate lots of efforts and lose energy
>>
>> I see 2 ways of approaching this while not losing too much time :
>>
>>  - (1) automatically generate the javascript binding out of the wsdl 
>> files ; and then add syntax sugar over this (node-soap could certainly help 
>> here)
>>  - (2) manage to automatically convert the wsdl into a json-schema 
>> bindings compatible with https://developers.google.com/discovery/ + add 
>> an adapter to the official node client 
>> https://github.com/google/google-api-nodejs-client/ so that it can work 
>> with the adwords SOAP API.
>>
>> if (2) hasn't been done it is maybe because there are fundamental 
>> differences between the SOAP bindings and what can be expressed via json 
>> schema but it is maybe worth a check.
>>
>> if you have ideas/feedback your are welcome.
>>
>> I'll post here after I decide if I want to pursue this or not (might take 
>> some time since I did not expect the non availability of a javascript 
>> client for adwords so I have to reconsider my overall planning and might go 
>> with one of the existing clients)
>>
>> Thanks
>> Jerome
>>
>>
>>
>>
>>
>> Le vendredi 29 août 2014 16:58:51 UTC+2, Jason Stedman a écrit :
>>>
>>> Jerome,
>>>
>>> Both the API and the JavaScript ecosystem have changed drastically since 
>>> 2011. I would think you might have a better chance starting over fresh at 
>>> this point using a node module to integrate with the AdWords SOAP services 
>>> directly.
>>>
>>> This one looks pretty stable and recently maintained : 
>>> https://github.com/vpulim/node-soap
>>>
>>> I have general reservations about node as a platform for running an 
>>> AdWords integration on. 
>>>
>>> It is very typical to have long running operations when working with 
>>> AdWords and to handle integration of very large datasets which is not 
>>> something I typically think of as a use case for node. Additionally, an 
>>> online marketing firm of any size would require things like overnight batch 
>>> processing, data integration, secondary analytics and unified reports. 
>>> These are things that have lots of support in more traditional enterprise 
>>> platforms like Java which already has a client library for AdWords. 
>>>
>>> Node is amazing at very high throughput of small messages, but it seems 
>>> people have lots of headaches any time they want to do heavy, necessarily 
>>> concurrent processing.
>>>
>>> That being said we use node at my day job and have been looking for a 
>>> reason to get back into coding for AdWords. I would be willing to 
>>> contribute to an opensource project like this with you. 
>>>
>>> On Thursday, August 28, 2014 11:49:54 AM UTC-4, Jerome Wagner wrote:

 Hello, 

 I understand that my best bet 

Re: Any plans for a JavaScript library?

[Jason Stedman]

Let's not turn this into a debate about node, but to provide specific 
examples of what I refer to:

For some good advice describing the challenges read this stackexchange 
thread all the way through(it's only 5 
posts): 
http://programmers.stackexchange.com/questions/205232/is-node-js-a-good-fit-for-background-processing

For an example use case that node probably wouldn't be great for, consider 
a bidding or budgeting algorithm being processed for each campaign, 
adgroup, placement, device target, location target, keyword, and ad every 
night for hundreds of accounts, some of them with over 100 campaigns and 
thousands of keywords. This is necessarily concurrent(likely distributed), 
otherwise you will never finish in time. It is not necessarily synchronous, 
that would depend on the algorithm itself, but it will be CPU bound(heavy). 


On Friday, August 29, 2014 11:48:31 AM UTC-4, Jerome Wagner wrote:
>
> Hello,
>
> by "it seems people have lots of headaches any time they want to do heavy, 
> necessarily concurrent processing" you mean heavy *synchronous* processing 
> ? otherwise can you explain to me a bit more the use case you mention ?
>
> I still don't know if I want to push something google has more or less 
> abandoned for the adwords API ("no plans at the moment since 2011")
>
> Starting from the google code base from 2011 could maybe help such a 
> project become a first class client one day ; at least it seem to have a 
> lot of google code requirements in it (using google closure for example). 
> The fact that it is browser compatible is a + I think even if it is only 
> through a proxy because of crossdomain issues.
>
> It is hard to decide if and how to start such a project while at the same 
> time avoiding the "official javascript client doom", meaning that 
>
> 1/ you invest a lot of time and effort into putting up such a non official 
> client 
> 2/ google decides to publish an official javascript client on its own 
> which has nothing to do with your now "rogue" client
> 3/ you duplicate lots of efforts and lose energy
>
> I see 2 ways of approaching this while not losing too much time :
>
>  - (1) automatically generate the javascript binding out of the wsdl files 
> ; and then add syntax sugar over this (node-soap could certainly help here)
>  - (2) manage to automatically convert the wsdl into a json-schema 
> bindings compatible with https://developers.google.com/discovery/ + add 
> an adapter to the official node client 
> https://github.com/google/google-api-nodejs-client/ so that it can work 
> with the adwords SOAP API.
>
> if (2) hasn't been done it is maybe because there are fundamental 
> differences between the SOAP bindings and what can be expressed via json 
> schema but it is maybe worth a check.
>
> if you have ideas/feedback your are welcome.
>
> I'll post here after I decide if I want to pursue this or not (might take 
> some time since I did not expect the non availability of a javascript 
> client for adwords so I have to reconsider my overall planning and might go 
> with one of the existing clients)
>
> Thanks
> Jerome
>
>
>
>
>
> Le vendredi 29 août 2014 16:58:51 UTC+2, Jason Stedman a écrit :
>>
>> Jerome,
>>
>> Both the API and the JavaScript ecosystem have changed drastically since 
>> 2011. I would think you might have a better chance starting over fresh at 
>> this point using a node module to integrate with the AdWords SOAP services 
>> directly.
>>
>> This one looks pretty stable and recently maintained : 
>> https://github.com/vpulim/node-soap
>>
>> I have general reservations about node as a platform for running an 
>> AdWords integration on. 
>>
>> It is very typical to have long running operations when working with 
>> AdWords and to handle integration of very large datasets which is not 
>> something I typically think of as a use case for node. Additionally, an 
>> online marketing firm of any size would require things like overnight batch 
>> processing, data integration, secondary analytics and unified reports. 
>> These are things that have lots of support in more traditional enterprise 
>> platforms like Java which already has a client library for AdWords. 
>>
>> Node is amazing at very high throughput of small messages, but it seems 
>> people have lots of headaches any time they want to do heavy, necessarily 
>> concurrent processing.
>>
>> That being said we use node at my day job and have been looking for a 
>> reason to get back into coding for AdWords. I would be willing to 
>> contribute to an opensource project like this with you. 
>>
>> On Thursday, August 28, 2014 11:49:54 AM UTC-4, Jerome Wagner wrote:
>>>
>>> Hello, 
>>>
>>> I understand that my best bet if I want to access the adwords API from 
>>> node.js is to dig into the old 
>>> https://code.google.com/p/google-api-adwords-js/ that used to work on 
>>> the browser and adapt it 
>>>  * for node.js (it seems that goog. has been adapted for node.js in 2013)
>>>  * for the newer v201

Re: Changing the OAuth2 client secret

[Josh Radcliff (AdWords API Team)]

Hi Rob,

I'm happy to report that you can now reset the client secret in the new Google 
Developers Console  as well by 
clicking the *Reset secret* button.

Cheers,
Josh, AdWords API Team

On Tuesday, June 10, 2014 4:09:44 AM UTC-4, Rob wrote:
>
> Thanks Josh, I wasn't aware of the original console link. Resetting the 
> client secret there works perfectly.
>
> On Monday, 9 June 2014 21:48:35 UTC+1, Josh Radcliff (AdWords API Team) 
> wrote:
>>
>> Hi Rob,
>>
>> Ray or I will let you know as soon as we have any updates from the 
>> relevant teams, but for the time being if you need to reset a 
>> *client_secret* you can do so from the prior version of developer 
>> console. To get to the prior version, click the *Return to original 
>> console* link at the bottom of 
>> https://console.developers.google.com/project.
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Monday, June 9, 2014 4:14:52 AM UTC-4, Rob wrote:
>>>
>>> Hi Ray,
>>>
>>> So far my post on that forum has gained a couple of votes and comments 
>>> but nothing from the Google team.
>>>
>>> This is a serious security request, as we cannot change what is 
>>> effectively our application password. That could result in leaks or damage 
>>> to your clients' data if it's not addressed. Please could you escalate this 
>>> if at all possible.
>>>
>>> On Friday, 16 May 2014 13:25:16 UTC+1, Ray Tsang (AdWords API Team) 
>>> wrote:

 Thanks Rob.  I've also notified the relevant teams.

 Cheers,

 Ray

 On Thursday, May 15, 2014 3:10:34 PM UTC+2, Rob wrote:
>
> Thanks Ray, I've posted a question there...
>
>
> http://stackoverflow.com/questions/23679229/generating-a-new-client-secret
>
> Rob.
>
> On Thursday, 15 May 2014 11:59:04 UTC+1, Ray Tsang (AdWords API Team) 
> wrote:
>>
>> Rob,
>>
>> I've noted this down.  However, I'm only able to help resolving 
>> AdWords API issues.  This is more related to the accounts and 
>> authentications  in general.
>>
>> Could I trouble you to reach out via Google Accounts API related 
>> forums ?
>>
>> Thanks,
>>
>> Ray
>>
>> On Wednesday, May 14, 2014 6:51:44 PM UTC+2, Rob wrote:
>>>
>>> Note that Bing Ads allow changing the client secret for a given ID 
>>> in their Developer Center... it shouldn't be that difficult for Google!
>>>
>>> On Wednesday, 14 May 2014 17:37:19 UTC+1, Rob wrote:

 Hi,

 Is there a way to change the OAuth2 client secret without changing 
 the client ID?

 From what I can see, the only option is to generate a new client ID 
 and secret together, meaning any refresh tokens obtained against the 
 old 
 client ID are effectively useless.

 If that is the case, what's the point of having a separate ID and 
 secret? Surely they should just be a single property of the 
 application.

 This appears to be a design flaw with separating authentication 
 from authorization. I can't periodically change the client secret as a 
 security best practice (like changing your password on a regular 
 basis) 
 without having to get all my clients to re-authorize me.

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/1d27524c-3da6-4b24-9059-f32ed691d056%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Any plans for a JavaScript library?

[Jerome Wagner]

Hello,

by "it seems people have lots of headaches any time they want to do heavy, 
necessarily concurrent processing" you mean heavy *synchronous* processing 
? otherwise can you explain to me a bit more the use case you mention ?

I still don't know if I want to push something google has more or less 
abandoned for the adwords API ("no plans at the moment since 2011")

Starting from the google code base from 2011 could maybe help such a 
project become a first class client one day ; at least it seem to have a 
lot of google code requirements in it (using google closure for example). 
The fact that it is browser compatible is a + I think even if it is only 
through a proxy because of crossdomain issues.

It is hard to decide if and how to start such a project while at the same 
time avoiding the "official javascript client doom", meaning that 

1/ you invest a lot of time and effort into putting up such a non official 
client 
2/ google decides to publish an official javascript client on its own which 
has nothing to do with your now "rogue" client
3/ you duplicate lots of efforts and lose energy

I see 2 ways of approaching this while not losing too much time :

 - (1) automatically generate the javascript binding out of the wsdl files 
; and then add syntax sugar over this (node-soap could certainly help here)
 - (2) manage to automatically convert the wsdl into a json-schema bindings 
compatible with https://developers.google.com/discovery/ + add an adapter 
to the official node 
client https://github.com/google/google-api-nodejs-client/ so that it can 
work with the adwords SOAP API.

if (2) hasn't been done it is maybe because there are fundamental 
differences between the SOAP bindings and what can be expressed via json 
schema but it is maybe worth a check.

if you have ideas/feedback your are welcome.

I'll post here after I decide if I want to pursue this or not (might take 
some time since I did not expect the non availability of a javascript 
client for adwords so I have to reconsider my overall planning and might go 
with one of the existing clients)

Thanks
Jerome





Le vendredi 29 août 2014 16:58:51 UTC+2, Jason Stedman a écrit :
>
> Jerome,
>
> Both the API and the JavaScript ecosystem have changed drastically since 
> 2011. I would think you might have a better chance starting over fresh at 
> this point using a node module to integrate with the AdWords SOAP services 
> directly.
>
> This one looks pretty stable and recently maintained : 
> https://github.com/vpulim/node-soap
>
> I have general reservations about node as a platform for running an 
> AdWords integration on. 
>
> It is very typical to have long running operations when working with 
> AdWords and to handle integration of very large datasets which is not 
> something I typically think of as a use case for node. Additionally, an 
> online marketing firm of any size would require things like overnight batch 
> processing, data integration, secondary analytics and unified reports. 
> These are things that have lots of support in more traditional enterprise 
> platforms like Java which already has a client library for AdWords. 
>
> Node is amazing at very high throughput of small messages, but it seems 
> people have lots of headaches any time they want to do heavy, necessarily 
> concurrent processing.
>
> That being said we use node at my day job and have been looking for a 
> reason to get back into coding for AdWords. I would be willing to 
> contribute to an opensource project like this with you. 
>
> On Thursday, August 28, 2014 11:49:54 AM UTC-4, Jerome Wagner wrote:
>>
>> Hello, 
>>
>> I understand that my best bet if I want to access the adwords API from 
>> node.js is to dig into the old 
>> https://code.google.com/p/google-api-adwords-js/ that used to work on 
>> the browser and adapt it 
>>  * for node.js (it seems that goog. has been adapted for node.js in 2013)
>>  * for the newer v201406 API
>>
>> how hard do you think that would be ? 
>>
>> are there any plans to retrofit the adwords API into the google api 
>> discovery service so that I could use its node.js client implementation ?
>>
>> --
>> Jerome
>>
>> Le mardi 8 avril 2014 15:25:41 UTC+2, Danial Klimkin a écrit :
>>>
>>> Hello Rasmus,
>>>
>>>
>>> No, we don't have any plans for JS library at the moment.
>>>
>>>
>>> -Danial, AdWords API Team.
>>>
>>>
>>> On Monday, April 7, 2014 11:44:37 PM UTC+4, Rasmus Ladekjær Pedersen 
>>> wrote:

 Hi there,

 do you have any plans for a JavaScript library?

 With all the Node.js going on, I believe we are a lot wanting a 
 JavaScript library for the Google AdWords API.

>>>

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

Re: Issue with uploading large amounts of data using MutateJobService

[Oliver]

Anash,

Can you please clarify what the documentation (I pointed out earlier) is 
referring to when it says:

>> try to reduce the likelihood of jobs operating on the same AdGroups at 
the same time

Is creating multiple Ads within the same adgroup using MJS something that 
the above is saying shouldn't be done?





On Friday, August 29, 2014 4:37:46 PM UTC+1, Anash P. Oommen (AdWords API 
Team) wrote:
>
> Hi Alan, Oliver,
>
> We have identified the issue at our end, it's a flaky connection to our 
> datastore when creating and reading jobs. We are working on a fix, but 
> meanwhile you can put a retry loop around your code to resubmit the job. 
> MJS can handle the batch size you are providing, so this error needn't be a 
> limiting factor when deciding whether or not to use MJS.
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Friday, August 29, 2014 4:21:35 AM UTC-4, Oliver wrote:
>>
>> Thanks Alan for the update. Let us know if the changes you make will have 
>> an effect.
>>
>> Hopefully also the API team will shed some light on this.
>>
>> Oliver
>>
>>
>> On Friday, August 29, 2014 9:14:44 AM UTC+1, Alan Coleman wrote:
>>>
>>> Hi Oliver,
>>>
>>> Thanks for getting involved, that's an interesting find in the 
>>> documentation that I haven't seen before. I started this post about the 
>>> UNEXPECTED_INTERNAL_API_ERROR which I'm sometimes receiving when trying 
>>> bulk uploads using MJS - Hopefully this is being looked into.
>>>
>>> However there has been issues with MJS nearly finishing my jobs but then 
>>> just stopping in a *deadlock-like condition*. The SOAP Logs report back 
>>> as normal and indicate that the job is *pending*.
>>>
>>> There's no way round using the same customerId as that would defeat the 
>>> object of what we're trying to achieve. 
>>>
>>> If I use adding TextAds as an example, the array that I currently pass 
>>> to the MJS is constructed in AdGroup order, which is how it comes out of my 
>>> db, and it's not unusual to be trying to add several TextAds in each 
>>> AdGroup.
>>>
>>> I'm chunking my ordered array into arrays of 1000 and then looping round 
>>> through MJS to create jobs of that size, so it's possible that a concurrent 
>>> job may contain the same AdGroup if the TextAds for that AdGroup have been 
>>> chunked half way through. I think that is what the following means:
>>>
>>> *>> jobs operating on the same AdGroups*
>>>
>>> It may be a long shot but a good place for me to start would be to 
>>> ensure that a particular Adgroup can only appear in one job.
>>>
>>> With regards to:
>>>
>>> Is the creation of multiple Ads within the same AdGroup considered as 
 operating on the adgroup itself?
 If so, is this implying that we shouldn't attempt to create multiple 
 Ads within the same adgroup using MJS?
>>>
>>>
>>> I may be wrong, but I've never experienced any problems with writing 
>>> multiple TextAds or Keywords to a single AdGroup until I started using MJS, 
>>> and even then it's only when maintaining large job sizes.
>>>
>>> As I said earlier, probably unrelated to the 
>>> UNEXPECTED_INTERNAL_API_ERROR, but I'm going to make the subtle changes to 
>>> constructing my MJS anyway.
>>>
>>> Thanks again,
>>>
>>>
>>>
>>> On Thursday, August 28, 2014 5:09:18 PM UTC+1, Oliver wrote:

 I'm about to do something similar to what Alan is doing and, hence, why 
 I'm also interested in this.

 I see on this page:
 https://developers.google.com/adwords/api/docs/guides/batch-processing

 there is a paragraph that says:


- 

When submitting a lot of concurrent jobs for the same customerId, 
try to reduce the likelihood of jobs operating on the same AdGroups at 
 the 
same time, while maintaining large job sizes. Many unfinished jobs 
 (with 
status of PENDING or PROCESSING) that try to mutate the same set of 
AdGroups may lead to deadlock-like conditions resulting in severe 
 slow-down 
and even job failures.

 I don't know exactly what is being referred to by this term:

 >> jobs operating on the same AdGroups

 Is the creation of multiple Ads within the same AdGroup considered as 
 operating on the adgroup itself?

 If so, is this implying that we shouldn't attempt to create multiple 
 Ads within the same adgroup using MJS?

 Oliver



 On Thursday, August 28, 2014 10:39:40 AM UTC+1, Alan Coleman wrote:
>
> Thanks Anash,
>
> I caught another such error in my SOAP Log this morning, although this 
> time the error returned before any results.
>
> I'd really appreciate it if you could take a quick look and let me 
> know what you think.
>
> Many thanks.
>
> HTTP/1.1 500 Internal Server Error
> Content-Type: text/xml; charset=UTF-8
> Date: Thu, 28 Aug 2014 09:28:48 GMT
> Expires: Thu, 28 Aug 2014 09:28:48 GMT

Re: Issue with uploading large amounts of data using MutateJobService

[Anash P. Oommen (AdWords API Team)]

Hi Alan, Oliver,

We have identified the issue at our end, it's a flaky connection to our 
datastore when creating and reading jobs. We are working on a fix, but 
meanwhile you can put a retry loop around your code to resubmit the job. 
MJS can handle the batch size you are providing, so this error needn't be a 
limiting factor when deciding whether or not to use MJS.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

On Friday, August 29, 2014 4:21:35 AM UTC-4, Oliver wrote:
>
> Thanks Alan for the update. Let us know if the changes you make will have 
> an effect.
>
> Hopefully also the API team will shed some light on this.
>
> Oliver
>
>
> On Friday, August 29, 2014 9:14:44 AM UTC+1, Alan Coleman wrote:
>>
>> Hi Oliver,
>>
>> Thanks for getting involved, that's an interesting find in the 
>> documentation that I haven't seen before. I started this post about the 
>> UNEXPECTED_INTERNAL_API_ERROR which I'm sometimes receiving when trying 
>> bulk uploads using MJS - Hopefully this is being looked into.
>>
>> However there has been issues with MJS nearly finishing my jobs but then 
>> just stopping in a *deadlock-like condition*. The SOAP Logs report back 
>> as normal and indicate that the job is *pending*.
>>
>> There's no way round using the same customerId as that would defeat the 
>> object of what we're trying to achieve. 
>>
>> If I use adding TextAds as an example, the array that I currently pass to 
>> the MJS is constructed in AdGroup order, which is how it comes out of my 
>> db, and it's not unusual to be trying to add several TextAds in each 
>> AdGroup.
>>
>> I'm chunking my ordered array into arrays of 1000 and then looping round 
>> through MJS to create jobs of that size, so it's possible that a concurrent 
>> job may contain the same AdGroup if the TextAds for that AdGroup have been 
>> chunked half way through. I think that is what the following means:
>>
>> *>> jobs operating on the same AdGroups*
>>
>> It may be a long shot but a good place for me to start would be to ensure 
>> that a particular Adgroup can only appear in one job.
>>
>> With regards to:
>>
>> Is the creation of multiple Ads within the same AdGroup considered as 
>>> operating on the adgroup itself?
>>> If so, is this implying that we shouldn't attempt to create multiple Ads 
>>> within the same adgroup using MJS?
>>
>>
>> I may be wrong, but I've never experienced any problems with writing 
>> multiple TextAds or Keywords to a single AdGroup until I started using MJS, 
>> and even then it's only when maintaining large job sizes.
>>
>> As I said earlier, probably unrelated to the 
>> UNEXPECTED_INTERNAL_API_ERROR, but I'm going to make the subtle changes to 
>> constructing my MJS anyway.
>>
>> Thanks again,
>>
>>
>>
>> On Thursday, August 28, 2014 5:09:18 PM UTC+1, Oliver wrote:
>>>
>>> I'm about to do something similar to what Alan is doing and, hence, why 
>>> I'm also interested in this.
>>>
>>> I see on this page:
>>> https://developers.google.com/adwords/api/docs/guides/batch-processing
>>>
>>> there is a paragraph that says:
>>>
>>>
>>>- 
>>>
>>>When submitting a lot of concurrent jobs for the same customerId, 
>>>try to reduce the likelihood of jobs operating on the same AdGroups at 
>>> the 
>>>same time, while maintaining large job sizes. Many unfinished jobs (with 
>>>status of PENDING or PROCESSING) that try to mutate the same set of 
>>>AdGroups may lead to deadlock-like conditions resulting in severe 
>>> slow-down 
>>>and even job failures.
>>>
>>> I don't know exactly what is being referred to by this term:
>>>
>>> >> jobs operating on the same AdGroups
>>>
>>> Is the creation of multiple Ads within the same AdGroup considered as 
>>> operating on the adgroup itself?
>>>
>>> If so, is this implying that we shouldn't attempt to create multiple Ads 
>>> within the same adgroup using MJS?
>>>
>>> Oliver
>>>
>>>
>>>
>>> On Thursday, August 28, 2014 10:39:40 AM UTC+1, Alan Coleman wrote:

 Thanks Anash,

 I caught another such error in my SOAP Log this morning, although this 
 time the error returned before any results.

 I'd really appreciate it if you could take a quick look and let me know 
 what you think.

 Many thanks.

 HTTP/1.1 500 Internal Server Error
 Content-Type: text/xml; charset=UTF-8
 Date: Thu, 28 Aug 2014 09:28:48 GMT
 Expires: Thu, 28 Aug 2014 09:28:48 GMT
 Cache-Control: private, max-age=0
 X-Content-Type-Options: nosniff
 X-Frame-Options: SAMEORIGIN
 X-XSS-Protection: 1; mode=block
 Server: GSE
 Transfer-Encoding: chunked

 
 http://schemas.xmlsoap.org/soap/envelope/";>
   
 https://adwords.google.com/api/adwords/cm/v201402";>
   000501ad297264b00a4254a6960046b8
   MutateJobService
   mutate
   0
   8909
 
   
   
 
   soap:Server
   [InternalApiError.UNEXPECTED_INTERN

Re: Missing feedItems

[Anash P. Oommen (AdWords API Team)]

Looks like we also had a documentation issue that suggested you could use 
CampaignID and AdgroupId. We will get this fixed to avoid confusion in the 
future.

Cheers,
Anash

On Thursday, August 28, 2014 3:52:09 AM UTC-4, GrueneOrchidee wrote:
>
> If I use the fields TargetingAdGroupId and TargetingCampaignId instead of 
> CampaignID and AdgroupId for filtering, the problem is solved.
>
> Thank you!
>
> Am Donnerstag, 21. August 2014 11:20:46 UTC+2 schrieb GrueneOrchidee:
>>
>> I make a request by using the CustomerSyncService for getting changes of 
>> one customer, restricted by one feedId. The request returns 10 ids of 
>> changed feedItems. If I use the FeedItemService for getting these 
>> feedItems, only 7 of them will be returned. What about the missing 3 
>> feedItems (feedItemIds: 803011504, 190106556, 190106436)?
>>
>> I use the java library adwords-appengine, version 1.30.0
>>
>> Here are my requests and the answer of the CustomerSyncService:
>>
>> http://schemas.xmlsoap.org/soap/envelope/";>
>> 
>> https://adwords.google.com/api/adwords/ch/v201406";>
>> https://adwords.google.com/api/adwords/cm/v201406
>> ">false
>> https://adwords.google.com/api/adwords/cm/v201406";>ngts 
>> (AwApi-Java, AdWords-AppEngine/1.30.0, Common-Java/1.30.0, JAX-WS/Unknown, 
>> Java/1.7.0, maven)
>> https://adwords.google.com/api/adwords/cm/v201406
>> ">XXX
>> https://adwords.google.com/api/adwords/cm/v201406
>> ">1904772276
>> 
>> 
>> 
>> https://adwords.google.com/api/adwords/cm/v201406"; 
>> xmlns:ns2="https://adwords.google.com/api/adwords/ch/v201406"; xmlns:ns3="
>> https://adwords.google.com/api/adwords/rm/v201406"; xmlns:ns4="
>> https://adwords.google.com/api/adwords/o/v201406"; xmlns:ns5="
>> https://adwords.google.com/api/adwords/mcm/v201406"; xmlns:ns6="
>> https://adwords.google.com/api/adwords/express/v201406"; xmlns:ns7="
>> https://adwords.google.com/api/adwords/billing/v201406";>
>> 
>> 
>> 20140820 01 Europe/Berlin
>> 20140821 01 Europe/Berlin
>> 
>> 1668876
>> 
>> 
>> 
>> 
>>
>> SOAP Response:
>> http://schemas.xmlsoap.org/soap/envelope/";>
>> 
>> https://adwords.google.com/api/adwords/cm/v201406"; xmlns:ns2="
>> https://adwords.google.com/api/adwords/ch/v201406";>
>> 0005011fb73d86f00adb45a554007582
>> CustomerSyncService
>> get
>> 0
>> 360
>> 
>> 
>> 
>> https://adwords.google.com/api/adwords/cm/v201406"; 
>> xmlns:ns2="https://adwords.google.com/api/adwords/ch/v201406";>
>> 
>> 
>> 1668876
>> FIELDS_UNCHANGED
>> 44168796
>> 803011480
>> 44171796
>> 803011504
>> 44166036
>> 190106556
>> 803011471
>> 190106436
>> 803011486
>> 803011516
>> 
>> 20140821 01 
>> Europe/Berlin
>> 
>> 
>> 
>> 
>>
>> http://schemas.xmlsoap.org/soap/envelope/";>
>> 
>> https://adwords.google.com/api/adwords/cm/v201406";>
>> false
>> ngts (AwApi-Java, AdWords-AppEngine/1.30.0, 
>> Common-Java/1.30.0, JAX-WS/Unknown, Java/1.7.0, maven)
>> XX
>> 1904772276
>> 
>> 
>> 
>> https://adwords.google.com/api/adwords/cm/v201406"; 
>> xmlns:ns2="https://adwords.google.com/api/adwords/express/v201406"; 
>> xmlns:ns3="https://adwords.google.com/api/adwords/rm/v201406"; xmlns:ns4="
>> https://adwords.google.com/api/adwords/mcm/v201406"; xmlns:ns5="
>> https://adwords.google.com/api/adwords/billing/v201406"; xmlns:ns6="
>> https://adwords.google.com/api/adwords/o/v201406"; xmlns:ns7="
>> https://adwords.google.com/api/adwords/ch/v201406";>
>> 
>> AdGroupId
>> AttributeValues
>> CampaignId
>> DevicePreference
>> EndTime
>> FeedId
>> FeedItemId
>> KeywordMatchType
>> KeywordText
>> Scheduling
>> StartTime
>> Status
>> UrlCustomParameters
>> ValidationDetails
>> 
>> FeedItemId
>> IN
>> 44168796
>> 803011480
>> 44171796
>> 803011504
>> 44166036
>> 190106556
>> 803011471
>> 190106436
>> 803011486
>> 803011516
>> 
>> 
>> 20140820
>> 20140821
>> 
>> 
>> FeedId
>> ASCENDING
>> 
>> 
>> 
>> 
>> 
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ea2df5ce-0fc2-4db3-b8d3-480980ee0197%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shuld I choice reporttype about ProductPartition.

[Anash P. Oommen (AdWords API Team)]

Hi,

You can get the same data from either Criteria performance or product 
partition report.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

On Thursday, August 28, 2014 5:01:32 AM UTC-4, 照沼領 wrote:
>
> Hi,
>
> I'll want to migrate API version to v201406 and retrieve ProductPartition 
> report.
>
> In ReportType page. There are "Criteria Performance" and "Product 
> Partition" at Available Reports.
>
> Q1, Should I use "Product Partition" ReportType for retrieving data?
>
> Q2, Can I retrieve "Product Partition" report from "Criteria Performance" ?
>
> https://developers.google.com/adwords/api/docs/appendix/reports?hl=en
>
> Best 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/cfb6fb72-7cf4-42f6-b8e5-e2bb4c289ab8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting the Change History via the API

[Josh Radcliff (AdWords API Team)]

Hi Danilo,

I believe this was already filed as a feature request, but I went ahead and 
filed another request on your behalf just now. I'll reply to this thread 
when I have an update.

Cheers,
Josh, AdWords API Team

On Friday, August 29, 2014 10:44:25 AM UTC-4, Danilo Bargen wrote:
>
> Hi
>
> On Friday, August 29, 2014 3:47:03 PM UTC+2, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> The API does not provide user information about changes at this time. 
>> Anash's previous post regarding CustomerSyncService 
>>  
>> covers 
>> the only change history-related features of the API.
>>
>
> That's what I feared, thanks for the information. Too bad that Google 
> don't eat their own dogfood regarding the APIs (hello there Amazon)...
>
> Is there a way to make this a feature request?
>
> Cheers
> Danilo
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/00438b50-51a7-4b53-a0a3-06ef96214f3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Auto-tagging via API

[GDZ]

Thank you Josh!



On Friday, August 29, 2014 9:11:55 AM UTC-4, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> As described in our Managing Customer Accounts guide 
> ,
>  
> you can use the *CustomerService* to set an account's autoTaggingEnabled 
> 
>  attribute.
>
> Cheers,
> Josh, AdWords API Team
>
> On Thursday, August 28, 2014 11:56:40 AM UTC-4, GDZ wrote:
>>
>> As far as I understand, account's auto-tagging field is not available in 
>> API. Is it possible to use adwords scripts to be able to modify it?
>>
>> Thank you,
>> GDZ 
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/89178706-888e-44aa-a9fe-fa83a82da49d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Any plans for a JavaScript library?

[Jason Stedman]

Jerome,

Both the API and the JavaScript ecosystem have changed drastically since 
2011. I would think you might have a better chance starting over fresh at 
this point using a node module to integrate with the AdWords SOAP services 
directly.

This one looks pretty stable and recently maintained 
: https://github.com/vpulim/node-soap

I have general reservations about node as a platform for running an AdWords 
integration on. 

It is very typical to have long running operations when working with 
AdWords and to handle integration of very large datasets which is not 
something I typically think of as a use case for node. Additionally, an 
online marketing firm of any size would require things like overnight batch 
processing, data integration, secondary analytics and unified reports. 
These are things that have lots of support in more traditional enterprise 
platforms like Java which already has a client library for AdWords. 

Node is amazing at very high throughput of small messages, but it seems 
people have lots of headaches any time they want to do heavy, necessarily 
concurrent processing.

That being said we use node at my day job and have been looking for a 
reason to get back into coding for AdWords. I would be willing to 
contribute to an opensource project like this with you. 

On Thursday, August 28, 2014 11:49:54 AM UTC-4, Jerome Wagner wrote:
>
> Hello, 
>
> I understand that my best bet if I want to access the adwords API from 
> node.js is to dig into the old 
> https://code.google.com/p/google-api-adwords-js/ that used to work on the 
> browser and adapt it 
>  * for node.js (it seems that goog. has been adapted for node.js in 2013)
>  * for the newer v201406 API
>
> how hard do you think that would be ? 
>
> are there any plans to retrofit the adwords API into the google api 
> discovery service so that I could use its node.js client implementation ?
>
> --
> Jerome
>
> Le mardi 8 avril 2014 15:25:41 UTC+2, Danial Klimkin a écrit :
>>
>> Hello Rasmus,
>>
>>
>> No, we don't have any plans for JS library at the moment.
>>
>>
>> -Danial, AdWords API Team.
>>
>>
>> On Monday, April 7, 2014 11:44:37 PM UTC+4, Rasmus Ladekjær Pedersen 
>> wrote:
>>>
>>> Hi there,
>>>
>>> do you have any plans for a JavaScript library?
>>>
>>> With all the Node.js going on, I believe we are a lot wanting a 
>>> JavaScript library for the Google AdWords API.
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/9e3ce795-d4ad-4c32-b96b-05e45fca8075%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting the Change History via the API

[Danilo Bargen]

Hi

On Friday, August 29, 2014 3:47:03 PM UTC+2, Josh Radcliff (AdWords API 
Team) wrote:
>
> The API does not provide user information about changes at this time. 
> Anash's previous post regarding CustomerSyncService 
>  covers 
> the only change history-related features of the API.
>

That's what I feared, thanks for the information. Too bad that Google don't 
eat their own dogfood regarding the APIs (hello there Amazon)...

Is there a way to make this a feature request?

Cheers
Danilo

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/c24e8cf6-c1ba-4da7-9b2b-b28b03de39f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Shared[*]Services AdWords API services given access denied error.

[ddofborg]

I see. 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/5c40f92c-a0e2-4546-8f59-a303f82d78c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting the Change History via the API

[Josh Radcliff (AdWords API Team)]

Hi Danilo,

The API does not provide user information about changes at this time. 
Anash's previous post regarding CustomerSyncService 
 covers 
the only change history-related features of the API.

Best regards,
Josh, AdWords API Team

On Friday, August 29, 2014 8:57:00 AM UTC-4, Danilo Bargen wrote:
>
> Hi everyone
>
> The issue below is now over 2 years old. Is there a way now to query the 
> change history? I need to be able to retrieve the list of people that 
> edited an account during the last month.
>
> Danilo
>
>
> On Tuesday, June 26, 2012 12:12:11 PM UTC+2, Anash P. Oommen wrote:
>>
>> Hi Oliver,
>>
>> CustomerSyncService doesn't give you the kind of change details you are 
>> looking for, it is mostly useful for figuring out what objects changed 
>> during a time period and then sync local databases with AdWords API server 
>> by downloading only the modified objects.
>>
>> Cheers,
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Monday, 18 June 2012 21:36:50 UTC+5:30, Oliver wrote:
>>>
>>> Hi,
>>>
>>> I believe the only way to get some data about the 'Change History' is by 
>>> using the CustomerSyncService object. 
>>>
>>> Looking at this object I have 2 questions:
>>>
>>> 1) There doesn't seem to be a timestamp given for when the change took 
>>> place.  This is unlike the adwords interface that tells you when and how 
>>> performed the change.  Correct?
>>>
>>> 2) It doesn't tell you the nature of the change e.g. if the 'Target CPA' 
>>> of an adgroup changed, all the API can tell me is that there was a change 
>>> to the adgroup (but it can't tell me what the change is).  Again, this is 
>>> different from the interface. Correct?
>>>
>>> Many thanks.
>>>
>>> Oliver
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/12c7621c-0f03-49d3-ae16-f34c86ad2e25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Shared[*]Services AdWords API services given access denied error.

[Josh Radcliff (AdWords API Team)]

Hi,

At this time, there is no way to get shared set-related information from 
the API unless you were whitelisted for shared set features in the past.

Best regards,
Josh, AdWords API Team

On Friday, August 29, 2014 9:25:58 AM UTC-4, ddofborg wrote:
>
> I see!
>
> Is there another way to download shared negative keywords? Using adhoc or 
> something else?
>
>
>
> On Friday, August 29, 2014 3:19:12 PM UTC+2, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Shared set services are only available to existing whitelisted customers 
>> .
>>
>> Cheers,
>> Josh, AdWords API Team
>>
>> On Friday, August 29, 2014 5:17:35 AM UTC-4, ddofborg wrote:
>>>
>>>
>>> We have some trouble accessing Shared[*]Services to download all shared 
>>> negative keywords. We receive a AuthorizationError.SERVICE_ACCESS_DENIED 
>>> errors on get-request.
>>>
>>> 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/1a0ff8ce-78fb-4c72-9859-3d7bf2a5b6a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: InternalApiError.UNEXPECTED_INTERNAL_API_ERROR

[Josh Radcliff (AdWords API Team)]

Hi,

I noticed that your request is missing the advertisingChannelType 
.
 
This field is required starting with v201402 
. 
Please include that element in your request and try again.

Thanks,
Josh, AdWords API Team

On Friday, August 29, 2014 7:00:10 AM UTC-4, Alexey Polotnyanko wrote:
>
> Hello!
>
> I'm trying to create campaign and it fails with %subj error.
> What's wrong?
>
> Request is:
>
>  xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:wsdl="https://adwords.google.com/api/adwords/cm/v201406"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>xmlns="https://adwords.google.com/api/adwords/cm/v201406";>
>  AwApi-Ruby/0.13.1, Common-Ruby/0.9.5, Savon/1.2.0, 
> ruby/1.9.3, HTTPI/1.1.1, curb)
>  my_token
>  my_customer_id
>  true
>   
>
>
>   https://adwords.google.com/api/adwords/cm/v201406";>
>  
> ADD
> 
>Коллекции
>
>   299055549
>
>
>   true
>
>
>   true
>   true
>   true
>   
> false
>
>
>   MANUAL_CPC
>
> 
>  
>   
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/1b3e9768-3cbd-4d6e-9eff-b3e26c31f64c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Shared[*]Services AdWords API services given access denied error.

[ddofborg]

I see!

Is there another way to download shared negative keywords? Using adhoc or 
something else?



On Friday, August 29, 2014 3:19:12 PM UTC+2, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi,
>
> Shared set services are only available to existing whitelisted customers 
> .
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, August 29, 2014 5:17:35 AM UTC-4, ddofborg wrote:
>>
>>
>> We have some trouble accessing Shared[*]Services to download all shared 
>> negative keywords. We receive a AuthorizationError.SERVICE_ACCESS_DENIED 
>> errors on get-request.
>>
>> 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/8cc78caa-3d9d-4a0e-a9ec-1bebf912c352%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Refresh token usage for downloading adhoc reports

[Josh Radcliff (AdWords API Team)]

Hi Amar,

You need an OAuth *access token* for any API request, including reporting 
requests -- see the OAuth2 Guide 
 for an 
overview of the basic steps for OAuth.

If you want to construct reporting requests without a client library, check 
out our Reporting Basics Guide 
, 
which includes information about the required headers and parameters for 
reports.

I'd encourage you to use one of our client libraries, if possible. They 
handle all of the OAuth requests and responses for you and make using the 
API much easier all around.

Cheers,
Josh, AdWords API Team

On Friday, August 29, 2014 1:06:10 AM UTC-4, AMAR NAYAK wrote:
>
> Hi ,
> I need to download couple of performance reports : Adgroup and Campaign 
> performance report using adhoc reports.
> I am going through the v201406 documentation and getting confuse over the 
> usage of refresh token .
> Do we need to use refresh token in adhoc reports ? If yes ,where should I 
> use it?
> Are there any examples of adhoc report downloads not using the client 
> library ?
>
> Thanks,
> -Amar
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/964fb901-634e-4280-8288-c7d4771f5285%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Shared[*]Services AdWords API services given access denied error.

[Josh Radcliff (AdWords API Team)]

Hi,

Shared set services are only available to existing whitelisted customers 
.

Cheers,
Josh, AdWords API Team

On Friday, August 29, 2014 5:17:35 AM UTC-4, ddofborg wrote:
>
>
> We have some trouble accessing Shared[*]Services to download all shared 
> negative keywords. We receive a AuthorizationError.SERVICE_ACCESS_DENIED 
> errors on get-request.
>
> 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/44bb4f84-1baa-4e61-89ff-75fc65732fa2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: INCOMPLETE_SIGNUP error returned by Adwords API

[Josh Radcliff (AdWords API Team)]

Hi Eli,

Billing info needs to be setup and terms and conditions must be accepted on 
the *production* MCC (the one with the developer token). I can see that 
terms & conditions have not been accepted yet on your production MCC. 
Please follow the instructions in our Common Errors Guide 
. 
That guide also contains contact information you can use if you have 
trouble with the billing or terms & conditions setup.

Cheers,
Josh, AdWords API Team

On Thursday, August 28, 2014 10:20:19 AM UTC-4, eli@aimeesoft.com wrote:
>
> Hi,
> When making requests with a  production key to test a MCC i get an 
> INCOMPLETE_SIGNUP error.
> I followed the instructions in other posts and made sure the billing info 
> is updated and the terms contract has been approved.
> Can you please help?
>
> Test customer id: 879-695-1428
> Production customer id: 471-076-9636
>
> Thanks,
> Eli
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/5f32b4b5-5f4d-4709-a9c9-04f0434728b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Auto-tagging via API

[Josh Radcliff (AdWords API Team)]

Hi,

As described in our Managing Customer Accounts guide 
,
 
you can use the *CustomerService* to set an account's autoTaggingEnabled 

 attribute.

Cheers,
Josh, AdWords API Team

On Thursday, August 28, 2014 11:56:40 AM UTC-4, GDZ wrote:
>
> As far as I understand, account's auto-tagging field is not available in 
> API. Is it possible to use adwords scripts to be able to modify it?
>
> Thank you,
> GDZ 
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/e2813f07-4004-4eb4-a590-f9dff2fb7618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Adword Api

[Josh Radcliff (AdWords API Team)]

Hi Rakesh,

Regarding the auth.ini file, please read the PHP library README 
 for 
instructions on configuring your environment. You may also find the library's 
OAuth2 wiki 

 helpful.

All of the examples in the library are meant to be run from the command 
line, as they write to stdout and (in some cases) read from stdin. If you 
try to "run" them by deploying them and navigating to them in your browser, 
you'll just see a blank page.

Once you have completed the setup, you can run the GetAccountHierarchy.php 
example 

 (from 
the command line) to see all of the accounts under your MCC.

Cheers,
Josh, AdWords API Team

On Friday, August 29, 2014 12:15:43 AM UTC-4, Rakesh Kumar wrote:
>
> Hi Jason Stedman,
>
> Thank you for your reply . but i don't know how to run this script on wamp 
> server in php.
> please help me here is the demo url for testing purpose please take a look 
> and tell me what is the problem here
>
> http://adwordmedia.biz/googleads-php-lib-master/
>
> i want fetch the all MCC account  Details with the all client which 
> already exist in the adwords account.
>
>
> Thanks
> Rakesh
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b80c6b15-8b16-4756-9e9b-a934e474d705%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting the Change History via the API

[Danilo Bargen]

Hi everyone

The issue below is now over 2 years old. Is there a way now to query the 
change history? I need to be able to retrieve the list of people that 
edited an account during the last month.

Danilo


On Tuesday, June 26, 2012 12:12:11 PM UTC+2, Anash P. Oommen wrote:
>
> Hi Oliver,
>
> CustomerSyncService doesn't give you the kind of change details you are 
> looking for, it is mostly useful for figuring out what objects changed 
> during a time period and then sync local databases with AdWords API server 
> by downloading only the modified objects.
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Monday, 18 June 2012 21:36:50 UTC+5:30, Oliver wrote:
>>
>> Hi,
>>
>> I believe the only way to get some data about the 'Change History' is by 
>> using the CustomerSyncService object. 
>>
>> Looking at this object I have 2 questions:
>>
>> 1) There doesn't seem to be a timestamp given for when the change took 
>> place.  This is unlike the adwords interface that tells you when and how 
>> performed the change.  Correct?
>>
>> 2) It doesn't tell you the nature of the change e.g. if the 'Target CPA' 
>> of an adgroup changed, all the API can tell me is that there was a change 
>> to the adgroup (but it can't tell me what the change is).  Again, this is 
>> different from the interface. Correct?
>>
>> Many thanks.
>>
>> Oliver
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0ee47177-c18b-48c5-b06f-2f152f773a6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Keyword ID with no information in Keywords Performance Report

[Josh Radcliff (AdWords API Team)]

Hi Oscar,

Thanks for sending the info. The criteria ID you provided from the Click 
Performance Report is for a *UserList* criterion. You can see this is if 
you add the *CriteriaType* column to the Criteria Performance Report 
 and 
filter by (criterion) ID:

SELECT Date, CampaignId, AdGroupId,* Id, CriteriaType* FROM 
CRITERIA_PERFORMANCE_REPORT WHERE *Id = xxx* DURING 20140827,20140827

Keyword ID  Criteria Type  Impressions
789...  User List  6233

The reason the *Click Performance Report* and the *Criteria Performance 
Report* both return this criterion ID instead of a keyword ID is that these 
reports are both single attribution reports 
,
 
so AdWords picks the most relevant criterion for each impression on those 
reports. Impressions in a *Display Network* campaign can be triggered by 
various criteria, not just keywords, which is why the API offers criterion 
type-specific reports such as the *Display Keywords Performance Report*, 
the *Age Range Performance Report*, etc.

For user lists, there's the Audience Performance Report 
, 
which returns the following for your campaign and ad group for that day.

AudienceImpressions
boomuserlist::6978660   179
boomuserlist::8113860   6233
boomuserlist::8113980   28
Total   6440

So for you particular use case, you'll have to keep in mind that the 
*CriteriaId* returned in the *Click Performance Report* is not going to 
always be for a keyword. To determine the type of criteria, you could:

   1. Run the *Click Performance Report* and capture the *CriteriaId*
   2. Run a *Criteria Performance Report*, filtered by your *CampaignId, 
   AdGroupId, *and *Id* (criterion), and include *CriteriaType* in the list 
   of selected fields. This report should use the same single attribution 
   logic as the *Click Performance Report*.
   3. For each *Id/CriteriaType* pair returned in step 2, run the multiple 
   attribution report 
   

 that 
   corresponds to the *CriteriaType* to gather more criterion type-specific 
   information, if desired.

Cheers,
Josh, AdWords API Team

On Thursday, August 28, 2014 3:07:36 PM UTC-4, Oscar Martinez wrote:
>
> Hi Josh, 
>
> I sent you privately the information of the Google Click ID, Campaign 
> ID, Ad group ID, Keyword ID.
>
> Thank you, 
>
> On Thursday, August 28, 2014 11:07:14 AM UTC-6, Oscar Martinez wrote:
>>
>> Hi, 
>>
>> We are creating a small report for my company. We need to get Campaign 
>> Name, AdGroup Name and Keywords for a gclid. We have these steps:
>>
>> 1. Capture and save gclid.
>> 2. CLICK_PERFORMANCE_REPORT to get CampaignId, AdGroupId and CriteriaId 
>> (Keyword ID) filtering by gclid and DateRange=TODAY (or Yesterday, if we 
>> saved the gclid yesterday).
>> 3. KEYWORD_PERFORMANCE_REPORT to get KeywordText, CampaignName and 
>> AdGroupName, filtering by Id (Keyword ID) and DateRange=ALL_TIME.
>>
>> If we test using gclid from today, we get data on steps 2 and 3 (Good). 
>> If we test using gclid from yesterday we get results only on step 2, but 
>> step 3 is empty (Bad).
>> We have 2 saved gclid from today and 1 saved gclid from yesterday. I can 
>> post the gclid information, but I'm not sure if it's a good idea to do it 
>> public.
>>
>> Pdata: The documentation in spanish is different to english version. In 
>> spanish we don't have the Click Report. We had to use a browser in English 
>> to see it.
>>
>> 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0c49b9d3-a6c9-4984-8609-d5f72e58ace8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

InternalApiError.UNEXPECTED_INTERNAL_API_ERROR

[Alexey Polotnyanko]

Hello!

I'm trying to create campaign and it fails with %subj error.
What's wrong?

Request is:

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:wsdl="https://adwords.google.com/api/adwords/cm/v201406"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
   
  https://adwords.google.com/api/adwords/cm/v201406";>
 AwApi-Ruby/0.13.1, Common-Ruby/0.9.5, Savon/1.2.0, 
ruby/1.9.3, HTTPI/1.1.1, curb)
 my_token
 my_customer_id
 true
  
   
   
  https://adwords.google.com/api/adwords/cm/v201406";>
 
ADD

   Коллекции
   
  299055549
   
   
  true
   
   
  true
  true
  true
  false
   
   
  MANUAL_CPC
   

 
  
   

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0e4a92b9-b732-49f4-b97b-41a4cd8ccb23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Refresh token usage for downloading adhoc reports

[AMAR NAYAK]

Hi ,
I need to download couple of performance reports : Adgroup and Campaign 
performance report using adhoc reports.
I am going through the v201406 documentation and getting confuse over the 
usage of refresh token .
Do we need to use refresh token in adhoc reports ? If yes ,where should I 
use it?
Are there any examples of adhoc report downloads not using the client 
library ?

Thanks,
-Amar

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/eac10a40-cbab-4ad6-8477-dd8a58319bcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Any plans for a JavaScript library?

[Danial Klimkin]

Hello Jerome,


There are no current plans for re-working of the AdWords API.

I can't give any estimation on how complex this can be but you can always 
create a project on github and make it open for other contributors. 
Questions on node.js are asked on this forum from time to time.


-Danial, AdWords API Team.


On Thursday, August 28, 2014 7:49:54 PM UTC+4, Jerome Wagner wrote:
>
> Hello, 
>
> I understand that my best bet if I want to access the adwords API from 
> node.js is to dig into the old 
> https://code.google.com/p/google-api-adwords-js/ that used to work on the 
> browser and adapt it 
>  * for node.js (it seems that goog. has been adapted for node.js in 2013)
>  * for the newer v201406 API
>
> how hard do you think that would be ? 
>
> are there any plans to retrofit the adwords API into the google api 
> discovery service so that I could use its node.js client implementation ?
>
> --
> Jerome
>
> Le mardi 8 avril 2014 15:25:41 UTC+2, Danial Klimkin a écrit :
>>
>> Hello Rasmus,
>>
>>
>> No, we don't have any plans for JS library at the moment.
>>
>>
>> -Danial, AdWords API Team.
>>
>>
>> On Monday, April 7, 2014 11:44:37 PM UTC+4, Rasmus Ladekjær Pedersen 
>> wrote:
>>>
>>> Hi there,
>>>
>>> do you have any plans for a JavaScript library?
>>>
>>> With all the Node.js going on, I believe we are a lot wanting a 
>>> JavaScript library for the Google AdWords API.
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/8b644350-48fe-4f90-83f5-80c517fcc0e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sub-Divide Existing Product Parition

[Shopping API Team]

Hi there,

To subdivide an existing partition, I'd actually recommend deleting the 
entire tree (by deleting the root node) and reuploading it, as it's going 
to be significantly easier from an implementation point of view. The only 
exception is if you can't upload your tree in one go, in which case you'll 
need a different approach 
.

Cheers,
Sérgio

---
Sérgio Gomes
Developer Relations

Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 
9TQ
Registered in England Number: 3977902

On Thursday, 28 August 2014 14:34:45 UTC+1, aroxo...@gmail.com wrote:
>
> Hi,
>
> i have following queries :
>
> 1. Sub-dividing Existing Product Partition 
>
> https://groups.google.com/d/msg/adwords-api/P6DYn6N3XTU/-2FfmLh54EcJ
>
> This is the exact need , can i get the code on these steps ?
>
> 2. i can create product Paritions using Product offerId , but can;t able 
> to do with product type
>
> *For example :  first child *
>
> $helper = new ProductPartitionHelper($var_adgroup_id); 
>
> $root = $helper->createSubdivision();
>
> $helper->createUnit($root, new 
> ProductType('PRODUCT_TYPE_L1','radiators'),2);
> $helper->createUnit($root, new ProductType('PRODUCT_TYPE_L1','shower 
> enclosures'),2);
>
> $helper->createUnit($root, new ProductType());
>
> $result = $adGroupCriterionService->mutate($helper->getOperations());
>
> ---
>
> 3.  ' PRODUCT_TYPE_L1' -> For first child level product types/
>
> if we use 2nd child -> then we have to use 'PRODUCT_TYPE_L2' ?
>
> Please help me out
>
> 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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/9b2b4983-1226-45d9-8ca0-f3577a5ec303%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Accessing Shared[*]Services AdWords API services given access denied error.

[ddofborg]

We have some trouble accessing Shared[*]Services to download all shared 
negative keywords. We receive a AuthorizationError.SERVICE_ACCESS_DENIED 
errors on get-request.

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 http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/e8c70e94-579f-4f4d-af1b-c41e826fac8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue with uploading large amounts of data using MutateJobService

[Oliver]

Thanks Alan for the update. Let us know if the changes you make will have 
an effect.

Hopefully also the API team will shed some light on this.

Oliver


On Friday, August 29, 2014 9:14:44 AM UTC+1, Alan Coleman wrote:
>
> Hi Oliver,
>
> Thanks for getting involved, that's an interesting find in the 
> documentation that I haven't seen before. I started this post about the 
> UNEXPECTED_INTERNAL_API_ERROR which I'm sometimes receiving when trying 
> bulk uploads using MJS - Hopefully this is being looked into.
>
> However there has been issues with MJS nearly finishing my jobs but then 
> just stopping in a *deadlock-like condition*. The SOAP Logs report back 
> as normal and indicate that the job is *pending*.
>
> There's no way round using the same customerId as that would defeat the 
> object of what we're trying to achieve. 
>
> If I use adding TextAds as an example, the array that I currently pass to 
> the MJS is constructed in AdGroup order, which is how it comes out of my 
> db, and it's not unusual to be trying to add several TextAds in each 
> AdGroup.
>
> I'm chunking my ordered array into arrays of 1000 and then looping round 
> through MJS to create jobs of that size, so it's possible that a concurrent 
> job may contain the same AdGroup if the TextAds for that AdGroup have been 
> chunked half way through. I think that is what the following means:
>
> *>> jobs operating on the same AdGroups*
>
> It may be a long shot but a good place for me to start would be to ensure 
> that a particular Adgroup can only appear in one job.
>
> With regards to:
>
> Is the creation of multiple Ads within the same AdGroup considered as 
>> operating on the adgroup itself?
>> If so, is this implying that we shouldn't attempt to create multiple Ads 
>> within the same adgroup using MJS?
>
>
> I may be wrong, but I've never experienced any problems with writing 
> multiple TextAds or Keywords to a single AdGroup until I started using MJS, 
> and even then it's only when maintaining large job sizes.
>
> As I said earlier, probably unrelated to the 
> UNEXPECTED_INTERNAL_API_ERROR, but I'm going to make the subtle changes to 
> constructing my MJS anyway.
>
> Thanks again,
>
>
>
> On Thursday, August 28, 2014 5:09:18 PM UTC+1, Oliver wrote:
>>
>> I'm about to do something similar to what Alan is doing and, hence, why 
>> I'm also interested in this.
>>
>> I see on this page:
>> https://developers.google.com/adwords/api/docs/guides/batch-processing
>>
>> there is a paragraph that says:
>>
>>
>>- 
>>
>>When submitting a lot of concurrent jobs for the same customerId, try 
>>to reduce the likelihood of jobs operating on the same AdGroups at the 
>> same 
>>time, while maintaining large job sizes. Many unfinished jobs (with 
>> status 
>>of PENDING or PROCESSING) that try to mutate the same set of AdGroups 
>>may lead to deadlock-like conditions resulting in severe slow-down and 
>> even 
>>job failures.
>>
>> I don't know exactly what is being referred to by this term:
>>
>> >> jobs operating on the same AdGroups
>>
>> Is the creation of multiple Ads within the same AdGroup considered as 
>> operating on the adgroup itself?
>>
>> If so, is this implying that we shouldn't attempt to create multiple Ads 
>> within the same adgroup using MJS?
>>
>> Oliver
>>
>>
>>
>> On Thursday, August 28, 2014 10:39:40 AM UTC+1, Alan Coleman wrote:
>>>
>>> Thanks Anash,
>>>
>>> I caught another such error in my SOAP Log this morning, although this 
>>> time the error returned before any results.
>>>
>>> I'd really appreciate it if you could take a quick look and let me know 
>>> what you think.
>>>
>>> Many thanks.
>>>
>>> HTTP/1.1 500 Internal Server Error
>>> Content-Type: text/xml; charset=UTF-8
>>> Date: Thu, 28 Aug 2014 09:28:48 GMT
>>> Expires: Thu, 28 Aug 2014 09:28:48 GMT
>>> Cache-Control: private, max-age=0
>>> X-Content-Type-Options: nosniff
>>> X-Frame-Options: SAMEORIGIN
>>> X-XSS-Protection: 1; mode=block
>>> Server: GSE
>>> Transfer-Encoding: chunked
>>>
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/";>
>>>   
>>> https://adwords.google.com/api/adwords/cm/v201402";>
>>>   000501ad297264b00a4254a6960046b8
>>>   MutateJobService
>>>   mutate
>>>   0
>>>   8909
>>> 
>>>   
>>>   
>>> 
>>>   soap:Server
>>>   [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]
>>>   
>>> https://adwords.google.com/api/adwords/cm/v201402";>
>>>   [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]
>>>   
>>> ApiException
>>>   http://www.w3.org/2001/XMLSchema-instance"; 
>>> xsi:type="InternalApiError">
>>> 
>>> 
>>> 
>>> InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>>> InternalApiError
>>> UNEXPECTED

Re: Issue with uploading large amounts of data using MutateJobService

[Alan Coleman]

Hi Oliver,

Thanks for getting involved, that's an interesting find in the 
documentation that I haven't seen before. I started this post about the 
UNEXPECTED_INTERNAL_API_ERROR which I'm sometimes receiving when trying 
bulk uploads using MJS - Hopefully this is being looked into.

However there has been issues with MJS nearly finishing my jobs but then 
just stopping in a *deadlock-like condition*. The SOAP Logs report back as 
normal and indicate that the job is *pending*.

There's no way round using the same customerId as that would defeat the 
object of what we're trying to achieve. 

If I use adding TextAds as an example, the array that I currently pass to 
the MJS is constructed in AdGroup order, which is how it comes out of my 
db, and it's not unusual to be trying to add several TextAds in each 
AdGroup.

I'm chunking my ordered array into arrays of 1000 and then looping round 
through MJS to create jobs of that size, so it's possible that a concurrent 
job may contain the same AdGroup if the TextAds for that AdGroup have been 
chunked half way through. I think that is what the following means:

*>> jobs operating on the same AdGroups*

It may be a long shot but a good place for me to start would be to ensure 
that a particular Adgroup can only appear in one job.

With regards to:

Is the creation of multiple Ads within the same AdGroup considered as 
> operating on the adgroup itself?
> If so, is this implying that we shouldn't attempt to create multiple Ads 
> within the same adgroup using MJS?


I may be wrong, but I've never experienced any problems with writing 
multiple TextAds or Keywords to a single AdGroup until I started using MJS, 
and even then it's only when maintaining large job sizes.

As I said earlier, probably unrelated to the UNEXPECTED_INTERNAL_API_ERROR, 
but I'm going to make the subtle changes to constructing my MJS anyway.

Thanks again,



On Thursday, August 28, 2014 5:09:18 PM UTC+1, Oliver wrote:
>
> I'm about to do something similar to what Alan is doing and, hence, why 
> I'm also interested in this.
>
> I see on this page:
> https://developers.google.com/adwords/api/docs/guides/batch-processing
>
> there is a paragraph that says:
>
>
>- 
>
>When submitting a lot of concurrent jobs for the same customerId, try 
>to reduce the likelihood of jobs operating on the same AdGroups at the 
> same 
>time, while maintaining large job sizes. Many unfinished jobs (with status 
>of PENDING or PROCESSING) that try to mutate the same set of AdGroups 
>may lead to deadlock-like conditions resulting in severe slow-down and 
> even 
>job failures.
>
> I don't know exactly what is being referred to by this term:
>
> >> jobs operating on the same AdGroups
>
> Is the creation of multiple Ads within the same AdGroup considered as 
> operating on the adgroup itself?
>
> If so, is this implying that we shouldn't attempt to create multiple Ads 
> within the same adgroup using MJS?
>
> Oliver
>
>
>
> On Thursday, August 28, 2014 10:39:40 AM UTC+1, Alan Coleman wrote:
>>
>> Thanks Anash,
>>
>> I caught another such error in my SOAP Log this morning, although this 
>> time the error returned before any results.
>>
>> I'd really appreciate it if you could take a quick look and let me know 
>> what you think.
>>
>> Many thanks.
>>
>> HTTP/1.1 500 Internal Server Error
>> Content-Type: text/xml; charset=UTF-8
>> Date: Thu, 28 Aug 2014 09:28:48 GMT
>> Expires: Thu, 28 Aug 2014 09:28:48 GMT
>> Cache-Control: private, max-age=0
>> X-Content-Type-Options: nosniff
>> X-Frame-Options: SAMEORIGIN
>> X-XSS-Protection: 1; mode=block
>> Server: GSE
>> Transfer-Encoding: chunked
>>
>> 
>> http://schemas.xmlsoap.org/soap/envelope/";>
>>   
>> https://adwords.google.com/api/adwords/cm/v201402";>
>>   000501ad297264b00a4254a6960046b8
>>   MutateJobService
>>   mutate
>>   0
>>   8909
>> 
>>   
>>   
>> 
>>   soap:Server
>>   [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]
>>   
>> https://adwords.google.com/api/adwords/cm/v201402";>
>>   [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
>> com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]
>>   
>> ApiException
>>   http://www.w3.org/2001/XMLSchema-instance"; 
>> xsi:type="InternalApiError">
>> 
>> 
>> 
>> InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
>> InternalApiError
>> UNEXPECTED_INTERNAL_API_ERROR
>>   
>> 
>>   
>> 
>>   
>> 
>>
>> On Wednesday, August 27, 2014 12:40:01 PM UTC+1, Alan Coleman wrote:
>>>
>>> Hello everyone,
>>>
>>> I'm creating some functionality in our app to build a fresh copy of a 
>>> campaign based on a current  campaign's ALL_TIME sqpr report. The report 
>>> has the potential to produces tens of thousands of search term