Hi,
We've made some improvements to *LocationCriterionService* and it now
returns a reach of 1,160,000 for location ID 1019250.
Cheers,
Josh, AdWords API Team
On Sunday, January 5, 2014 7:08:26 AM UTC-5, Ittai Chorev wrote:
>
> Great, Thanks!
> We haven't found any other discrepancies between t
Great, Thanks!
We haven't found any other discrepancies between the UI and API - I'll let
you know if we do.
On Friday, January 3, 2014 6:30:08 PM UTC+2, Josh Radcliff (AdWords API
Team) wrote:
>
> Hi,
>
> I have confirmed the behavior you described. We're aware of this and
> looking into it o
Hi,
I have confirmed the behavior you described. We're aware of this and
looking into it on our side, and I'll post an update once I have more
information.
If you have any other locations where you see a *Reach* of zero, please
pass those along so I can investigate those as well.
Cheers,
Jos
For criteria ID: 1019250 (Detroit,Michigan,United States)
API returns reach "0" instead of reach 295,000 that you see in the UI.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com
http://groups.google.com/g
