I set a daily impression limit on an ad, but it received more impressions than the limit is set for
To understand why ads with daily impression limits exceed the actual limit set for them, consider the following:
Stats are run once an hour
Every five minutes an estimate of the ads stats is calculated based on prior stats history. This estimate is then used in determining whether an ad has hit its cap limit or not
The estimate is typically over the cap limit due to the delay in processing.
Ads with a monthly impression limit don't appear, even though the impression limit hasn't been reached
When an ad is set with a monthly impression limit, Banner Ads will attempt to spread the value of the impressions throughout the calendar month of the ad start date. As an example, if an ad is set with an impression limit of 100,000 per month, Banner Ads will estimate the delivery of impressions over the remainder of the current calendar month and sets a virtual impression limit of 3,330 per day (assuming the ad start date was the 1st day of the month). If that ad started on the 15th of the month, the 100,000 per month impressions would be spread over the remaining 15 days in the month (if the month has 30 days) for a virtual limit of 6,660 per day.
If the ad reaches the virtual, daily impression limit, Banner Ads will stop serving the ad until the next day.
Banner Ads re-calculates the estimate every day to handle sporadic site traffic, thus the virtual limit can change without notice.
The monthly impression limit is calculated on the calendar month, not a 30 day period. So some months such as February or March will spread the monthly impressions over 28 or 31 days, rather than 30.
Cache-busting (random number generator and timestamp) in BLOX Banner Ads
If your agency supplied ad requires a cache-buster in the ad tag, please replace all occurrences of [CACHEBUSTER] or other cache busting code in the ad tags with:
Support for random number generation inside HTML ads should be able to replace 'timestamp' or similar placeholders with a special syntax:
[% ad.timestamp %]
This will, replace this parameter with javascript that generates a current unix timestamp on page refresh.
Support for truly random can be provided by using:
[% ad.random %]
This should be replaced with javascript that generates a new random number each refresh.
Why is code getting stripped out of my HTML ads?
BLOX Banner Ads strips out any HTML comments and the code between them. In the following example everything between the <!-- and --> will get stripped out when the ad is rendered
<script language='JavaScript' type='text/javascript' src='http://example.com/phpadsnew/adx.js'></script> <script language='JavaScript' type='text/javascript'> <!--if (!document.phpAds_used) document.phpAds_used = ','; phpAds_random = new String (Math.random()); phpAds_random = phpAds_random.substring(2,11); document.write ("<" + "script language='JavaScript' type='text/javascript' src='"); document.write ("http://example.com/phpadsnew/adjs.php?n=" + phpAds_random); document.write ("&clientid=4"); document.write ("&exclude=" + document.phpAds_used); if (document.referrer) document.write ("&referer=" + escape(document.referrer)); document.write ("'><" + "/script>");--> </script> <p> <noscript> <a href='http://example.com/phpadsnew/adclick.php?n=af4d3606' target='_blank'><img src='http://example.com/phpadsnew/adview.php?clientid=4&n=af4d3606' border='0' alt=''></a> </noscript>
Previously, individuals would insert HTML comments so that in really old browsers it didn't write out the JavaScript onto the page. Since our Banner Ad system writes out the ads with JavaScript anyway, it doesn't make sense to insert the comments, and it can cause your ad not to render. No Script tags will also be ignored.