Hi Eric,
with the new api v200909 everything works fine.
Harald
On Mar 26, 10:54 pm, AdWords API Advisor
adwordsapiadvi...@google.com wrote:
Hi Harald,
From what I can tell this bug has not yet been fixed in the v13
version of the API. Given the sunset of the v13 campaign management
Hi Harald,
From what I can tell this bug has not yet been fixed in the v13
version of the API. Given the sunset of the v13 campaign management
services on April 22nd, I would urge you to migrate your code to the
v200909 version of the API which doesn't have this issue.
Best,
- Eric
On Mar 25,
Hi Eric,
the link:
http://www.mail-archive.com/adwords-api@googlegroups.com/msg02065.html
Thanks,
Harald
On Mar 23, 5:39 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hi Harald,
Can you link to the original thread so I can get more background
information on this problem? Do
Hi Harald,
Can you link to the original thread so I can get more background
information on this problem? Do you have the SOAP XML from your
request that generates this error?
Best,
- Eric Koleda, AdWords API Team
On Mar 22, 2:41 pm, Harald Bartel harald.bar...@prozentor.de wrote:
Hello,
Hi Harald,
Can you link to the original thread so I can get more background
information on this problem? Do you have the SOAP XML from your
request that generates this error?
Best,
- Eric Koleda, AdWords API Team
On Mar 22, 2:41 pm, Harald Bartel harald.bar...@prozentor.de wrote:
Hello,
Hello,
this bug seems not to be fixed.
What shoud I do if I have this problem?
best regards
Harald
On Mar 4, 1:44 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hello Xavier,
This is a bug that the engineering team is going to have to resolve.
I'll update this thread with
Thanks Jeff! I was on vacation last week, but just catching up now.
We still see this error daily, so if there is any more info you need,
just let me know.
Bryan Jacobs
Marin Software
On Mar 4, 1:44 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hello Xavier,
This is a bug
Hello,
So this appears to be a new variation on an old issue. The common
thread here seems to be that there is an ad group in the same campaign
that contains only placement criteria (no keywords) and that ad group
only has its siteMaxCpc bid set (no keywordMaxCpc). The presence of
this ad group
Thanks a lot Jeff, I was able to reproduce the problem with the
campaign that didn't had the problem, I created a new adgroup with
only site placement, and this reproduced the error.
I can remove those ad groups from the campaigns we own, but for other
customers, I think we can't touch those ad
Hello Xavier,
This is a bug that the engineering team is going to have to resolve.
I'll update this thread with more information when I have it, but
they are actively looking into the issue.
Cheers,
-Jeff Posnick, AdWords API Team
On Mar 4, 2:14 pm, Xavier javier1...@hotmail.com wrote:
Hello,
Hmmm... that is an old issue, and now that you mention it I do
remember it cropping up last year. I'm going to dig a little and see
if this appears to be the same cause. If so, it would explain why
Xavier is seeing inconsistent behavior across different accounts.
Cheers,
-Jeff Posnick,
Hello Xavier,
If you don't have a value set for keywordContentMaxCpc (or you set it
to 0) then the value of keywordMaxCpc will be used for content network
CPC bids instead. So setting keywordMaxCpc will be enough to determine
your content bid in that scenario.
Cheers,
-Jeff Posnick, AdWords
I set it zero and the content bid gets set to Auto when I see it
through the web, if I'm not wrong Auto is not the same as using the
search bid (it's an average of keyword bids).
I solve this by editing the bids entering them manually through the
web, but the idea is to use the API to turn this
I created a new campaign and ad group with the same settings, and I
cannot reproduce the problem, it seems it happens only on the account
I'm working. So, I don't know what's going on here with this error (I
already tried setting the keywordMaxCpc only too).
The SOAP request id is:
requestId
Hi, setting only keywordMaxCpc works fine, but it sets the search max
cpc, not the content one, and what I want to do is to set the content
max cpc.
The request id that succeeded is:
requestId soapenv:actor=http://schemas.xmlsoap.org/soap/actor/next;
soapenv:mustUnderstand=0
Hello Xavier,
The explanation you describe may be correct, and if that's the case
then I'd imagine you should just set the keywordMaxCpc property to the
desired bid for the keywords (even though they will only run on the
Content network). Can you try setting that via the API and then check
out
16 matches
Mail list logo
