Jump to content

Erik Geurts

  • Posts

  • Joined

  • Last visited

About Erik Geurts

Contact Methods

  • Website URL

Recent Profile Visitors

4,561 profile views

Erik Geurts's Achievements

  1. With those kinds of volumes, running maintenance once per hour should be more than sufficient. There are almost never any good reasons to run it more often.
  2. See https://www.revive-adserver.com/mailinglist/ and we post every release on Twitter as well.
  3. That is not the correct process for upgrading. You should not just upload the new files overwriting the existing files. The upgrade process is described in full detail here: https://www.revive-adserver.com/support/upgrading/
  4. You're referring to the generic documentation for the Download edition. The Hosted edition uses a specific delivery URL that's clearly mentioned in the FAQ. The reason the FAQ does not specifically refer to video ads is because we assume that video ads won't be used very frequently on the Hosted edition.
  5. This is a user of the Hosted edition. It turns out the dimensions of the banners in the campaigns did not match the dimensions of the zone(s).
  6. Thanks for letting us know, Roy. The link has just been fixed.
  7. As explained in the FAQ, the delivery URL does not include the /www/delivery part, it's straight to fc.php
  8. See https://www.revive-adserver.net/faq/ and then the very last question "What is the ad delivery URL of Hosted edition?" on that page.
  9. For 70 million ad request for month, you would need to select the Ultimate plan, that would cost you $150 per month. However, you would be paying an overage use cost each month, since 70 million is significantly higher than 15 million. You can have as many publishers (websites) as you want. See https://www.revive-adserver.net/pricing/ for pricing details and direct signup. If you'd need something a bit more dedicated, we can recommend Aqua Platform's Revive Adserver hosting, see www.aquaplatform.com.
  10. Well, on the contrary... Revive Adserver processes and stores hardly any personal data. Either way, Revive Adserver is just a piece of software. The publisher using it is ultimately responsible for how they use it. They are the 'data controller' and most likely also the 'data processor'. Nothing new here, same for any other software being used by the same publisher. GDPR is not a technical issue, it's primarily a legal issue. Also, GDPR has been in effect since May 25, 2016. Everyone should have been compliant for a long time already. The only thing new is that enforcement will start on May 25, 2018.
  11. It may be that you ran into an issue that was found in the upgrade process in v4.1.0 and that was fixed in v4.1.1. Please try if using the most recent version fixes this for you. See https://www.revive-adserver.com/download/ and https://www.revive-adserver.com/blog/revive-adserver-v4-1-1-released-bug-fixes/
  12. The API built into Revive Adserver has nothing to do with the actual ad delivery, it's just for the management of your inventory and for reviewing statistics.
  13. See http://dev.maxmind.com/geoip/legacy/geolite/
  14. Technical requirements for Revive Adserver v4.0.x are listed here: https://www.revive-adserver.com/support/requirements/ As you can see, PHP 7.1.x is not yet officially supported. I've opened an issue on Github for the developers to look into this, see https://github.com/revive-adserver/revive-adserver/issues/837
  15. That table is used for tracking conversions (i.e. when someone sees or clicks an ad, and subsequently purchases something). However, it is a remnant of a very old version, it is no longer being used.
  • Create New...