Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


If you are using Single Page Call Tags, review your use of the tags.  By default, Revive Adserver will load a banner for every zone in the website, even if you're then only displaying some of the zones on the page. This can lead to a high number of requests vs. impressions.

To limit the zones that an SPC Tag will select a banner for, simply add the following code to your page above the SPC Tag:

Code Block
<script type='text/javascript'><!--// <![CDATA[
    var OA_zones = {
      'zone1' : 1,
      'zone4' : 4
// ]]> --></script>

In the above case, this will limit the SPC tag to simply loading the zones with the name/ID pairs shown.

Step 2: Review Load Performance

Probably the most common reason for a significant difference in requests vs. impressions, however, is banner loading performance. Any banner that takes a long time to load, relative to the rest of the page, is likely to significantly increase the "drop off" rate - that is, the rate of users who visit a website, which results in banner requests being logged, but who then "navigate away" to another page (on the site, or elsewhere) before some (or all) of the banners have actually loaded.

In particular, you should consider looking for:

  • Large banner creatives, such as very large image files, Flash banners or complex HTML5 banners; and
  • Banners which are served from 3rd party networks (possibly from a series of chained 3rd party networks), which are slow to load (relative to the rest of the page).

Using a tool such as YSlow, Firebug or one of the many others that provide an analysis of the total page load time can often help you to see and understand the difference in performance between the time required for the web page to load vs. the time required for all the banners to load.

Note: This issue can be particularly exacerbated by the SPC and the Asyncrhonous Tags   

Step 3: Review Server Performance

If you're not selecting banners via an SPC Tag for zones that you never display, and the load performance of your banner creatives is reasonable relative to the load performance of your page, you will need to review the performance of your Revive Adserver server performance.

Poor performance on the Revive Adserver server (in general terms - not having enough memory, CPU or disk I/O performance to meet the load demands of the server under load) can result in poor banner creative load time and/or lost data, as the server fails to respond to e.g. impression beacon requests, and users' web browsers time out. This can also lead to "missing" impressions when compared with the request levels.