XML request to get traffic for a campaign (or adgroup)

[RockyRaccoon]

I have been searching on this one for days. I can't seem to find
working XML that gets traffic estimations for a campaign or adgroup.
Since I have had zero luck using proximity targets ("circles" mainly)
to get keyword estimates for a specific radius I thought I would
create a geo-targeted campaign, adgroup, insert keywords and then
estimate the traffic for the campaign. However, if I can find a way to
estimate keywords in <circle></circle> that would be ideal. Thanks
ahead of time for the help - I appreciate it.

-Taylor

[AdWords API Advisor]

Hello Taylor,

I'm not 100% sure about the reliability of using proximity targeting
with the TrafficEstimator service. What I'd recommend is that you
follow the steps outlined in this blog post and use named geo
targeting:

http://adwordsapi.blogspot.com/2008/07/traffic-estimator-service-explained.html

Cheers,
-Jeff Posnick, AdWords API Team

[Rockyraccoon]

Yeah, I saw this too... I will take another look and see if it can
help me. Do you have any idea why the service would be "unreliable"? I
am having trouble explaining this to the other people that are working
on the product with me. Basically, I haven't been able to get
"circles" working at all... Is this feature even functional?

-Taylor



On Jun 30, 8:59 am, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:

> Hello Taylor,
>
>  I'm not 100% sure about the reliability of using proximity targeting
> with the TrafficEstimator service. What I'd recommend is that you
> follow the steps outlined in this blog post and use named geo
> targeting:
>

>  http://adwordsapi.blogspot.com/2008/07/traffic-estimator-service-expl...

[Rockyraccoon]

Last thing. Based on the post you mentioned I tried this... I get NO
errors, but if I change the radius from "30000" to "100000" the
numbers remain the same. :-(

<estimateCampaignList>
<campaignRequests>
<adGroupRequests>
<keywordRequests>
<text>muestra</text>
<type>Broad</type>
</keywordRequests>
<maxCpc>30000</maxCpc>
</adGroupRequests>
<networkTargeting>
<networkTypes>SearchNetwork</networkTypes>
<networkTypes>ContentNetwork</networkTypes>
</networkTargeting>
<languageTargeting>en</languageTargeting>
<geoTargeting>
<proximityTargets><circles><latitudeMicroDegrees>54663408</
latitudeMicroDegrees>
<longitudeMicroDegrees>-3363526</longitudeMicroDegrees>
<radiusMeters>10000</radiusMeters>
</circles>
</proximityTargets>
</geoTargeting>
</campaignRequests>
</estimateCampaignList>

[AdWords API Advisor]

Hello Taylor,

I don't know the root cause for this, but I've always observed that
the results you obtain from specifying a named geo target are much
more meaningful than the results you'd get back from a proximity
target when using the TrafficEstimatorService. Do note that we're
dealing with estimates here and there's no single "correct" response,
but I'd recommend sticking with the named geo targets.

Cheers,
-Jeff Posnick, AdWords API Team

[Rockyraccoon]

I really HATE to be a bother but I simply cannot use "named" geos. We
are a local search company that uses proximity targeting with our
adwords campaigns and I need to get estimates using circles instead of
by city or state. I am having trouble understanding why the precise
functionality I need is included in the API but not supported? Is this
the case? Are you telling me this method is broken? If that is the
case can we escalate this so it gets fixed? If not, and there is a way
to get results (more accurate or not) then I am hoping you will help
me.

-Taylor





On Jun 30, 12:39 pm, AdWords API Advisor

[AdWords API Advisor]

Hello Taylor,

Apologies that this has been a source of frustration for you. I dug
around a bit on my end and determined that the team responsible for
providing traffic estimate data is aware of a change that effectively
ignores proximity target data that you pass in to the service. If your
request only contains proximity targets, then you'll get back the same
estimate you would when no geo targeting is specified.

Unfortunately, this is not functionality that they are able to add
back, and my understanding is that the web based version of the
traffic estimator (https://adwords.google.com/select/
TrafficEstimatorSandbox) will be updated to prevent users from
entering proximity or polygon targets. The AdWords API team will not
be making any changes to the v13 TrafficEstimatorService WSDLs at this
point, but I have asked our documentation team to make it clear in the
docs that any proximityTargets you pass in to the service will be
ignored.

Cheers,
-Jeff Posnick, AdWords API Team