.Net BingAds SDK BingAds Keyword MatchType AIOptimized causing parsing errors when reading from Bulk report

The MatchType value set in the Microsoft Advertising APIs and Bulk schema currently only defines the following values:

• Broad
• Exact
• Phrase

In Ad Insight, there is also an Aggregate value for reporting, but AIOptimized is not part of any documented MatchType enumeration or Bulk schema in the provided references.

Because AIOptimized is not a valid value in the published MatchType value set, the .NET Bing Ads SDK (and any code generated from the WSDL) will fail to parse it. The SDK expects only the documented enumeration values and will throw when encountering an unknown string.

Given the available information, the only supported approach is to restrict processing to the documented MatchType values and treat any other value (such as AIOptimized) as unsupported or invalid. For example, when reading Bulk rows, custom parsing logic can:

1. Read the raw Match Type column as a string.
2. Map Broad, Exact, and Phrase to the corresponding enum values.
3. For any other value (including AIOptimized), either:
   • Skip the row, or
   • Map it to a fallback value only in local code (e.g., a custom enum or string field), without attempting to bind it to the official MatchType enum.

However, since AIOptimized is not documented in the current API or Bulk contracts, there is no supported way—based on this context—to use it as a first‑class MatchType in the .NET SDK. Any long‑term resolution would require an SDK and contract update from Microsoft Advertising so that AIOptimized is added to the official MatchType value set.

References:

• MatchType Value Set - Ad Insight
• MatchType Value Set - Campaign Management
• KeywordAndMatchType Data Object - Ad Insight
• Negative Keyword List Record - Bulk
• Bulk Data Objects
• BroadMatchKeywordOpportunity Data Object - Ad Insight
• KeywordIdEstimatedBid Data Object - Ad Insight
• UseBroadMatchKeywordRecommendation Data Object - Ad Insight