google adwords api usage
Hi Eric, Jeff and others, first of all, many thanks for all your hard work in writing the api-libs/examples and providing assistance to the community, it is much appreciated. I have a question about the usage of the adwords api, I would like to perform keyword research by parsing large lists of keywords and extracting the exact search volume and CPC. Clients of us get filtered results from these lists based on the adwords api data and data from other sources. Would this be acceptable under the adwords api tc, if not, what needs to be changed? The tc is not unambiguous about this and of course I do not want to spend development time on a project which may be killed without notice due to an unspecified 'breach' of the API tc, that's why I ask for help here. Thanks in advance. Greetings, Bram -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: db migration, are accents now ignored for spanish terms
Hi Eric, is there a consistent way in which I can check whether the results apply to the seed keywords ? I have tried checking the keywords from the result with the seed keywords but that doesn't do the trick, I see in the results from the web tool that indeed the accents are removed, shouldn't the api do the same ? (I use the php soap library btw) Greetings, Bram On Nov 9, 10:12 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Thank you for your feedback, I'll pass that along to the appropriate team. Please be clear that this behavior I'm describing only applies to the TargetingIdeaService and the Keyword Tool, and has no bearing on Google search results or ad serving. Best, - Eric On Nov 7, 1:25 am, manuel manuel_pa...@sapo.pt wrote: You say: statistics for accents and non-accented keywords are combined into a single search volume number. This is absolutely wrong. Google can't simple combine two absolute different words, with a complete different meaning into one, just because they look alike. I see Google is now doing the same mistake on the search results!!! I don't know what language experts Google has consulted, but in French, Spanish and Portuguese there are a lot of words that when accented gain a complete different meaning! Regards, On Sep 28, 1:54 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi All, To be clear, the changes in how accents are handled is part of a larger change in the Keyword Tool backend, and the behavior is consistent across the API and the web interface. My current understanding is that the statistics for accents and non-accented keywords are combined into a single search volume number. There are changes in search volume data across the board, as explained in this blog post: http://adwords.blogspot.com/2010/09/updated-keyword-tool-out-of-beta In addition to these improvements, we’ve also changed how we calculate Global Monthly Searches and Local Monthly Searches. Statistics in these columns are now based on Google.com search traffic only. Previously, they also included traffic from search partners. We've updated these statistics based on advertiser feedback, and hope you find them more helpful for keyword selection. Your feedback regarding these changes is appreciated and I will pass it on to the engineering and product teams. Best, - Eric On Sep 24, 6:32 pm, JSL jslasc...@hotmail.com wrote: For your information, this intended behavior is quite an accomplishment in the sense that queries for some of the top latin accented keywords return absolutely no relevant adwords data. Regardless of the locations and languages settings, a query for crédit (french) returns either nothing or irrelevant data for english credit keywords. Pizza's on me at the next engineer meeting. In all seriousness, success is the journey, not the destination -Bruce Lee Good luck guys (and gals) On Sep 21, 8:50 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Just to confirm, this is the intended behavior. Best, - Eric On Sep 20, 5:12 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, I believe this was intentional, but I'll circle back with the engineering team and confirm. Best, - Eric Koleda, AdWords API Team On Sep 19, 10:23 am, bramiozo brami...@gmail.com wrote: Besides the rather large numerical discrepancy between different backends one thing I noticed was that the accents for the Spanish terms are ignored, is this a bug or is this intentional ? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: db migration, are accents now ignored for spanish terms
Thanks Eric. I would suggest, if I may, to set to SE-algo so that it always searches strictly if one keyword is given. Greetings, Bram On Sep 28, 3:54 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi All, To be clear, the changes in howaccentsare handled is part of a larger change in the Keyword Tool backend, and the behavior is consistent across the API and the web interface. My current understanding is that the statistics foraccentsand non-accented keywords are combined into a single search volume number. There are changes in search volume data across the board, as explained in this blog post: http://adwords.blogspot.com/2010/09/updated-keyword-tool-out-of-beta In addition to these improvements, we’ve also changed how we calculate Global Monthly Searches and Local Monthly Searches. Statistics in these columns are now based on Google.com search traffic only. Previously, they also included traffic from search partners. We've updated these statistics based on advertiser feedback, and hope you find them more helpful for keyword selection. Your feedback regarding these changes is appreciated and I will pass it on to the engineering and product teams. Best, - Eric On Sep 24, 6:32 pm, JSL jslasc...@hotmail.com wrote: For your information, this intended behavior is quite an accomplishment in the sense that queries for some of the top latin accented keywords return absolutely no relevant adwords data. Regardless of the locations and languages settings, a query for crédit (french) returns either nothing or irrelevant data for english credit keywords. Pizza's on me at the next engineer meeting. In all seriousness, success is the journey, not the destination -Bruce Lee Good luck guys (and gals) On Sep 21, 8:50 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Just to confirm, this is the intended behavior. Best, - Eric On Sep 20, 5:12 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, I believe this was intentional, but I'll circle back with the engineering team and confirm. Best, - Eric Koleda, AdWords API Team On Sep 19, 10:23 am, bramiozo brami...@gmail.com wrote: Besides the rather large numerical discrepancy between different backends one thing I noticed was that theaccentsfor the Spanish terms are ignored, is this a bug or is this intentional ? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: db migration, are accents now ignored for spanish terms
Eric, I have to urge a reconsideration of ignoring accents, this is really undermining the usefulness of the api and what is more, of google SE itself. Accents are part of most languages which have a roman characterset, they convey meaning and in some cases the presence of accents might indicate a completely different meaning. Targeting your advertisement starts with the keywords, imo you should leave the keywords alone. I think this move will not remain without consequences, if google thinks that languages have accents for no particular reason and chooses to ignore them it will raise awareness of language conservation groups all over the world and it will be considered a nuisance by everyone who now have to type their accented keywords with a plus sign or quotation marks just to ensure that google will not mess it up. A trivial example is røge which means smoke in Danish, in the new google SE interface I get everything BUT røge and instead end up with french cousin rogé, even a Russian one, simply because my browser is French, if I type røge I mean røge ! Of all this doesn't explain why your non-roman character domains show significantly lower results, this imo undermines using google #SERP/SV as a reference. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: db migration, are accents now ignored for spanish terms
Thanks Eric, did they tell you why because accented terms in French, Portuguese, Spanish ARE searched. This behavior applies to what roman character languages exactly and/or to what accents ? For instance German seems to be ok with the umlaut (ü,ö etc.) but ç with French is ignored, how did they decide what accents to include and what not ? Does the development team expect foreign advertisers to ignore accents and misspell their content (I assume not) or is it a catch-all solution where accented and non-accented results are added ? This means that accented terms for these particular languages/accents are ignored also in the SERP's ? I think it undermines the fidelity of the results since it is unknown to what extent the results come from the accented terms and to what extent it comes from the non-accented terms, furthermore the accents are ignored with the advent of idn's where exact searches on accented terms might be relevant for indexing. Sorry but it does raise some questions :) . On Sep 22, 2:50 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, Just to confirm, this is the intended behavior. Best, - Eric On Sep 20, 5:12 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, I believe this was intentional, but I'll circle back with the engineering team and confirm. Best, - Eric Koleda, AdWords API Team On Sep 19, 10:23 am, bramiozo brami...@gmail.com wrote: Besides the rather large numerical discrepancy between different backends one thing I noticed was that the accents for the Spanish terms are ignored, is this a bug or is this intentional ? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
db migration, are accents now ignored for spanish terms
Besides the rather large numerical discrepancy between different backends one thing I noticed was that the accents for the Spanish terms are ignored, is this a bug or is this intentional ? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: Suggested Bid from Search-based keyword tool vs (API) CPC from Traffic Estimator
Hi Eric, I saw the new beta doesn't have CPC information yet, is this still being pursued as a feature in coming releases ? Greetings, Bram On 3 sep, 23:44, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Hank, Unfortunately I don't have any information about how the SKTool generates suggested bids. There is no API for the SKTool, but the TargetingIdeaService provides results similar to the Keyword Tool: https://adwords.google.com/select/KeywordToolExternal Best, - Eric Koleda, AdWords API Team On Sep 3, 4:48 am, hank khang henry@gmail.com wrote: Two related parts question: I am an API user ... 1) What is the relationship between CPC from Traffic Estimator (TE) service and Suggested Bid returned from the Search-based keyword tool (http://www.google.com/sktool/#)? Can I estimate Suggested Bid from TE outputs? Do they represent the same thing at some level? 2) Is there an API for getting search-based keyword tool results. Thanks Hank -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: trafficEstimator service migration
I know enough, estimate or not ;) . Thanks Eric On 4 mei, 16:33, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Bram, Based on our current estimates, the new version of the TrafficEstimatorService should be available around mid-Q3. The v13 version of the service won't sunset until a couple months after the new version is released. Please note that while we're sharing these rough estimates to help you plan your API development, all dates are subject to change. Best, - Eric Koleda, AdWords API Team On May 2, 7:11 am, bramiozo brami...@gmail.com wrote: Dear sir/madam, can you give some indication about the migration of the trafficestimator service, right now I want to implement the service but it would be somewhat of a waste of time if it sunsets in a month. Thanks, Bram -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group:http://adwordsapi.blogspot.comhttp://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 athttp://groups.google.com/group/adwords-api?hl=en -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group:http://adwordsapi.blogspot.comhttp://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 athttp://groups.google.com/group/adwords-api?hl=en -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
trafficEstimator service migration
Dear sir/madam, can you give some indication about the migration of the trafficestimator service, right now I want to implement the service but it would be somewhat of a waste of time if it sunsets in a month. Thanks, Bram -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
AdWords API Re: Allowed charactersets/unicode ranges,TargetingIdeaService
Can anyone comment on this please ? On Dec 30 2009, 4:57 pm, bramiozo brami...@hotmail.com wrote: Moderators/Developers, what charactersets are allowed for the keywords, specifically for the TargetingIdeaService ? A term like casino♠ still gets EXACT searches which is obviously incorrect, the ♠ seems to be ignored, besides MiscellaneousSymbols what otherunicoderangesare ignored ? -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: TargetingIdeaService, how are the results sorted and is there any control in that ?
Ok, thanks Eric. On Dec 30, 4:06 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, Unfortunately it is not possible to control the sorting of the ideas returned by the TargetingIdeaService. Best, - Eric Koleda, AdWords API Team On Dec 29, 7:01 pm, bramiozo brami...@gmail.com wrote: I am processing terms with multiple keywords at a time but the order in which they come in is not the order of the terms in the output xml, this is rather inconvenient. Is there any way to get one-on-one input- output ordering ? I use the php api library (v. 1.2.1) btw. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Allowed charactersets/unicode ranges,TargetingIdeaService
Moderators/Developers, what charactersets are allowed for the keywords, specifically for the TargetingIdeaService ? A term like casino♠ still gets EXACT searches which is obviously incorrect, the ♠ seems to be ignored, besides MiscellaneousSymbols what other unicode ranges are ignored ? -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API TargetingIdeaService, how are the results sorted and is there any control in that ?
I am processing terms with multiple keywords at a time but the order in which they come in is not the order of the terms in the output xml, this is rather inconvenient. Is there any way to get one-on-one input- output ordering ? I use the php api library (v. 1.2.1) btw. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: Seed keyword type=Exact with keyword_tool_service
When will the exact/phrase match results be added to the api, because
imo that's basically what Goose is referring to.
Don't want to be sassy but this has been addressed a looong time ago,
I want to know when people type my keywords exactly, not broadly or in
a phrase,
I am sure I am not the only one.
Regards,
Bram
On 4 aug, 21:43, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hello,
The behavior is not entirely intuitive, especially if you're familiar
with the web-based tool. Please see this blog post:
http://adwordsapi.blogspot.com/2009/01/keyword-match-type-and.html
There have also been a few other threads in this Google Group
regarding the same behavior that you can search the archives for.
Cheers,
-Jeff Posnick, AdWords API Team
On Aug 4, 1:29 pm, Goose jaigo...@gmail.com wrote:
I tried to change the seed keyword type to an Exact match for
keyword_tool_service but didn't see any difference in the result when
compared with Broad match.
Does match type Exact work with getKeywordVariations or is there an
error in the code below?
# Create seed keyword structure.
$seed_keyword = 'negativefalse/negativetextmars/
texttypeExact/type';
$use_synonyms = 'useSynonymsfalse/useSynonyms';
# Get keyword variations.
$request_xml = 'getKeywordVariations' .
'seedKeywords' . $seed_keyword . '/seedKeywords' .
$use_synonyms .
'languagesen/languages' .
'countriesUS/countries' .
'/getKeywordVariations';
$variation_lists = $keyword_tool_service-call
('getKeywordVariations', $request_xml);
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
