OptionaladServer?: "ad-manager"OptionalbannerSizes?: MultiFormatBannerSize[]OptionalrequestCount?: 1OptionalstalenessWindowMillis?: numberPublisher staleness window in milliseconds. When omitted, the request applies the one-hour guidance default for display formats and records that source on each handle. Not the SDK's cache timeout.
One AdLoader-style request where native and/or GAM banner formats compete for a single winner.
This is multi-format, not multi-count:
requestCountis fixed at 1. Banner requiresbannerSizes; adaptive sizes are excluded because no view width exists at request time.FLUIDis excluded because the attach-onlyMultiFormatBannerAdViewis sized fromhandle.sizeand has no channel for the height a fluid creative settles on after render (the SDKs themselves acceptFLUIDin an AdLoader banner request). The banner arm is Google Ad Manager only, soadServeraccepts only'ad-manager'. Custom native formats compete only throughMultiFormatCustomNativeAdRequestOptions.TypeScript excludes known-illegal size/count values. Runtime creation still validates facts types cannot express, including an empty format list, banner without sizes, and an AdMob unit used with banner.