dJAX

Depends on settings I think @dottedquad - there's an option to recalculate priorities of campaigns on changes, which I think it on by default... But it can be disabled, so if it's not appearing to work, check that setting.

Adding the click macro to the source URL of the iframe means that a click will be counted for every single impression. You should remove that.
The real answer to your question is that clicks inside iframes can not be counted.

Sorry to disappoint you, but since the ad server is completely unaware of what's going on inside the iframe, it is impossible to count clicks on this type of externally hosted banner.

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.

I don't think that cookie-based targeting has ever been possible the way you describe it. This is not a standard feature of Revive Adserver, and never has been.
 
One way to achieve this is by means of this third-party plugin named TargetiX:
http://www.adserverplugins.com/retargeting-plugin-for-revive-adserver/
 
Full disclosure: this plugin was developed by me and partner Matteo Beccati and licenses are sold through my company. The proceeds of this type of activity enable us to spend unpaid time on the open source project.

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 in v3.1.0 which has been fixed in v3.2.0.

You'll have to enter the width and height (mandatory).
 
I would also recommend that you set the click tracking to "do not alter".

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

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

Hi there,
 
Please start by having a look at this blog post: http://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/
 
Full disclosure, the paid plugin mentioned and linked in that blog post is a product of my company.

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.

You could have a look at this commercial plugin: http://www.adserverplugins.com/in-banner-video-ads-plugin-for-revive-adserver/
Full disclosure, this plugin is developed and sold by my company.

No extra HTML tags or code is added in the AdSense code. All Revive Adserver does is add (after the ad itself) an additional bit of code known as the listener (as described in my previous reply).
Don't worry, thousands of sites have been displaying their AdSense tags via Revive Adserver for more than a decode, and I have never heard of any problems coming from that.

Revive Adserver delivers the Google AdSense code unaltered. All it does is deliver an additional snippet of code to the browser, known as a 'listener' that attempts to recognize that a click has happened on that AdSense ad. Since the code is not altered, there is no reason even even wonder what Google's opinion on that might be.

I don't think this should work any different for the async invocation codes vs the traditional javascript codes. There must have been another reason why it started to work.

If you want to use "is equal to", you need to paste in the full URL, so even the http:// part.
I would recommend using 'contains' however, much easier, and also works on partial URL.

Can you post a screen shot of the delivery options of one of those banners?

You should not use the 'referring page' delivery limitation, that is for targeting the page the user came from before.
Instead, use "Site - Page URL"
Also, have you checked to make sure you're connecting them with an OR instead of an AND?

Please note that VidiX is a commercially available plugin, offered by a third party.

Not very patient, are you? :)
See: http://blackriver.to/2014/01/openx-source-revive-adserver-magic-macros/
Third party tracking pixels are typically put into the Append field on the Advanced tab. You need to turn it into a 1x1 pixel image, not just paste in the URL.

You're going to have to make the gif itself loop (start over after it displays the last frame). An ad server can not modify the behavior of the gif itself.
The setting you're referring to has nothing to do with this, it is there to prevent the same banner from showing twice in two different zones on a single page.

Could be many things, hard to diagnose based on this brief description. How long is "some time"? An hour, a day, a week? Either way, it would be atypical for a real visitor to keep a tab open for that long, so I wouldn't worry about it.
See also https://www.revive-adserver.com/faq/troubleshooting-banner-delivery/

@giantstep your issue is complete unrelated, see