Interface: AdAdapterDetectOptions

First IsSupported() wins. Custom adapters (via Register) are probed before built-ins. Network-specific signals (FbPlayableAd, ExitApi, dapi, MRAID_ENV.sdk identifiers) are probed before generic MraidAdapter because MRAID-compatible networks usually expose both.

Mintegral is detected by the combined presence of window.{gameReady,gameEnd,gameRetry,install} as functions — those stubs are injected by the Mintegral host environment before the playable script runs. Moloco is NOT probed: it uses Meta's FbPlayableAd contract at runtime, so the registry can't distinguish it from Facebook. Construct MolocoAdapter explicitly when the packaging target is Moloco (runtime behaviour is identical to FacebookAdapter).

Same reasoning excludes Adwords, Appier, Liftoff, Pangle, Rubeex, Smadex, Tiktok and Vungle: all eight run on bare MRAID with no host-set marker, so a probe would be a coin flip and the generic MraidAdapter they inherit from wins anyway with identical behaviour. Pass them through EngineOptions.adAdapter (or Register) when the packaging target needs the name to match. Adikteev IS probed — AK_CLICK_DESTINATION_URL is unambiguous.

Properties

Property	Type
storeUrls?	StoreUrls