Hi Eric,
with the new api v200909 everything works fine.
Harald
On Mar 26, 10:54 pm, AdWords API Advisor
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
> services on April 22nd, I wou
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
wrote:
> 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
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 wrote:
> Hello,
>
> this bug seems not to be fi
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 wrote:
> Hello,
>
> this bug seems not to be fi
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
wrote:
> 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
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
wrote:
> Hello Xavier,
>
> This is a bug that the engineering team is
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 wrote:
> Thanks a lot Jeff, I was
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 g
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
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, A
Jeff,
We also saw this error yesterday for the first time in over a year.
Before this was caused by a data issue on Google servers (support
#246301284):
"The corrupt ad groups were due to a problem on our end; they were
basically incomplete ad groups, incorrectly created due to a bug which
shoul
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
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 API
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:
http://schemas.xmlsoap.org/soap/actor/next";
soapenv:mustUnderstand="0" xmlns="https://adwords.google.com/api/
ad
Hello Xavier,
The request you just referenced shows the same behavior as the
previous request, in that you're trying to set keywordContentMaxCpc on
an ad group that has search disabled. Could you please try just
setting keywordMaxCpc for that type of ad group, and if it fails,
provide a requestI
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:
http://sche
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 t
Thanks Jeff, I work on a company that does updates the Google
campaigns on behalf of our customers, I got to ask my bosses first
before posting a soap request id or other customer information.
>From what investigated, this code worked for one customer that had
search and content networks selected
Hello Xavier,
Okay, I just wanted to clarify your actual intent before debugging
this further, as your variable names indicated that you might be doing
something other than what you wanted.
The most straightforward way of determining what is triggering this
error would be for me to look up you
Hello, thanks for your reply, the code actually tries to update an
adgroup not adding a new one.
I read on the API documentation that in the updateAdGroup() call, if
you omit one parameter, it will maintain the original value:
http://code.google.com/apis/adwords/docs/developer/AdGroupService.html
Hello Xavier,
Backing up a bit, based on the snippet of code you provided, I don't
think you're going about things the right way.
The snippet suggests you're trying to create a new ad group. If
that's the case, you should not set the id of the ad group (because
you don't know it in advance) an
22 matches
Mail list logo