Erik Geurts

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 
 

Can you clarify what you mean by 'rotating banners'?

Can you please explain what the problem is you are trying to solve? 

It is not an error message. It simply tells you that zones being used for pre-roll video do not use the ordinary invocation code.
Just follow the link in the note to http://documentation.revive-adserver.com/display/DOCS/Invocation+code%3A+Zone+level#InvocationCode:ZoneLevel-Video where you will find more information about what to do.
Also please have a look at https://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/

Revive Adserver is what it says, an ad server. You'll have to provide the video player yourself.

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.

Please do not double post the same question.

Was wondering if the new release version plans to support AMP in Revive Adserver?

That is actually the solution that the OP has tried and which doesn't help. So it must be something else...

The Magic of the Macros

That is not possible. You can assign a weight to a remnant campaign, the system will calculate the probability of delivery by putting that weight into the perspective of the total weight of all active banners on each zone. See http://documentation.revive-adserver.com/display/DOCS/Creating+a+Campaign

I guess it is related to permission access.

The respective folder should have 777 permissions.
 

I would recommend to put the MaxMind files in their own folder somewhere on the server outside of the Revive Adserver folders. That way when you perform an upgrade in the future, these MaxMind files will not be affected and geotargeting will continue to work. 
See http://www.reviveconsultant.com/articles/choosing-a-smart-location-for-a-revive-adserver-installation/

I guess you're talking about the 'dashboard'? Those 3 widgets are the only ones available. No need looking anywhere else.

I would recommend to put the MaxMind files in their own folder somewhere on the server outside of the Revive Adserver folders. That way when you perform an upgrade in the future, these MaxMind files will not be affected and geotargeting will continue to work. 
See http://www.reviveconsultant.com/articles/choosing-a-smart-location-for-a-revive-adserver-installation/

You need to set the full path of the file(s), so the location and the filename(s), not just the folder.

There is some ongoing work for the next release of Revive Adserver with regard to various forms of device and OS targeting. You will not need a third party plugin for that, it will be built right into the core application.

I recommend switching to the asynchronous tag type we introduced in the spring of 2015.
See https://www.revive-adserver.com/blog/revive-adserver-v3-2-0-released/

The new asynchronous tags in Revive Adserver have been designed so that when you put 2 or more of them on a single page, they will execute a single bundled request to the ad server. That means you have the advantage of single page call without the disadvantage of a potentially blocking javascript in the head of the page.
So in short, async tags already do what you proposed.