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 enableSeparateContentBids value set to true.
While you can currently make a call to updateCampaign() and manually set this value to false, last week's change to the default behavior of new campaigns was made in anticipation of a larger change that is in the works for the AdWords API. We are planning on changing the behavior of the enableSeparateContentBids campaign attribute in v12 of the AdWords API so that it is always set to true. Here's a rundown of the implications for developers of this planned change: If you currently have an existing campaign with enableSeparateContentBids set to false, then your campaign will automatically have this attribute swtiched to true once this change goes live. The keywordContentMaxCpc values of the ad groups in such a campaign will default to 0, though, meaning that the keywordMaxCpc bid value will be used instead. This effectively means that the campaign will behave as it previously did, with the keywordMaxCpc bid used for both the search and content networks. If you currently have an existing campaign with enableSeparateContentBids set to true, your campaign's settings will remain the same once this change goes live and any keywordContentMaxCpc bids in ad groups will continue to be used for the content network. If an ad group doesn't have an explicit keywordContentMaxCpc set then the keywordMaxCpc value will continue to be used for both the search and content network as before. The most noticeable difference takes place if you make an updateCampaign()/updateCampaignList() call on a campaign and set enableSeparateContentBids to false in your update. First of all, the enableSeparateContentBids attribute will continue to be returned as true--it will not be possible to set this to false. Additionally, the value of the keywordContentMaxCpc attribute in any ad groups in that camapaign will be set to 0, which will effectively disable separate content bids and ensure that that default keywordContentCpc value is used instead. This means that the end result will be the same behavior as what would previously happen if enableSeparateContentBids were false. Please do note that the previous value of keywordContentMaxCpc in each ad group will be wiped out in the process. There will be an official update to the documentation to reflect all this when the changes go live, but it's important enough that we wanted to give everyone a heads-up in advance. We expect the changes mentioned above to be implemented next week, around September 23. I'll post again when the changes are live. Cheers, -Jeff Posnick, AdWords API Team On Sep 15, 4:04 pm, bryanjj <[EMAIL PROTECTED]> wrote: > I have seen this as well. Anyone have any ideas on what is wrong and > when it will be fixed? > > Thanks, > Bryan > > On Sep 12, 12:27 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > When I add a new campaign using the api, my request includes a > > Campaign with enableSeparateContentBids = false, but the Campaign in > > the addCampaignList response has enableSeparateContentBids = true. > > > Any ideas ? Are there other Campaign settings that might cause this to > > happen ? I am using api v12, java / axis. I can post the soap request > > if that is helpful, > > > thanks, > > -j --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
