3 common violations on app of Interstitial Ads

Interstitial ads is one of the most popular ads used by many publishers today. They provide rich interactive advertising for users on mobile applications. They are interactive, full-screen ads that cover the interface of their host app or site. These ads appear between content, so they place at natural transition points or breaks, such as in between activities or game levels. Therefore, failure to follow these guidelines may result in invalid activity and Google disabling ad serving for your app. Here are 3 common violations when placing ads and interstitials.


  1. When the app is loading or exiting.

Don't place interstitials on app load and on app exit, as interstitials should only be placed between pages of app content. And ads should not be placed in applications running in the device's background or outside of the application environment.

  1. Set multiple duplicates.

Examples of non-compliant implementations include, but are not limited to: 

  • Place interstitials ad after each user action, including but not limited to clicks, swipes, and more. Publishers should not place more than one interstitial ad after every two user actions in their app. This requirement is also applied when the user clicks the Back button in the app. 
  • Place an interstitial immediately after another interstitial has been shown and closed by the user.

So we can notice that:

-> The app is not allowed to trigger interstitials every time a user clicks on the app. 

-> Ads should not be placed in a way that prevents viewing of the app's core content. And should not be placed in a way that interferes with the app's navigation or interaction with the core content and functionality

  1. Ad displays suddenly 

Your app shouldn't surprise users with an interstitial. Place interstitials so that they suddenly appear when a user is focused on a task at hand (e.g. playing a game, filling out forms, reading content). This can lead to accidental clicks and often create a frustrating user experience. 

For this reason, interstitials should only be deployed at reasonable breaks between the publisher's app content (e.g. page, stage, or level) to ensure that the user is ready. participate in advertising.

Hope this post is useful for you and hope you have a nice day!

If you have any question, please contact us via sale@appmatic.sg

Recommended Posts

Online publishers are continually exploring new avenues to monetize their content effectively. Display advertising remains a cornerstone of online revenue generation, and Google AdSense is at the forefront of this domain. If you're a Google Publisher looking to optimize your earnings and leverage the power of display advertising, you're in the right place.
Google Publishers are constantly seeking ways to enhance their AdSense revenue. This concise guide is designed to equip publishers with actionable strategies, insights, and best practices. By implementing these proven methods, you can maximize your AdSense earnings and achieve greater success in online publishing.
This guide unveils the art of crafting high-quality ad inventory, empowering publishers to captivate premium advertisers, enhance user experiences, and unlock the full monetization potential of their digital real estate.
Step-by-Step on how you can implement a Dynamic Pricing Strategy and some example of it in action.
As Google Publishers, you're well aware that the industry never stands still. One of the most intriguing developments in recent years is Dynamic Pricing. In this guide, we'll delve into this pricing strategy, exploring its significance, pros and cons, and its diverse variations. Buckle up for an insightful ride into the world of Dynamic Pricing, tailor-made for you.
In the intricate world of digital advertising, where the intersection of technology, data, and creativity determines success, bid responses emerge as a pivotal component. For Google Publishers, understanding the nuances of bid responses is paramount in the quest to maximize revenue and optimize ad inventory effectively.