Re: questions about authentication and general viability
thanks again michael, and sorry if i've made u repeat yourself. :) have a good one, -rob -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/09a54100-cca1-4bf3-a003-b22b452fdd1f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: questions about authentication and general viability
hi there, thanks for those links. we have reviewed those, and we still have questions. specifically, the rmf guide mentions that tools offering very limited and specialized functionality do not have to meet any creation and management requirements, but then goes on to suggest that tools providing data related to the TrafficEstimatorSerive have to provide ALL functionality listed in the rmf table: so if all we want to do is query that service for two values, which of these recommendations do we adhere to? were we to provide access to our tool to anonymous third parties, it wouldnt be strictly for internal use, what would our requirements be in this case? which leads to my confusion about your answer to my second question. you mention that we should implement the application flow of authentication, but the documentation indicates that in this model the user does indeed have to manually authenticate via a login screen. only once, i get that, but in our case even once would not be acceptable. is not what we really want a service account for authentication where credentials are read from a file accessible only by our tool? i should mention that this tool will run on php, browser-based. thanks for all your help. kind regards, -rob -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/0c615275-28c3-4680-8aa0-58903cafa057%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
questions about authentication and general viability
hello, we are developing a tool to automate and possibly outsource some keyword research tasks. long-tail keywords are generated by us but need to be checked for search traffic volume and adwords competition, as is possible using the estimator service in the adwords frontend. we need to be able to let third parties use this tool to assist us in our research endeavors. first off i'm wondering if this is generally a viable application for qualified adwords api usage. will we get a permanent, unlimited developer token for this kind of application model? actually, the really crucial piece of information for us is search volume per search key, competition value would be great but isnt totally necessary. and actually, imho, given google's market position in search engines, this information should be freely available to anyone, anyway.. my second question is about authentication. i see there are several methods available, but i'm unclear as to which will work for us. the main thing is that the main user of the tool must not have access to any kind of adwords credentials, so all authentication needs to happen silently and without user interaction (no oauth2 login screens etc). how can we best achieve this? thanks for your help! kind regards, -rob k. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/7e40be72-21a3-4d84-826b-a2e71b33b27d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
questions about general viability and authentication
hello, i thought i just posted a question, but there must have been a glitch as i dont see it in the forum. if this topic ends up being a duplicate, i apologize. we are developing a tool to assist us in doing (and outsourcing) some keyword research. we are basically generating long-tail keywords and need to test each phrase for overall search volume and adwords competition using the TrafficEstimatorService. actually, the really crucial piece of information is search traffic volume (competition could be guesstimated), and imho, given google's monopolistic position in the search engine market, this information should be provided freely to anyone. since it isn't, can we expect to be issued a permanent developer token for such an application even though there is virtually no relation to any classic adwords-related tasks? my second question is about authentification. since the goal is to outsource this task, it is essential that users of the tool do not have access to any adwords credentials or logins/passwords. this is the main motivation behind creating this tool. any kind of authentication with the api server needs to be done silently and without any user interaction (no oauth2 login screens etc). i see that there are several authentication methods available - how can we best achieve this sort of automated authentication that we're used to from so many other soap apis out there? thanks in advance for your help. kind regards, -rob k. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/a606cf0d-026d-478d-818a-1f6911b2bc99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: v13 Cross Client Report Service
Thanks for clearing things up Kevin. Can I suggest/request that something is put in place where old posts are updated if they are incorrect? Not easy I know but would be usable across the Google blogs and would help prevent misunderstandings and confusion in general. Thanks again On Dec 15, 3:09 pm, Kevin Winter wrote: > Hi, > The most recent posts are more up-to-date regarding sunsets than the > earlier posts you linked in the below message. V13 reporting will be > sunset on February 29th, 2012 along with every version with the exception > of v201109. > > - Kevin Winter > AdWords API Team > > > > > > > > On Wednesday, December 14, 2011 6:52:10 AM UTC-5, rh wrote: > > > Thanks, I have found this post also. > > > The confusing thing is Google are contradicting themselves. > > > I have found 1 post where they state that V13 ReportingService will > > sunset in August 2011:http://adwordsapi.blogspot.com/2011/03/adwords- > > api-v201101-launch-providing.html > > > I have found another where it states "We want to clarify that the > > sunset that will happen four months from when MCC cross-client reports > > go live" > >http://adwordsapi.blogspot.com/2011/05/update-on-adwords-api-v201101-... > > Yet they now state "*Note: We are not supporting cross-client reports > > in this release". > > > Due to the above a concrete answer from Google would be fantastic. Or > > maybe when they go back on what they have said previously, an update > > to previous post's would help clear things up. > > > Still confused. I really need a definitive answer, thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: v13 Cross Client Report Service
Thanks, I have found this post also. The confusing thing is Google are contradicting themselves. I have found 1 post where they state that V13 ReportingService will sunset in August 2011:http://adwordsapi.blogspot.com/2011/03/adwords- api-v201101-launch-providing.html I have found another where it states "We want to clarify that the sunset that will happen four months from when MCC cross-client reports go live" http://adwordsapi.blogspot.com/2011/05/update-on-adwords-api-v201101-sunset.html Yet they now state "*Note: We are not supporting cross-client reports in this release". Due to the above a concrete answer from Google would be fantastic. Or maybe when they go back on what they have said previously, an update to previous post's would help clear things up. Still confused. I really need a definitive answer, thanks. On Dec 14, 11:35 am, TompiT wrote: > I have found these official information from the Google AdWords API > Team : > > "As we announced (http://adwordsapi.blogspot.com/2011/11/120-days- > until-deprecation-deadline.html) earlier this month, with the recent > release of AdWords API v201109 (http://adwordsapi.blogspot.com/2011/10/ > adwords-api-v201109-launch-providing.html) , we will be deprecating > earlier versions of the AdWords API on February 29, 2012. > > The versions and services we will be shutting down are:- API versions > v13, v200909, v201003, v201008, v201101.*- API version v13 > AccountService will only be available on a whitelist basis.*Note: We > are not supporting cross-client reports in this release. We have > released support for downloading v201109 AdHoc reports in all the > client libraries. We have also released reference implementations > demonstrating how to use AdHoc reports to download reports across > multuple clients in both Java (http://code.google.com/p/google-api- > adwords-java/source/browse/apps/multipleclientreportdownloader/src/com/ > google/api/adwords/reportdownload/) and Ruby (http://code.google.com/ > p/google-api-ads-ruby/source/browse/adwords_api/examples/v201109/ > parallel_report_download.rb) . > In addition, we would like to remind you that starting on Tuesday, > January 17, 2012, you must provide your developer token as an HTTP > header for all report downloads. Details can be found on the blog > (http://adwordsapi.blogspot.com/2011/11/update2-developer-token- > required-in.html) ." > On 14 déc, 10:22, rh wrote: > > > > > > > > > Hi, I run keyword reports, at an MCC level for all sub accounts that > > we manage via the v13 Cross Client Report Service. > > > Is this functionality being sunsetted or not? I have found conflicting > > information. > > > Thanks > > > RH -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
v13 Cross Client Report Service
Hi, I run keyword reports, at an MCC level for all sub accounts that we manage via the v13 Cross Client Report Service. Is this functionality being sunsetted or not? I have found conflicting information. Thanks RH -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en