Can't access or modify BiddingScheme for Maximize Conversion Value and Target Impression Share via API

[Mfallh]

Hi,

We've run into an issue with the Bing Ads API where we can't access or modify the bidding parameters for two specific bidding strategies: Maximize Conversion Value and Target Impression Share.

While we can easily change these settings in the Bing Ads UI, our effort to do this via the API remain with no results because the BiddingScheme object seems to be missing or inaccessible for these two strategy types.

What we're seeing

When working with other bidding strategies like Target ROAS or Target CPA, we can retrieve and update the BiddingScheme object without any issues.
But for campaigns using Maximize Conversion Value or Target Impression Share, we hit a wall - the API doesn't expose these bidding parameters.

This forces us to manually update these campaigns through the UI, which is a major pain point when managing multiple accounts.

Impact on our workflow

We have to:

• Manually identify campaigns using these strategies
• Log into the UI to make adjustments
• Track changes separately outside of our normal API-based workflows

Steps to reproduce

1. Create a campaign using either "Maximize Conversion Value" (set a TROAS value) or "Target Impression Share" (set a Max CPC and Target Imp share value) as the bidding strategy
2. Try to retrieve the BiddingScheme object and its parameters via the API using the GetCampaignsByAccountId or GetCampaignsByIds methods
3. Attempt to update these bidding parameters programmatically

You'll notice that unlike other bidding strategies, these two don't expose their BiddingScheme objects through the API.

Ideally, we should be able to:

• Retrieve the current bidding parameters for ANY bidding strategy type
• Update these parameters programmatically via the API
• Have consistent access to BiddingScheme objects regardless of strategy type

Possible solutions

1. Add support for MaximizeConversionValueBiddingScheme and TargetImpressionShareBiddingScheme in the API
2. Ensure these objects expose the same parameters that are available in the UI

Has anyone else run into this issue or found a workaround? Any timeline on when these bidding schemes might be supported in the API?

Thanks for looking into this!

Attachements :