Hello Bryan,
This behavior won't be rolled out all at once, and some accounts will
see it earlier than others. (I don't know what the exact criteria is
for determining which accounts will see the change first.)
For that reason, I'd recommend that you just empirically determine
whether your acc
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
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
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'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
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
This is simply a getCampaign() service call which is returning
enableSeparateContentBids = false. According to your previous post:
"your campaign will automatically have this attribute swtiched to true
once this change goes live."
Thanks,
Bryan
On Oct 15, 11:03 am, AdWords API Advisor
<[EMAIL
Hello Bryan,
Sorry for the delay in getting back to you. This behavior should
already have gone live. I'm not sure whether you're seeing a
discrepancy while updating an existing campaign or creating a new one,
but it would be great if you could provide either an anonymized SOAP
request/response
Any updates?
Thanks,
Bryan
On Oct 6, 1:31 pm, bryanjj <[EMAIL PROTECTED]> wrote:
> Jeff,
>
> We are still receiving responses with enableSeparateContentBids =
> false. What is the status of this change? What is the best way to be
> notified when the change goes live?
>
> Thanks,
> Bryan
>
> On
Jeff,
We are still receiving responses with enableSeparateContentBids =
false. What is the status of this change? What is the best way to be
notified when the change goes live?
Thanks,
Bryan
On Sep 17, 5:30 pm, bryanjj <[EMAIL PROTECTED]> wrote:
> Jeff,
>
> Thanks for the update. Just to cla
Hello Bryan,
There won't be any mass update to the NetworkTargeting setting. If
you don't already target the content network then nothing should
change regarding that.
Cheers,
-Jeff Posnick, AdWords API Team
On Sep 17, 8:30 pm, bryanjj <[EMAIL PROTECTED]> wrote:
> Jeff,
>
> Thanks for the upd
Jeff,
Thanks for the update. Just to clarify, does this change affect the
NetworkTargeting setting? So if the campaign is only targeting the
search network, this change should have no effect?
-Bryan
On Sep 17, 7:44 am, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> Thanks for bringing up t
Thanks for bringing up this behavior, and apologies for any
inconvenience or confusion this may have caused. As of last week,
regardless of what value is set for enableSeparateContentBids in the
addCampaign()/addCampaignList() call, the new AdWords campaign will be
created with the enableSeparateC
13 matches
Mail list logo
