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 request. This is the behavior that prompted this thread to begin with.
The other changes mentioned in my earlier post, which were planned to go live around September 23, have not yet been widely rolled out. I'm hearing the familiar timeframe of "next week" as to when accounts should start seeing that new behavior, and that the changed behavior will be rolled out in batches of accounts, so it may take longer for some users to start seeing them. Apologies for the initial confusion. Cheers, -Jeff Posnick, AdWords API Team On Oct 16, 3:52 pm, AdWords API Advisor <[EMAIL PROTECTED]> wrote: > 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." Here are a couple of > > campaign IDs: > > 9102704 > > 7325619 > > 8331041 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
