My guess would be that it replaces the field but gets a new name so it
won't interfere with existing applications.
Regards,
Christian
On 16 Okt., 11:33, brandon <[EMAIL PROTECTED]> wrote:
> Hi Tim,
>
> Will the First Page Bid information be a new field labeled
> FirstPageBid (as
> inhttp://adwo
Hello Boris,
I wanted to let you know that the engineering team has traced the
source of the bug back to some faulty logic in the keyword variations
code. They're planning on fixing it, but I am afraid I can't provide a
timeline as to when that will go live.
Cheers,
-Jeff Posnick, AdWords API T
I'm trying to use CheckAds but it keeps throwing the exception "There
is an error in XML document (16, 32)". The inner exception is "The
input string was not in the correct format"
I have been using the API for over a year now and have always been
able to get stuff to work. The code is
p
Hi Tim,
Will the First Page Bid information be a new field labeled
FirstPageBid (as in
http://adwords.google.com/support/bin/answer.py?answer=104209&topic=15369)
or will it be replacing the Min Bid field?
If it isn't replacing the Min Bid field, then what will the min bid be
returning? Again in
Hi,
The most likely cause of your problem is that the text in your adverts
does not meet the editorial guidelines, or the text contains
trademarked items. What happens if you try to create the Advert
manually?
Creating and advert costs 50 API units even if the operation fails.
What you should do
That's true, my understanding is that all existing campaigns were
being switched over to enable separate content bids as part of the
larger change.
Could you either pass along the requestId of the call you're making or
at least provide the campaign id in question? I'm not seeing the same
behavior
Here's what I do. We used to pull the keyword performance data via
the API, but the costs (both in Google bills and processing time)
became an issue. We still use the API to pull the campaign and
adgroup information each night for all customers' accounts (those are
"cheap" calls to the API and t
I'm seeing the same thin - I did a spot check and didn't see any with
enableSeparateContentBids set to "true." Here are a couple of
campaign IDs:
9102704
7325619
8331041
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hello Peter,
That exception text is coming from the .NET runtime, not from a SOAP
fault generated on the server. It's not clear from what you posted
whether the exception is triggered before your request is sent or
after the response is received. I'd think it's more likely that your
code is gene
Thanks, I'll pass those along to the engineering team and let you know
what I hear back.
Cheers,
-Jeff Posnick, AdWords API Team
On Oct 16, 1:54 pm, Reed <[EMAIL PROTECTED]> wrote:
> I'm seeing the same thin - I did a spot check and didn't see any with
> enableSeparateContentBids set to "true."
I've gotten the following update from the engineering team: one change
has already been put in place for all accounts, which is that
enableSeparateContentBids is always set to "true" when creating a new
campaign with the AdWords API, regardless of whether its set to "true"
or "false" in the reques
Jeff,
Thanks for the update. Is there an official online location where the
status of this update will be announced, or should we just check back
at this thread?
Thanks,
Bryan
On Oct 16, 3:00 pm, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> I've gotten the following update from the engine
12 matches
Mail list logo
