Being MRAID compliant does not mean an SDK (or ad) is also ORMMA compliant
-- or vice versa.
The web tester at the ORMMA site has modes for you to test both MRAID and
ORMMA ads. Crisp ads created with our Engage platform are compliant with
both standards. I can send you an example if you like.
But ultimately, it sounds like you have built an application that can
display ads according to the ORMMA standard and you are requesting an ad
that only follows the MRAID standard. While these standards are very
strongly related, they differ on a couple of key technical issues.
"ormma.expand()" and MRAID APIs use the "mraid" namespace like
* Initialization: The ORMMA reference code uses method initialization like
"ORMMAReady()" and the MRAID API defines event-based initialization like
These two differences are important enough that ad vendors need to support
both for one ad to run in either an MRAID or ORMMA compliant SDK. Sounds
like your ad vendor has chosen only MRAID.
You can either choose to add a facade layer to your current app to follow
the MRAID standard as well, or you can ask your vendor to modify their ad
to comply with ORMMA.