Erik Geurts

Please have a look at http://www.reviveconsultant.com/articles/how-to-move-the-banner-image-storage-location-in-revive-adserver/ which is what we've assumed you've done before performing an upgrade as described here http://www.revive-adserver.com/support/upgrading/

In my opinion, it is a very bad idea to enable advertisers to add or change banners. It will almost certainly result in unapproved or unwanted advertising on your site(s) if you do not moderate what they add.

We've noticed the same thing in some cases. The May 2015 update of the city data file made by MaxMind appears to be defective. We reverted to the April 2015 data file and all was fine again.
 
We tried contacting MaxMind about it, but they claim the data file is OK (even though there is strong evidence it is not). Hopefully the June update will fix things again.

The software had been designed to update the statistics once per hour. This can not be changed.

In the dimensions of a zone, you can enter the width or the height (or both) as a * instead of a fixed number. This means the size becomes a wild card.
 
Let's suppose you make a zone of 300 pixels wide and * pixels high. You can then link banners from campaigns, with sizes like 300x250 but also 300x600.

This is a known issue:
https://github.com/revive-adserver/revive-adserver/issues/544

I'd suggest to start browsing http://www.revive-adserver.com/security/

The software had been designed to update the statistics once per hour. This can not be changed.

This is a known issue https://github.com/revive-adserver/revive-adserver/issues/549 which will be fixed in the upcoming release v3.2.1.

This is a known issue in v3.1.0 which has been fixed in v3.2.0.

I use Version 3.1.0
When i create overlay ad, I can't find the box to fill the link when click banner.
Help me

In the dimensions of a zone, you can enter the width or the height (or both) as a * instead of a fixed number. This means the size becomes a wild card.
 
Let's suppose you make a zone of 300 pixels wide and * pixels high. You can then link banners from campaigns, with sizes like 300x250 but also 300x600.

The async tag does not support auto refresh (nor should it).

Upgrade instructions appear to be here: http://www.revive-adserver.com/support/upgrading/

See http://forum.revive-adserver.com/topic/1415-problem-serving-iframe-ads-of-juicyads/

I agree with firstimpression, the number of impressions per day is irrelevant if we don't know what kind of resources your vps has. On our hosting platform, we can easily serve a million impressions per 10 minutes, but that involves a lot more hardware than just a tiny VPS.

This is open source software, you can make any changes you like.

The basic instructions given by AdSense are indeed to just take the code the generate for you and put it directly into the source code of your website.
 
However, an ad server such as Revive Adserver can also be used to do that. The steps you described are exactly right.
 
The ad server will "deliver" the AdSense tag to the browser. The browser will then execute the AdSense code and while doing so, it will be able to determine the domain of your actual site and then also crawl the page to determine what the content is. AdSense will then attempt to find a suitable and relevant advertisement and display it on your site.
 
Think of Revive Adserver as the vehicle transporting the AdSense code to your site and into the visitor's browser.
 
If it can be avoided, don't use the iframe invocation code for the zone, but rather use the javascript invocation code.

Single Page Call (which is what we normally call it) can do this.
 
You might enjoy reading this set of articles: http://www.reviveconsultant.com/articles/single-page-call-in-revive-adserver/
 
Your topic is addressed in the third one.

One way to achieve this would be the use of the TargetiX Retargeting plugin for Revive Adserver. More information can be found here:
http://www.adserverplugins.com/retargeting-plugin-for-revive-adserver/
 
Full disclosure: this plugin was developed by my company in close collaboration with fellow Revive Adserver team member Matteo Beccati. We've built in in 2009 on request of a customer and have been selling it as licensed software since that year.

Your existing code will continue to work before, during and after the upgrade to v3.2.0. After the upgrade, it's your choice if you want to switch to asynchronous tags immediately or perhaps gradually. We'll be adding more information and documentation about this in the coming days and weeks.

Revive Adserver v3.2.0 (a beta was released recently) has a new feature: asynchronous javascript tags. See also:
http://www.revive-adserver.com/blog/beta-version-of-revive-adserver-v3-2-0-released/
 
Do note, though, that expanding ads will never be possible, in case of iframes (even friendly iframes).

Community member Ilya Behr at Black River in Toronto, Canada, wrote two extremely detailed online guides related to Conversion tracking using Revive Adserver.
 
The Conversion Tracking tutorial explains how to enable the feature, how to setup and implement a tracker, and how to analyze and interpret the statistics recorded by these trackers.
 
Next, the Debugging Conversion Trackers guide provides detailed instructions on how to check and validate the conversion tracking has been implemented correctly and reliably.
 
Thank you, Ilya, well done!

Hi Richard,
 
We've been considering this, but we do not think a sub-forum is a good place for that. In the future, there will be a separate section on http://www.revive-adserver.com/ with vendors and reviews.

A campaign that's created inside one account is completely invisible from any other account. Likewise, a site and zone created in one account is not accessible from any other account.
 
The reason is that each account is a completely separate entity, what happens on one account is locked inside that account.