Jump to content

Erik Geurts

  • Content Count

  • Joined

  • Last visited

About Erik Geurts

  • Rank

Contact Methods

  • Website URL

Recent Profile Visitors

2,825 profile views
  1. As explained in the FAQ, the delivery URL does not include the /www/delivery part, it's straight to fc.php
  2. 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.
  3. 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.
  4. 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.
  5. 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/
  6. 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.
  7. See http://dev.maxmind.com/geoip/legacy/geolite/
  8. 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
  9. 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.
  10. Instead of beer, perhaps consider: https://www.patreon.com/revive_adserver
  11. It should be possible to change it there in the UI, but only while working as the specific account, not as administrator.
  12. The dashboard is the only place that uses it, so it won't affect anything else.
  13. Revive Adserver does not contain any functionality to detect and/or report viewability.
  14. Revive Adserver does not contain any functionality to detect and/or report NHT.
  15. That "dashboard" page isn't extremely useful, and not at all critical to the working of the ad server. I would recommend just disabling it altogether and you won't see that message anymore. To disable it: log in as an administrator, and switch to "working as administrator" go to the Configuration tab, and then "User interface settings" menu item on the left at the very end of that page, uncheck the "Enable dashboard" checkbox don't forget to save the changes Problem solved.
  • Create New...