Thanks Jeff. We'll try adding with less info if the with-address
addition fails.
Pete
On Apr 27, 11:45 am, AdWords API Advisor
<adwordsapiadvi...@google.com> wrote:
> Hello Pete,
>
> I'm fairly sure that the AdWords API uses the same (or at least
> substantially similar) geo-coder logic that maps.google.com uses, so
> testing there should be a good indication of what's going on behind
> the scenes.
>
> In the case of your first request, 6a194064142c097a23d760cc206511ab,
> if I search in maps.google.com for the [street address], [city],
> [country] [zip] then I do get a main result and one disambiguation
> result ("Did you mean: ..."). So I do think there is some uncertainty
> as to the correct location for that input, and rather than place the
> ad in the wrong location, the AdWords API will return an error. When I
> search for either [street address], [zip] or [street address], [city],
> [country] then I do get exactly one result back, so I'd think that
> adding the local business ad with less information specified will
> actually lead to a successful request in this case. (I don't know
> enough about how our geo-coder backend works to tell you why that
> would be.)
>
> As for your second request, bcd27c2eb094a001d3b522213e6f14d5, I
> believe your issue is a misspelled street name. There's no
> "Bodenhaner", which is what you're specifying, but there is a
> "Bodenhamer".
>
> Cheers,
> -Jeff Posnick, AdWords API Team
>
> On Apr 27, 9:17 am, Pete Lavetsky <pete.lavet...@gmail.com> wrote:
>
> > Jeff,
>
> > Along the same lines, we also get error messages sometimes stating
> > that "Could not get lat/long for the given name and address".
>
> > In this case, I have an example of Kernersville, US 27284 ... the
> > requestId is bcd27c2eb094a001d3b522213e6f14d5 ... google maps thinks
> > it has a single location in North Caroline
>
> > Pete
>
> > On Apr 27, 9:11 am, Pete Lavetsky <pete.lavet...@gmail.com> wrote:
>
> > > Jeff,
>
> > > Sorry for the delayed response. This particular city / zip combo
> > > always fails. Here is a failed requestId:
>
> > > 6a194064142c097a23d760cc206511ab
>
> > > Pete
>
> > > On Apr 13, 11:52 am, AdWords API Advisor
>
> > > <adwordsapiadvi...@google.com> wrote:
> > > > Hello Pete,
>
> > > > I just successfully added a local business ad with only Nederland,
> > > > US, and the postal code specified when it comes to location. It seems
> > > > to have placed it properly at
>
> > > > http://maps.google.com/maps?q=29.994487999999997,-93.998048
>
> > > > Does the request to create the local business ad using that specific
> > > > geo information always fail, or was it a one-off? If it always fails,
> > > > could you give me the requestId associated with the failure so I can
> > > > investigate further?
>
> > > > Cheers,
> > > > -Jeff Posnick, AdWords API Team
>
> > > > On Apr 7, 9:01 am, "Pete Lavetsky (AdWords API Guru)"
>
> > > > <pete.lavet...@gmail.com> wrote:
> > > > > A small percentage of the Local Business Ads we attempt to add fail
> > > > > due to "More than onepossiblelat/long for location" errors. In one
> > > > > example, the pertinent geographical data we're setting on the Ad is:
>
> > > > > City: Nederland
> > > > > CountryCode: US
> > > > > PostalCode: 77627
>
> > > > > Google Maps seems to think there is only onepossiblelocation for
> > > > > this:http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=nederland...
>
> > > > > The majority of our Local Business Ads additions succeed with only the
> > > > > City, Country, PostalCode criteria set.
>
> > > > > How can we increase the success rate on the rest of our Local Business
> > > > > Ad additions?
>
> > > > > Thanks
> > > > > Pete
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
