Hello Roelf,
Absolutely (provided you use the same ad group ID). This is known as
"sparse updates" -- we recommend to only send the fields you are actually
changing, and an ID to identify the object.
-Danial, AdWords API Team.
On Thursday, May 16, 2013 4:47:35 PM UTC+4, Roelf Jansen wrote:
Hi Danial
As I responded earlier, this workaround does the trick.
I need to confirm that the tempory AdGroup object is just a local construct
& won't be seen as a new AdGroup object in the Campaign ?
We do not want to use the AdGroups' long performance histories.
Regards
Roelf
On Wed, May 15,
Hello Roelf,
It sounds like you are sending a biddingStrategyType or biddingScheme in
the mutate request. I suggest creating a new AdGroup object locally and
setting its ID to the ad group ID value and the status to the one you want.
Please let us know if you still get this error after that.
Hi,
Can you please share the request xml which succeeds with 8.10.1 and the
request xml which throws an error (you mentioned above)?
(Except for sensitive info such as developer token, access token)
In the first place, BiddingStrategyConfiguration with BiddingStrategyType
at AdGroup level is n
O, I forgot to note that this code worked with adwords-api-8.10.1 but is
not working in adwords-api-8.11.1.
On Monday, May 13, 2013 12:10:58 PM UTC+2, Roelf Jansen wrote:
>
>
> I'm trying to enable a paused AdGroup in a Campaign which is set up for
> automatic bidding.
>
> However, when I try t
I'm trying to enable a paused AdGroup in a Campaign which is set up for
automatic bidding.
However, when I try to mutate I'm told I'm not allow to override the
BiddingStrategy. I don't understand how enabling the AdGroup should
trigger a BiddingStrategy exception ?
AdGroup adGroup = (
