andrewatfornax

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. 

This is not possible when using the javascript invocation code. You could perhaps build something within your own site that repeatedly calls them.

You actually posted the problem already ! It's on the right of "Reason:"
Anyway, I would contact your system administrator, it isn't (CORS header) suddenly enabled out of the blue.
(The ads work for me fine though)

We solved it... this is how :)
 

Your results will not be representative for others  because the overall volume of impressions per day will also be different for others. 

Thanks Erik, makes sense. I have had successfully run a campaign with daily limit 70. So I will try with daily limit 24 and higher numbers and will post at which limit it starts working.

The number is just too low to be statistically significant. It's less than 1 per hour, after all. 

Hi folks,
Sorry to re-open a resolved thread, but I'm having the same difficulty. I've downloaded the latest GeoLiteCity.dat file from here: http://dev.maxmind.com/geoip/legacy/geolite/?rId=revive, I've uploaded it to the same location as the "GeoIP.dat" file ([document root]/plugins/geoTargeting/oxMaxMindGeoIP/data/) and referenced it in the "Path to geoipCityLocation file" section of the plugin settings with the full path, and I've made sure that the permissions are the same on both files (owned by the webserver user) but I'm still not seeing a "Geo - City" option in my delivery options. I've even tried renaming the file to GeoIPCity.dat as suggested here (http://dev.maxmind.com/geoip/legacy/install/city/). It *seems* that Revive is seeing the new file because the "Geo - Lat/Long" option appears when I have that file specified in the settings whereas I don't get the option when it's not there. Any thoughts as to what I might check next?
Thanks!
Reid

@Reid We had a very similar case yesterday. It was the same file, downloaded from that same location you mentioned on Tuesday of this week. We downloaded it again today (and it had changed since Tuesday, surprisingly). Once uploaded on the server, geotargeting started working again.
My two cents: somehow the file you found earlier on maxmind.com was wrong, and it was corrected after they found out.

Hi @scott001,
I have doubts that it's a fork bomb - I don't think there's any code in Revive Adserver that creates any additional threads - everything is single threaded (although you can of course have as many single-threaded pathways executing as you set up your web server to allow).
It's more likely a mis-identified report by Suhosin as a result of a high number of calls to the logging scripts - either simply legitimately (as a result of a normal traffic spike or a legitimate scripted bulk access), or, possibly a DoS attack.

I think I have this sorted.. I used the refreshed the invocation code each time....

Thanks. We finally upgraded this week. No evident change yet, but I'm not sure how long it would take for these campaigns to correct themselves, so we're keeping an eye on it for now.

Hi @sikjoy,
It appears to be an account preference, under Preferences > Account Preferences > Campaign Preferences.

Sorry, there isn't... :(

just in case anyone needs this in the future - this doesn't seem to be a common problem around here based on the sheer amount of responses:
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookieJar); curl_setopt($ch, CURLOPT_COOKIEJAR, $cookieJar); curl_setopt($ch, CURLOPT_REFERER, APP_URL.'/fancy_changing_fake_url_here/page/'); i managed to successfully get banners when i pass curl a cookiejar for the entire session and an always changing referrer

Thanks to @Erik Geurts who pointed me to this thread and this issue as well, I've been able to verify and fix the bug. The fix will apper in the next Revive Adserver release. Thanks for your report.

I found out what the problem was...IE 11 (eeeech) determined that all sites were "Local intranet" for some bizarre reason. By default, intranet sites in IE 11 are set to run in compatibility mode ... which I guess is such old tech that it doesn't work with Revive's Asynchronous Tag. My fix was to add the following to the head of our site:
<meta http-equiv="X-UA-Compatible" content="IE=edge">
Problem now solved.

This is not a browser issue. Looks like your server is doing an incorrect redirect, because there is no such thing as admin.php.

The way Revive Adserver tracks clicks is by inserting a click counter with redirect. The setting you refer to is unable to automatically recognize tags from Google Tag Manager.
You should contact your third party and ask them to provide a tag that is capable of third-party click tracking.
Once you have an updated tag, you can use the Revive Adserver macro {clickurl} to insert a click tracker into that tag.

Contrary to the previous comment, this is definitely possible. One can add any key=value parameter to a zone's invocation code and then use that for targeting on the banner(s).

Well it seemed to work properly... I have a cron job that starts it. I've also tried with the option "Automatically perform maintenance during delivery if scheduled maintenance is not set up"
Lets see how it is going to work after the reinstall. I will wait a few days and will monitor it. Then I will write back to share the results.

The items to concentrate on are the contract campaigns. Remnant campaigns don't "take" probabability, the "get" whatever is left after the share for your contract campaigns has been taken. So if there's a problem with the contract campaigns, they get no volume and the remaining impressions (hence the word remnant) go to the Remnant campaigns.
You seem to have a contract campaign with 2000 impressions in a period of more than 1 month. It started only today. That comes down to less than 3 impressions per hour on average. It is not unlikely this results in 0% probability on the first day, but this should automatically correct over the course of your contract campaign. In short: be patient!

There is no table "stats_country" in the stock Revive Adserver system. You'll have to talk to the vendor of third-party where you purchased the plugin that created this table.

That depends, if I recall correctly from 3.2.2 are no database changes made. Anything under I recommend restoring a backup, and doing the upgrade via the 'official' procedure :)

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.