Erik Geurts

My first bet would be that you enabled zone chaining on zone 5.

Perhaps this article over on my site gives you a clue about how to make a link on a banner still have something zone specific: http://www.reviveconsultant.com/articles/how-to-dynamically-insert-an-affiliate-id-into-a-banner/

In case of a 500 Internal Server Error, there should be more detailed information in your Apache error log. Your hosting provider or system administrator should be able to look up this information and fix the cause.

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.

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.

Out of the box, Revive Adserver v3.x only supports the VAST1 specifications, and it does not have support for creating pre-roll ads that are essentially using VAST2 tags from third parties. I would like to suggest having a look at the Advanced Video Ads plugin that you can find here: http://www.adserverplugins.com/advanced-video-ads-plugin-for-revive-adserver/ This plugin will enable you to traffic a third party VAST2 tag (we call this a Network Video Ad) as a banner, and then to serve that into any VAST2 compliant video player. Full disclosure: this product has been developed and is being sold by my company.

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.

I haven't received anything. I will check the spam folder, if I find your message I will reply.

I would like to suggest having a look at the Advanced Video Ads plugin that you can find here: http://www.adserverplugins.com/advanced-video-ads-plugin-for-revive-adserver/ This plugin will enable you to traffic a third party VAST2 tag (we call this a Network Video Ad) as a banner, and then to serve that into any VAST2 compliant video player. Full disclosure: this product has been developed and is being sold by my company.

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.

AdSense is not intended for use as in-app advertising. It won't work, not via Revive Adserver, and not directly either.

I've moved this topic from "Using Revive Adserver" to "Plugins" because I feel it's a better place for this discussion.

That article you linked to is related to DFP. not Revive Adserver.

OpenX Source became an open source project and was renamed to Revive Adserver in September of 2013. You can read about it here: http://www.revive-adserver.com/blog/openx-announces-sale-of-openx-source/ You can read more about Revive Adserver's functionality on our documentation pages at http://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Documentation

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).

Please see http://www.openxconsultant.com/blog/2011/10/what-to-do-when-you-suspect-your-openx-system-has-been-hacked/

April 10 2015 update A bug was reported by community member Pedro-Miguel. Many thanks for the detailed report! The bug report prompted us to re-package the downloadable files on Friday, April 10, around 10 AM UTC. This affects only those users who have upgraded from a previous version to v3.2.0-beta using the files downloaded prior to this fix. If you’ve downloaded the beta release before that time, please see the Github issue and comments for instructions on how to fix the issue.

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.

You wrote: However, in reality you'll have to make one for each city and string them together with an OR. I'd recommend using a targeting channel to make that easier to manage.

I have never heard of an "Elgg" plugin before. It is not something that ships with Revive Adserver or has ever shipped with it. Can you provide more detail please?

So you're saying you got hacked because of an old/known issue? Then way do you claim that your 3.1 installation was 'hacked'? What would be the point of notifying Google?

Yes, a full upgrade process would be required to get a properly working v3.0.6.

No, a delivery limitation is a feature to help you determine the conditions for delivering a banner through a zone. It works on the banners, not on the zones. Think of zones as the vehicles that transport the banners. These "targeting groups" you mention are not a feature we have. Do you perhaps mean "Targeting channels"? A Targeting channel is a kind of pre-made and saved set of delivery limitations you can easily apply to a banner so you don't have to define it each time. Plus, if you use a targeting channel on multiple banners, making a change to the delivery limitations of the channel automatically applies to all those banners.

Very kind of you, thanks for letting us know you like the product. And I think you'll like the next release we're brewing even more...

Why don't you just contact me as you were doing in previous days, instead of posting this here?