In-Page notifications are a specific type of display ad that shares many similarities with Push Notifications. However, there are some key differences that set them apart from traditional Push Notifications.

In-Page notification ads are displayed directly on the publisher's site, much like a banner ad. This means that they are fully integrated into the existing content of the site and do not interrupt the user's experience by asking for subscription permission.

Additionally, this format is designed to be fully responsive across all devices, including desktops, tablets, and mobile devices. This ensures that the ad remains visible and functional regardless of the device being used to access the site.

Overall, In-Page notifications provide a powerful yet unobtrusive way to reach potential customers with targeted messages and promotions.

How to configure in-page notifications

Notifications are configured in the same way as other ad formats, e.g. banners.

  1. Create a zone with the format "In-page notification"
  2. Install the ad code to your website. Note the code can be reconfigured for your needs (see below).
  3. Create ads in Notifications / In-Page format

Available options for in-page notifications code

skin

Our ad server supports several skins:

  • 1 – classic. Demo
  • 2 – rounded blue. Demo

Example:

_ASO.InpOptions = {
    idzone: XXXXX,
    skin: 2
};

delay

Sets delay for first notification. The default value is 0.5 sec.

Example:

_ASO.InpOptions = {
    idzone: XXXXX,
    delay: 0
};

maxPerPage

Sets a maximum number of In-Page Push Notifications you want to display on a page. The default value is 2.

Example:

_ASO.InpOptions = {
    idzone: XXXXX,
    maxPerPage: 3
};

loadTimeout

Timeout before loading the next notification. The default value is 2 sec.

Example:

_ASO.InpOptions = {
    idzone: XXXXX,
    loadTimeout: 2
};

cappingLimit

Using this option, you can define the maximum number of messages displayed to visitors within the capping interval (see below). Note this is client-based capping.

The default value is 2.

In the example below, the messages will be displayed as often as 3 times per 30 seconds:

_ASO.InpOptions = {     
    idzone: XXXXX,     
    cappingLimit: 3,
    cappingInterval: 30 
};

cappingInterval (in seconds)

Using this option, you can define the time interval of client-based capping.

The default value is 20 sec.

In the example below, the messages will be displayed as often as 2 times per hour:

_ASO.InpOptions = {     
    idzone: XXXXX,
    cappingInterval: 3600 
};

How to configure in-page notifications – complete code examples

<script>
(function(w,a){
  w[a] = w[a] || {};
  w[a].queue = w[a].queue || [];
  w[a].queue.push(function(){
    _ASO.InpOptions = {
        idzone: XXXXX,
        cappingLimit: 5,
        skin: 2,
        maxPerPage: 3
    }
    _ASO.loadInpHelper();
  })
})(window, "_aso");
</script>
<script data-cfasync="false" async="async" type="text/javascript" src="https://media.aso1.net/js/code.min.js"></script>

Compact tag

This type of tag is for easier placing in-page tags on websites. It contains one short line only.

Technically, it simply puts the standard tag described above into a single-file container.

The disadvantage of the compact tag is that it cannot be configured as flexibly as the standard tag. It supports a few options only via special parameters that are aliases for the standard tag parameters described above:

  • ci – cappingInterval
  • cl – cappingLimit
  • s – skin

Compact tag example:

<script data-cfasync="false" async src="https://media.aso1.net/js/inp/c.js#zid=100800&ci=30&cl=3&s=2"></script>

Conclusion

We hope this article will help you to configure in-page notifications easily and, more importantly, according to your needs.