Google AMP Pages Potential Limitations

Due to the structure of Google AMP, all third-party embed codes must be served through an iframe.

As a result, when you embed a TargetVideo player using the provided AMP embed codes, each player is rendered through an iframe that is hosted by us, on our domain, and cached via our CDN.

A potential issue you may encounter on AMP pages is that your ad provider might not be able to resolve your domain since the player is served within our iframe. If the ad provider cannot resolve your domain through Google AMP pages, you may see a decrease in fill rates for ads on these players.

Currently, there is no straightforward workaround for this issue unless you create your own custom Google AMP module. This would involve hosting custom iframes to serve our player. While this is technically possible, it requires significant development resources and must comply with Google’s strict policies for creating AMP modules.

Additionally, due to these limitations, certain player features, such as sticky players and the 50% in-view option, will not work as expected on AMP pages.

Note: If you make any custom changes to the video snapshot within TargetVideo (outside of the initial one generated by our system), the placeholder image for your AMP player will revert to a default TargetVideo image.