Skip to content

FAQs for Nostra

What are the possible integrations available on the Nostra?

You can integrate the following opportunities on the Nostra:

  • Rewarded screen (Replay, revive, level-up): Full-screen video and banner ads

  • Loading page: Banner (300x250 pixels) ads

  • Glance analytics

  • pauseEvent() and resumeEvent() methods

Should the game be responsive for different screen sizes?

Yes, the game must be responsive for all Android screen sizes.

Where should I put the integration files?

Put all integration-related files in the root folder of the game codebase.

What is the ideal order of integration?

You should integrate the screens as mentioned below:

<!--======================Ads===========================-->    
  <script type="text/javascript" src="./ads.js"></script>

What should be the size of the game?

The game size should be within 35-40 MB.

What should be the game loading time?

The ideal game loading time should be less than 15 seconds.

Should the game sound be on when playing the rewarded screen video ad?

The game sound should pause automatically when a video ad plays and resume the sound after the ad.

What are the testing edge cases for the ads?

You can find the edge cases in Integration testing.

How to implement rewarded ads on the Revive page?

Create a prompt page linked to the revive button, where players can opt to see the rewarded ad before the game grants them a revival. Call the rewarded ad function on the prompt page.

Why can’t the players see the rewarded ads?

Recheck the integration process based on the Game Monetization documentation. Make sure you have enabled test mode.

Can I test Glance Analytics integration before sending the final build to the Glance Account Manager?

You can test Glance Analytics integration using the Google Chrome Inspect tool before sending the final build to the Glance Account Manager. You can inspect all the possible events. For more help on the integration testing, contact your Glance Account Manager.

What is the impact of ‘__split’ and ‘__GPID not populated properly' errors in the Google Chrome console during testing? How to fix the errors?

You can ignore these errors. You won’t find them after the game goes live on the Nostra, as Glance SDK populates the required values.

Can we modify the libraries provided by the Glance team?

You may not require to change in most cases. If you see some required changes, contact your Glance Account Manager for the changes.

What are the macros of the game URL?

Append the following macros after your game URL:

?userid=$USER\_ID&apikey=$API\_KEY&impId=$IMP\_ID&glanceId=$GLANCE\_ID&gpid=$GPID&LPMREC=true