Hello,
According to documentation
API_docs adServingOptimizationStatus is strictly related to selected campaign bidding strategy type. In particular, as it is described, adServingOptimizationStatus=CONVERSION_OPTIMIZE is possible only if campaign's bidding strategy is
CONVERSION_OPTIMIZER:
Ad serving is optimized based on CTR * Conversion for the campaign. If the campaign is not in the conversion optimizer bidding strategy, it will default to OPTIMIZED
Somehow, it is still possible to set adServingOptimizationStatus=CONVERSION_OPTIMIZE having bidding strategy set as
MANUAL_CPC.
The question is: is it a bug in documentation? Or maybe I've missed something?
Please help, as I'm not sure if the campaign configured in that way will perform as intended...
Best regards,
Robert.
Below is a part of XML (API response - CampaignService.get) showing the mentioned state:
<elem>
<biddingStrategyConfiguration>
<biddingStrategySource nil="true" />
<biddingScheme nil="true" />
<bids type="array" />
<biddingStrategyId nil="true" />
<biddingStrategyName nil="true" />
<biddingStrategyType>MANUAL_CPC</biddingStrategyType>
</biddingStrategyConfiguration>
<networkSetting nil="true" />
<name type="string">rr5033 DISP Conv</name>
<adServingOptimizationStatus>
CONVERSION_OPTIMIZE
</adServingOptimizationStatus>
<forwardCompatibilityMap type="array" />
<status>ENABLED</status>
...
</elem>