Extended Zone (z2) Ads
On some platforms it may not be possible to show video ads if they place you inside an iframe so your ads track to the platform domain but they don’t provide you with access to their ads.txt file. For these situations we provide the z2 window option that allows you to track ads to your own domain rather than the platform domain so you can manage your own ads.txt file to enable high-CPM video ads.
The z2 windows must be launched from a click event or they will fail. There are many different ways to do this such as using the initial “Run” button, the “X” button from a purchase dialog or a specific button to watch reward videos. The normal ad windows will run without a click event but if you are stuck in a situation where your ads are tracking to the iframe owner and you cannot access the ads.txt file, then you will only be able to show banners and rich media ads using the fallback: option.
To entable z2 windows first add your option values to the z2index.html template found in the download package available from the link on the Games page on the Applixir website. Use the same options as your current integration and make sure to comment out any options you don’t need. Then place this file in the same directory your game is running from. Make sure to place an ads.txt file in the root directory of your game domain. Contact Applixir for a copy of an ads.txt file if you do not already have one since it must contain the correct publisher ID’s or you will not receive videos from the ad networks.
Once the z2index.html file is installed, place a new option in your existing integration block as follows:
The system will center the window over your game screen but if you wish to modify the placement you can add an option as follows (make sure there are no spaces inside the quotes):
As mentioned above, make sure you call invokeApplixirVideoUnit(options) from inside an onClick event or it will fail.