Limitations

The following are a few limitations/caveats that you may encounter during AMP implementation.

• AMP Consent Framework
  • When users consent or reject, the consentState is sent as either accept or reject (dismiss is not used by InMobi CMP). InMobi CMP treats partial consent as an accept action. The consentString contains the TCF consent string.
  • The TCString is passed to AMP as consentString but support of the string itself depends on the vendor's <amp-ad></amp-ad> implementation.
  • TCString is currently available only to amp-ad and amp-iframe components. AMP Project issue #30385 details an in-development feature to expose the postMessage API of TCFv2 to other components in AMP, which we intend to support when released.
  • consentMetadata is NOT currently exposed to amp-ad, therefore vendors cannot read it even though we’re setting it. This limitation is tracked as issue #30786.
  • IE11 is not supported. There are several open issues in the AMP project on this.
• InMobi CMP AMP configuration limitations
  • InMobi CMP AMP does not yet support WordPress.
  • Non-IAB Vendors' consent is not available in InMobi CMP AMP.
  • Group-level consent storage is not supported. We use the built-in AMP consent-string storage mechanism which is always site-local.
  • The InMobi CMP AMP UI always uses the summary page (displayed in the "bottom tray" position) as the first screen.
  • InMobi CMP AMP does not support configuring custom CSS for AMP through the portal. Basic CMP styling can be done through the Customize UI feature within our portal, and other styling can be done through style CSS on the AMP page.