Re: [9-2984000003358] TrafficEstimatorSelector value mismatch with UI and API.

2014-04-29 Thread chriss Moyle
Hi Josh, Thank you for your response. For traffic estimate i am following approach. 1. I am passing keywords to Traffic Search Volume API and here both result of keyword planner tool and API gives exact same result and this is great. 2. Once got result from Traffic Search Volume API, I am calcul

Re: [9-2984000003358] TrafficEstimatorSelector value mismatch with UI and API.

2014-04-29 Thread Josh Radcliff (AdWords API Team)
Hi Chriss, I believe my last response addressed the question on TrafficEstimatorService (please correct me if I'm wrong). Could you clarify if you are still seeing differences for *both* TrafficEstimatorService *and *TargetingIdeaService? I ask because in your last post you mentioned the Tra

Re: [9-2984000003358] TrafficEstimatorSelector value mismatch with UI and API.

2014-04-28 Thread chriss Moyle
Hi Josh, I have compared TrafficeEstimatorService and Keyword Planner Tool at the same time but still i am getting slightly different result on both Search Volume and TrafficEstimate service. If you need the request and response xml with screen shots again then please let me know, i will provided

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-28 Thread chriss Moyle
Hi Josh, I have checked by changing the All language to English but get the same result. There is not changes occurs i.e. country is English or all language. Please advice. Thanks, On Mon, Apr 28, 2014 at 7:56 PM, Josh Radcliff (AdWords API Team) < adwordsapiadvisor+j...@google.com> wrote: >

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-28 Thread Josh Radcliff (AdWords API Team)
Hi, I've been looking into this and one thing I noticed immediately was that you are searching for "All languages" in the UI but specifying a single language in your TrafficEstimatorService request. I'll look for any other differences, but please let me know if that resolves the issue. Thanks

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-28 Thread chriss Moyle
Hi, Is there anyone who can help me on this topic. I need your urgent help. as i am stuck on this place. I have already forwarded all information to Josh. Thanks On Mon, Apr 28, 2014 at 9:34 AM, chriss Moyle wrote: > Hi Josh, > > Please let me know your advice regarding data mismatch in API

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-27 Thread chriss Moyle
Hi Josh, Please let me know your advice regarding data mismatch in API and Keyword planner tool. I am waiting from your feedback. It is urgent. Thanks, On Saturday, April 26, 2014 10:24:52 AM UTC+5:30, chriss Moyle wrote: > > Hi Josh, > > I have sent you all required information according to

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-25 Thread chriss Moyle
Hi Josh, I have sent you all required information according to your feedback. Please advice on this. Urgently i need your help for this. Thanks, On Thu, Apr 24, 2014 at 7:38 PM, Josh Radcliff (AdWords API Team) < adwordsapiadvisor+j...@google.com> wrote: > Hi, > > I answered a similar ques

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-24 Thread Josh Radcliff (AdWords API Team)
Hi, I answered a similar question on another post -- could you take a look at my response there to see if it addresses your question? If that doesn't clear things up, please send the following details *only to me* by

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-24 Thread chriss Moyle
Hi Josh, I need you help. Previously i am getting correctly matched values using Google Keyword Planner Tool and API. But now, i am getting slightly difference between values of traffic estimator service and Keyword planner tool. Please advice. Thanks, On Friday, April 18, 2014 6:59:55 PM

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-18 Thread Josh Radcliff (AdWords API Team)
Hi, As you noticed, the account used for the TrafficEstimatorService *will* have an impact on the estimates produced. From the TrafficEstimatorService docs (emphasis mine): Estimates are *account specif

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-18 Thread chriss Moyle
Hi Josh, I need your help for a question. Assume we have 2 MMC accounts and each MMC account having 1 cutomer id as showing below. MMC 1st Account - Customer Id = 111-111- MMC 2nd Account - Customer Id = 222-222- Now, if i am using Customer Id (111-111-) to retrieve values from

Re: TrafficEstimatorSelector value mismatch with UI and API.

2014-04-17 Thread Josh Radcliff (AdWords API Team)
Hi, It sounds like you are setting the bid amount correctly, although you may want to check out the EstimateKeywordTrafficexample in you

TrafficEstimatorSelector value mismatch with UI and API.

2014-04-17 Thread chriss Moyle
Hi, I am working on getting information of Traffic Estimator service. as showing on below url. https://developers.google.com/adwords/api/docs/reference/v201309/TrafficEstimatorService.TrafficEstimatorSelector?hl=fr For this, i am passing "Enter a bid" amount value on "KeywordEstimateRequest"