traffic estimation service - problematic results when using proximity targets

[Guy Zucker]

Hi,

 

I'm using the v13 traffic estimation service and I receive peculiar results when setting proximity targets  (radius geo targets).

 

The following is example data I'm getting for a single keyword input (the output I get is max # clicks per month (aggregation of max daily clicks))

 

keyword input: jordan shoes

 

geo-target input parameter                                            output

no geo target                                                                10018

the US                                                                         9149                                                              

TX                                                                                304

Dallas Ft. Worth (Metro)                                                129

400 miles around 7826 la cabeza drive, Dallas                 10018

30 miles around 7826 la cabeza drive, Dallas                   10018

 

Are proximity targets not supported for traffic estimation?

 

Thanks,

 

Guy

[AdWords API Advisor]

Hi Guy,

ProximityTargets are not supported in the TrafficEstimatorService.
See the following thread for more details:

http://groups.google.com/group/adwords-api/browse_thread/thread/4bc5438e565bf135/

Best,
- Eric Koleda, AdWords API Team