Hi Eric, Jeff and others,
first of all, many thanks for all your hard work in writing the
api-libs/examples and providing assistance to the community, it is much
appreciated.
I have a question about the usage of the adwords api, I would like to
perform keyword research by parsing large lists o
:50 pm, AdWords API Advisor
wrote:
> Hi Bram,
>
> I'm not sure I understand the problem. Can you provide an example
> that demonstrates the problem?
>
> Best,
> - Eric
>
> On Dec 30 2010, 7:21 pm,bramiozo wrote:
>
> > Hi Eric,
>
> > is there a consi
t; > > "crédit" (french) returns either nothing or irrelevant data for
> > > > english credit keywords.
>
> > > > Pizza's on me at the next engineer meeting.
>
> > > > In all seriousness, success is the journey, not the destination -
> > Just to confirm, this is the intended behavior.
>
> > > Best,
> > > - Eric
>
> > > On Sep 20, 5:12 pm, AdWords API Advisor
> > > wrote:
>
> > > > Hi,
>
> > > > I believe this was intentional, but I'll circle back with th
Eric,
I have to urge a reconsideration of ignoring accents, this is really
undermining the usefulness of the api
and what is more, of google SE itself. Accents are part of most
languages which have a roman characterset,
they convey meaning and in some cases the presence of accents might
indicate a
rds API Advisor
> wrote:
>
> > Hi,
>
> > I believe this was intentional, but I'll circle back with the
> > engineering team and confirm.
>
> > Best,
> > - Eric Koleda, AdWords API Team
>
> > On Sep 19, 10:23 am, bramiozo wrote:
>
> > &g
Besides the rather large numerical discrepancy between different
backends one thing I noticed was that the accents for the Spanish
terms are ignored, is this a bug or is this intentional ?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://a
Hi Eric,
I saw the new beta doesn't have CPC information yet, is this still
being pursued as a feature in coming
releases ?
Greetings,
Bram
On 3 sep, 23:44, AdWords API Advisor
wrote:
> Hi Hank,
>
> Unfortunately I don't have any information about how the SKTool
> generates suggested bids. Th
ntil a couple months after the
> new version is released. Please note that while we're sharing these
> rough estimates to help you plan your API development, all dates are
> subject to change.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On May 2, 7:11 am, bramiozo w
Dear sir/madam,
can you give some indication about the migration of the
trafficestimator service, right now I want to implement
the service but it would be somewhat of a waste of time if it sunsets
in a month.
Thanks,
Bram
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our
Can anyone comment on this please ?
On Dec 30 2009, 4:57 pm, bramiozo wrote:
> Moderators/Developers, what charactersets are allowed for the
> keywords, specifically for the TargetingIdeaService ?
>
> A term like casino♠ still gets EXACT searches which is obviously
> incorrect, th
Moderators/Developers, what charactersets are allowed for the
keywords, specifically for the TargetingIdeaService ?
A term like casino♠ still gets EXACT searches which is obviously
incorrect, the ♠ seems to be ignored, besides
MiscellaneousSymbols what other unicode ranges are ignored ?
--
You r
Ok, thanks Eric.
On Dec 30, 4:06 pm, AdWords API Advisor
wrote:
> Hi,
>
> Unfortunately it is not possible to control the sorting of the ideas
> returned by the TargetingIdeaService.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On Dec 29, 7:01 pm, bramiozo wrote:
I am processing terms with multiple keywords at a time but the order
in which they come in is not the order of the terms in the output xml,
this is rather inconvenient. Is there any way to get one-on-one input-
output ordering ?
I use the php api library (v. 1.2.1) btw.
--
You received this mess
When will the exact/phrase match results be added to the api, because
imo that's basically what Goose is referring to.
Don't want to be sassy but this has been addressed a looong time ago,
I want to know when people type my keywords exactly, not broadly or in
a phrase,
I am sure I am not the only
body here can help you.
>
> - Jan
>
> On 5 Okt., 16:31, bramiozo <[EMAIL PROTECTED]> wrote:
>
> > It seems I have to decode the utf8 input using utf8_decode.
>
> > On Oct 5, 3:32 pm, bramiozo <[EMAIL PROTECTED]> wrote:
>
> > > Code: soapenv:Server.use
It seems I have to decode the utf8 input using utf8_decode.
On Oct 5, 3:32 pm, bramiozo <[EMAIL PROTECTED]> wrote:
> Code: soapenv:Server.userException
> String: This keyword text is not valid.
>
> Ascii input works fine.
>
> When I output all data, it seems
Code: soapenv:Server.userException
String: This keyword text is not valid.
Ascii input works fine.
When I output all data, it seems the input is urlencoded..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"AdW
perhaps you want to have a look at it if you encounter
> future problems:http://google-apility.sourceforge.net/
>
> - Jan
>
> On 23 Aug., 13:23, bramiozo <[EMAIL PROTECTED]> wrote:
>
> > Found it Jeff, the encoding of the nuSoap class is set to iso-8859-1
> >
lizeEnvelope(...) in class.nusoap_base.php and
nusoap.php
$body=utf8_encode($body);
$headers=utf8_encode($headers);
NuSoap 0.7.2
Thanks for the assistance,
Bram
On Aug 22, 5:52 pm, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> Hello Bramiozo,
>
> All communications with the AdW
Anyone, the tool is rather useless if it outputs ASCII
On Aug 21, 7:31 pm, bramiozo <[EMAIL PROTECTED]> wrote:
> function googleKeywordFromSite($seedUrl,
> $language=0,$locale=0,$includeLinks=0){
> //http://www.google.com/apis/adwords/developer/KeywordToolService.html
21 matches
Mail list logo