Re: [v201209] Discrepancy between API results and web UI search volume results
This thread is a few years old. Please create a new one instead of reopening such an old thread. -Danial. On Monday, April 20, 2015 at 3:39:29 PM UTC+3, Afrooz Shaikh wrote: I just came Accross this issue, initialy i taught every thing was working fine because the UI and API wer Giving same data, bt as the number of keywords kept on increasing i saw difference of about 100 times in the search volume of 30% of the keywords i used. package uber.keyword.bussiness; import java.io.IOException; import java.sql.CallableStatement; import java.sql.SQLException; import java.util.HashMap; import java.util.Map; import com.google.api.ads.adwords.axis.factory.AdWordsServices; import com.google.api.ads.adwords.axis.v201406.cm.ApiException; import com.google.api.ads.adwords.axis.v201406.cm.Language; import com.google.api.ads.adwords.axis.v201406.cm.Location; import com.google.api.ads.adwords.axis.v201406.cm.Money; import com.google.api.ads.adwords.axis.v201406.cm.Paging; import com.google.api.ads.adwords.axis.v201406.o.Attribute; import com.google.api.ads.adwords.axis.v201406.o.AttributeType; import com.google.api.ads.adwords.axis.v201406.o.IdeaType; import com.google.api.ads.adwords.axis.v201406.o.LanguageSearchParameter; import com.google.api.ads.adwords.axis.v201406.o.LocationSearchParameter; import com.google.api.ads.adwords.axis.v201406.o.LongAttribute; import com.google.api.ads.adwords.axis.v201406.o.MoneyAttribute; import com.google.api.ads.adwords.axis.v201406.o. RelatedToQuerySearchParameter; import com.google.api.ads.adwords.axis.v201406.o.RequestType; import com.google.api.ads.adwords.axis.v201406.o.SearchParameter; import com.google.api.ads.adwords.axis.v201406.o.StringAttribute; import com.google.api.ads.adwords.axis.v201406.o.TargetingIdea; import com.google.api.ads.adwords.axis.v201406.o.TargetingIdeaPage; import com.google.api.ads.adwords.axis.v201406.o.TargetingIdeaSelector; import com.google.api.ads.adwords.axis.v201406.o. TargetingIdeaServiceInterface; import com.google.api.ads.adwords.axis.v201406.o.Type_AttributeMapEntry; import com.google.api.ads.adwords.lib.client.AdWordsSession; import com.google.api.ads.common.lib.auth.OfflineCredentials; import com.google.api.ads.common.lib.auth.OfflineCredentials.Api; import com.google.api.ads.common.lib.conf.ConfigurationLoadException; import com.google.api.ads.common.lib.exception.OAuthException; import com.google.api.ads.common.lib.exception.ValidationException; import com.google.api.client.auth.oauth2.Credential; ... -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/2d038c46-3a90-45cd-92d4-8e706d761aae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v201209] Discrepancy between API results and web UI search volume results
I just came Accross this issue, initialy i taught every thing was working
fine because the UI and API wer Giving same data, bt as the number of
keywords kept on increasing i saw difference of about 100 times in the
search volume of 30% of the keywords i used.
package uber.keyword.bussiness;
import java.io.IOException;
import java.sql.CallableStatement;
import java.sql.SQLException;
import java.util.HashMap;
import java.util.Map;
import com.google.api.ads.adwords.axis.factory.AdWordsServices;
import com.google.api.ads.adwords.axis.v201406.cm.ApiException;
import com.google.api.ads.adwords.axis.v201406.cm.Language;
import com.google.api.ads.adwords.axis.v201406.cm.Location;
import com.google.api.ads.adwords.axis.v201406.cm.Money;
import com.google.api.ads.adwords.axis.v201406.cm.Paging;
import com.google.api.ads.adwords.axis.v201406.o.Attribute;
import com.google.api.ads.adwords.axis.v201406.o.AttributeType;
import com.google.api.ads.adwords.axis.v201406.o.IdeaType;
import com.google.api.ads.adwords.axis.v201406.o.LanguageSearchParameter;
import com.google.api.ads.adwords.axis.v201406.o.LocationSearchParameter;
import com.google.api.ads.adwords.axis.v201406.o.LongAttribute;
import com.google.api.ads.adwords.axis.v201406.o.MoneyAttribute;
import com.google.api.ads.adwords.axis.v201406.o.
RelatedToQuerySearchParameter;
import com.google.api.ads.adwords.axis.v201406.o.RequestType;
import com.google.api.ads.adwords.axis.v201406.o.SearchParameter;
import com.google.api.ads.adwords.axis.v201406.o.StringAttribute;
import com.google.api.ads.adwords.axis.v201406.o.TargetingIdea;
import com.google.api.ads.adwords.axis.v201406.o.TargetingIdeaPage;
import com.google.api.ads.adwords.axis.v201406.o.TargetingIdeaSelector;
import com.google.api.ads.adwords.axis.v201406.o.
TargetingIdeaServiceInterface;
import com.google.api.ads.adwords.axis.v201406.o.Type_AttributeMapEntry;
import com.google.api.ads.adwords.lib.client.AdWordsSession;
import com.google.api.ads.common.lib.auth.OfflineCredentials;
import com.google.api.ads.common.lib.auth.OfflineCredentials.Api;
import com.google.api.ads.common.lib.conf.ConfigurationLoadException;
import com.google.api.ads.common.lib.exception.OAuthException;
import com.google.api.ads.common.lib.exception.ValidationException;
import com.google.api.client.auth.oauth2.Credential;
import com.google.api.client.googleapis.auth.clientlogin.
ClientLoginResponseException;
import java.sql.Connection;
import uber.connection.Dbcon;
import uber.keywordbeans.AdwordBean;
import uber.keywordbeans.GoogleAPIBean;
public class Calculate_CPC_MCC {
private static final String clientId =
private static final String clientSecret =
private static final String refreshToken =
private static final String developerToken =
private static final String userAgent =
public AdwordBean getCPC_MCC(String keyword) throws
ClientLoginResponseException, IOException, ValidationException,
ConfigurationLoadException, OAuthException, ApiException,
ClassNotFoundException, InstantiationException, IllegalAccessException,
SQLException
{
String[] keywords=new String[]{keyword};
String finalresult=;
String[] locationNames = new String[] { Paris, Quebec, Spain,
Deutschland };
String kwd=keyword;
Long monthlySearches=null;
String monthltSearches_string=--;
Money avgCpc=null;
int k_id=0;
String k=--;
AdwordBean ad=new AdwordBean();
Connection con=new Dbcon().getConnection();
try {
Credential oAuth2Credential = new OfflineCredentials.Builder()
.forApi(Api.ADWORDS)
.withClientSecrets(clientId, clientSecret)
.withRefreshToken(refreshToken)
.build()
.generateCredential();
AdWordsSession session = new AdWordsSession.Builder()
.withDeveloperToken(developerToken)
.withUserAgent(userAgent)
.withOAuth2Credential(oAuth2Credential)
.build();
AdWordsServices adWordsServices = new AdWordsServices();
TargetingIdeaServiceInterface targetingIdeaService = adWordsServices.
get(session,TargetingIdeaServiceInterface.class);
TargetingIdeaSelector selector = new TargetingIdeaSelector();
selector.setRequestType(RequestType.STATS);
selector.setIdeaType(IdeaType.KEYWORD);
selector.setRequestedAttributeTypes(new AttributeType[] {
AttributeType.KEYWORD_TEXT, AttributeType.SEARCH_VOLUME,
AttributeType.AVERAGE_CPC
});
Language language = new Language();
language.setId(1000L);
Location location = new Location();
location.setId(2356L);
RelatedToQuerySearchParameter relatedToQuerySearchParameter = new
RelatedToQuerySearchParameter();
relatedToQuerySearchParameter.setQueries(keywords);
LocationSearchParameter locationSearchParameter = new
LocationSearchParameter();
locationSearchParameter.setLocations(new Location[] { location });
Re: [v201209] Discrepancy between API results and web UI search volume results
In case anyone stumbled on this thread, this has been addressed in v201302. Even though the migration notes didn't mention anything about it, a new search parameter has been added to support custom network targeting. In PHP, the required code is as follows: ?php $networkSetting = new NetworkSetting(); $networkSetting-targetContentContextual = false; $networkSetting-targetContentNetwork = false; $networkSetting-targetGoogleSearch = true; $networkSetting-targetSearchNetwork = false; $networkSetting-targetPartnerSearchNetwork = false; $networkSearchParameter = new NetworkSearchParameter(); $networkSearchParameter-networkSetting = $networkSetting; // And don't forget to add the parameter in your selector object $selector-searchParameters[] = $networkSearchParameter; ? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v201209] Discrepancy between API results and web UI search volume results
The earliest we'd be able to add such support is in the next major release. See this blog posthttp://googleadsdeveloper.blogspot.com/2012/08/release-schedule-for-adwords-api.htmlabout our published release schedule. - Kevin Winter AdWords API Team On Thursday, November 22, 2012 6:49:41 AM UTC-5, Adwords user wrote: On Friday, November 9, 2012 12:48:39 AM UTC+8, Kevin Winter wrote: We recently published a blog post talking about these numbers: http://googleadsdeveloper.blogspot.com/2012/11/understanding-adwords-api.html Any update on the plan mentioned in that blog post? Now that v201109 is officially offline (it still worked until Nov. 19), we don't have any way to retrieve the *correct* local search volume of keywords. Just like what Adrian Perez said, the API behavior shouldn't have been changed in the first place. And if it's really needed, you should've at least left your clients a way to retrieve the same old values - either by leaving the deprecated APIs online or by immediately releasing a new version that supports those values -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Haha! That's a joke right? You guys really take the piss, and you really get too much money and credits for the poor service you provide... Not once did I see a customer oriented answer, and not once did you guys apologise or at least pretend to be sorry... Amazing... -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
On Friday, November 9, 2012 12:48:39 AM UTC+8, Kevin Winter wrote: We recently published a blog post talking about these numbers: http://googleadsdeveloper.blogspot.com/2012/11/understanding-adwords-api.html Any update on the plan mentioned in that blog post? Now that v201109 is officially offline (it still worked until Nov. 19), we don't have any way to retrieve the *correct* local search volume of keywords. Just like what Adrian Perez said, the API behavior shouldn't have been changed in the first place. And if it's really needed, you should've at least left your clients a way to retrieve the same old values - either by leaving the deprecated APIs online or by immediately releasing a new version that supports those values -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Same results everywhere from everyone. I'm not judge of anything, but I don't really like this move. I mean, what's in for users? The takeaway here is, and correct me if I'm wrong, that you can't simply get global monthly searches without the google partners results in new api versions, coupled to the fact that old API versions are no longer usable, leaves the clients with little to none alternatives. I'm using the global network, as a last resort, I have to make two separate requests (let me rephrase, the upgrade has forced me to make two separate requests) in order to do a crazy nested hash merge of the global results I want. Is we API users who suffer, at least I'm suffering ;) If they were thinking to include a way to prevent that from happening, such as a filter, IMHO this should have been carried over first, or at least not deprecate the old functionality leaving us without options. Have you found other alternatives to getting those results? Feel free to post if you do. I just did with what I've done. On Tuesday, October 16, 2012 5:37:05 PM UTC-4, Sebastiaan Moeys wrote: I'm migrating my systems From V201109 to V201209, and I'm struggling with a number of things. This issue is related to retrieving search volume for keywords I already know. Googler David Torres said: The new SEARCH_VOLUME is equivalent to GLOBAL_MONTHLY_SEARCHES when no LocationSearchParameter and LanguageSearchParameter are specified, on the flip side SEARCH_VOLUME is equivalent to AVERAGE_TARGETED_MONTHLY_SEARCHES if a language and/or a location is required. So I did a test with the keyword 'games': - *API v201209 | No Targeting:* SEARCH_VOLUME 20,400,000 - *API v201109 | EXACT:* GLOBAL_MONTHLY_SEARCHES 16,600,000 - *Keyword Tool Web UI | EXACT:* Global Monthly Searches 16,600,000 That's about 20% of non-equivalence. Then I did a local/targeted comparison with the Dutch word 'spelletjes', meaning games: - *API v201209 | Dutch | The Netherlands:* SEARCH_VOLUME 1,000,000 - *API v201109 | EXACT | Dutch | The Netherlands:* AVERAGE_TARGETED_MONTHLY_SEARCHES 823,000 - *Keyword Tool Web UI | EXACT | Dutch | The Netherlands:* Global Monthly Searches 823,000 Right now there will be a split between results from the web interface and the API. This split is causing trouble in the team I work in. Some questions: 1. What is the exact difference in behaviour between the two API versions? Why isn't this difference documented? Why isn't there a migration guide? 2. Are you planning on permanently removing match type targeting (i.e. broad/exact/phrase)? If so, could you tell why? Something else than 'back-end changes' would be appreciated. Those back-end changes are made for a reason. Could be a good reason, but we'd like to know. 3. Do you plan on keeping the pre-v2012 features in the UI? That's my greatest concern, since different people will be working with different data. Otherwise very happy to be working with the API you provided, but would like to hear from you about this. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
v201109 officially sunset on 10/26: https://developers.google.com/adwords/api/docs/sunset-dates You should migrate off this version immediately. - Kevin Winter AdWords API Team On Thursday, November 8, 2012 4:42:53 PM UTC-5, Sébastien de Salvador wrote: As far as I'm concerned I think this is a poor decision, the company I work for relies on those numbers and explicitly asked for the local monthly volumes without partners data (or google network as you call it). Don't get me wrong I'm not being judgmental, I'm just the dev in the story, but if for some reason one day I decide to change the behaviour of my applications/code without notice I don't think the business will appreciate it... How long will the 201109 version be supported? The code still works for the moment... On Thursday, November 8, 2012 5:48:39 PM UTC+1, Kevin Winter wrote: We recently published a blog post talking about these numbers: http://googleadsdeveloper.blogspot.com/2012/11/understanding-adwords-api.html Please note that v201109 has sunset and should not be used. - Kevin Winter AdWords API Team On Tuesday, November 6, 2012 11:00:39 AM UTC-5, Sébastien de Salvador wrote: Ah well, I guess we'll stick to v201109 for now since it returns the right numbers... -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
We recently published a blog post talking about these numbers: http://googleadsdeveloper.blogspot.com/2012/11/understanding-adwords-api.html Please note that v201109 has sunset and should not be used. - Kevin Winter AdWords API Team On Tuesday, November 6, 2012 11:00:39 AM UTC-5, Sébastien de Salvador wrote: Ah well, I guess we'll stick to v201109 for now since it returns the right numbers... -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
As far as I'm concerned I think this is a poor decision, the company I work for relies on those numbers and explicitly asked for the local monthly volumes without partners data (or google network as you call it). Don't get me wrong I'm not being judgmental, I'm just the dev in the story, but if for some reason one day I decide to change the behaviour of my applications/code without notice I don't think the business will appreciate it. Fair enough the keyword tool is free of charge as is the I'm just the dev in the story and couldn't care less what numbers are returned, but I can understand the feeling of the analysts behind me -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Forget the last 2 sentences I meant to delete them. Anyway, what I was gonna ask is how long will the 201109 version still be running? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
As far as I'm concerned I think this is a poor decision, the company I work for relies on those numbers and explicitly asked for the local monthly volumes without partners data (or google network as you call it). Don't get me wrong I'm not being judgmental, I'm just the dev in the story, but if for some reason one day I decide to change the behaviour of my applications/code without notice I don't think the business will appreciate it... How long will the 201109 version be supported? The code still works for the moment... On Thursday, November 8, 2012 5:48:39 PM UTC+1, Kevin Winter wrote: We recently published a blog post talking about these numbers: http://googleadsdeveloper.blogspot.com/2012/11/understanding-adwords-api.html Please note that v201109 has sunset and should not be used. - Kevin Winter AdWords API Team On Tuesday, November 6, 2012 11:00:39 AM UTC-5, Sébastien de Salvador wrote: Ah well, I guess we'll stick to v201109 for now since it returns the right numbers... -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Actually I've just noticed that using the attribute SEARCH_VOLUME returns the value from the Google Search Network column, how can I get the value from the Local Monthly Searches column? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Sebastien: 1) Match type is no longer supported in newer API versions. One does wonder why it is still present in the Web UI, still waiting for a response from Google there. 2) SEARCH_VOLUME will return local results if you specify location targeting criteria. Those results seem to be slightly different, but strongly correlated, with local results in the Web UI. On Tuesday, November 6, 2012 4:21:28 PM UTC+1, Sébastien de Salvador wrote: Actually I've just noticed that using the attribute SEARCH_VOLUME returns the value from the Google Search Network column, how can I get the value from the Local Monthly Searches column? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Ah well, I guess we'll stick to v201109 for now since it returns the right numbers... -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
So my code is actually right, thanks for your answer, but the business wants those exact figures, I'm just the dev in the story so I'll stick to the older API :) -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
I'm having the same problem, described here: https://developers.google.com/adwords/api/community/?place=topic%2Fadwords-api%2F_Jx6stWJ7zk%2Fdiscussion -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Any Idea??? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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: [v201209] Discrepancy between API results and web UI search volume results
Hello,
i have the same problem.
The values are equal with the Column google-search-ad-network (sorry for
that translation, i hope you know what i mean) in the External-Keyword-Tool
not with the monthly-local-search.
Here is my java-code:
AdWordsUser user = new AdWordsUser();
TargetingIdeaServiceInterface targetingIdeaService = user
.getService(AdWordsService.V201209.TARGETING_IDEA_SERVICE);
// Create selector.
TargetingIdeaSelector selector = new TargetingIdeaSelector();
selector.setRequestType(RequestType.STATS);
selector.setIdeaType(IdeaType.KEYWORD);
selector.setRequestedAttributeTypes(new AttributeType[] {
AttributeType.KEYWORD_TEXT,
AttributeType.SEARCH_VOLUME,
});
Language language = new Language();
language.setId(1001L);
// Countrycodes
//
http://code.google.com/apis/adwords/docs/appendix/countrycodes.html
Location location = new Location();
location.setId(2276L);
RelatedToQuerySearchParameter relatedToQuerySearchParameter = new
RelatedToQuerySearchParameter();
relatedToQuerySearchParameter.setQueries(keywords
.toArray(new String[0]));
LocationSearchParameter locationSearchParameter = new
LocationSearchParameter();
locationSearchParameter.setLocations(new Location[]{location});
LanguageSearchParameter languageSearchParameter = new
LanguageSearchParameter();
languageSearchParameter.setLanguages(new Language[]{language});
selector.setSearchParameters(new SearchParameter[] {
relatedToQuerySearchParameter, locationSearchParameter,
languageSearchParameter });
selector.setLocaleCode(DE);
Paging paging = new Paging();
paging.setStartIndex(0);
paging.setNumberResults(keywords.size());
selector.setPaging(paging);
TargetingIdeaPage page = targetingIdeaService.get(selector);
TargetingIdea[] ideaArray = page.getEntries();
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
[v201209] Discrepancy between API results and web UI search volume results
I'm migrating my systems From V201109 to V201209, and I'm struggling with a number of things. This issue is related to retrieving search volume for keywords I already know. Googler David Torres said: The new SEARCH_VOLUME is equivalent to GLOBAL_MONTHLY_SEARCHES when no LocationSearchParameter and LanguageSearchParameter are specified, on the flip side SEARCH_VOLUME is equivalent to AVERAGE_TARGETED_MONTHLY_SEARCHES if a language and/or a location is required. So I did a test with the keyword 'games': - *API v201209 | No Targeting:* SEARCH_VOLUME 20,400,000 - *API v201109 | EXACT:* GLOBAL_MONTHLY_SEARCHES 16,600,000 - *Keyword Tool Web UI | EXACT:* Global Monthly Searches 16,600,000 That's about 20% of non-equivalence. Then I did a local/targeted comparison with the Dutch word 'spelletjes', meaning games: - *API v201209 | Dutch | The Netherlands:* SEARCH_VOLUME 1,000,000 - *API v201109 | EXACT | Dutch | The Netherlands:* AVERAGE_TARGETED_MONTHLY_SEARCHES 823,000 - *Keyword Tool Web UI | EXACT | Dutch | The Netherlands:* Global Monthly Searches 823,000 Right now there will be a split between results from the web interface and the API. This split is causing trouble in the team I work in. Some questions: 1. What is the exact difference in behaviour between the two API versions? Why isn't this difference documented? Why isn't there a migration guide? 2. Are you planning on permanently removing match type targeting (i.e. broad/exact/phrase)? If so, could you tell why? Something else than 'back-end changes' would be appreciated. Those back-end changes are made for a reason. Could be a good reason, but we'd like to know. 3. Do you plan on keeping the pre-v2012 features in the UI? That's my greatest concern, since different people will be working with different data. Otherwise very happy to be working with the API you provided, but would like to hear from you about this. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
