Google AMP pages potential problems

Due to the way Google AMP is set up, every third-party embed code must be served through an iframe. 

This means that whenever you embed a Brid player through the provided AMP embed codes, each player is pushed through an iframe which is hosted by us, on our domain and cached under our CDN.

A potential problem that you may experience when used on AMP pages is that your advertiser may not be able to resolve your domain as the player is served through our iframe. In this case, if your ad provider cannot resolve your domain through Google AMP pages, you may experience a decrease in fill rate on players displayed on these pages.

There is currently no workaround to this problem unless you plan on creating your own Google AMP module where you would be hosting custom iframes which serve our player. Although this is possible, you will need considerable dev resources to do this and would have to pass Google's strict policies for creating AMP modules.

Furthermore, due to these limitations, certain player options like sticky players and 50% in-view options also won't be able to work.

Note: If you do any custom change to any video snapshot inside Brid (outside of the initial one that our system creates), the placeholder image for your AMP player will revert back to a default Brid image.