Jump to content

Erik Geurts

Administrators
  • Posts

    752
  • Joined

Everything posted by Erik Geurts

  1. It says rather clearly on the homepage: About Revive Adserver Revive Adserver is a free, open source ad serving system that enables publishers, ad networks and advertisers to: Serve ads on websites, in apps, and in video players, and collect detailed statistics about impressions, clicks and conversions Manage campaigns for multiple advertisers and from ad networks all at once, via an easy to use interface Define rules for delivery of campaigns and ads, including frequency capping, URL targeting, geo-targeting Track and report campaign performance, including click-through rates, conversion rates, revenue, eCPM and conversion details, like basket value and number of items purchased
  2. The files present on Github are not packaged for installation, the files we publish on the Downloads page are.
  3. The ads you see on this forum are served via a Revive Adserver instance and are from Google AdX (the big brother of AdSense). Just to demonstrate that it does work...
  4. Google Page Speed Insights obviously has no clue about dynamic content like ad servers... No, you can not cache that file, it should be called anew every single time.
  5. The geotargeting plugin that ships with Revive Adserver by default will be installed automatically during install. You do not have to do anything manually.
  6. This is essentially the same as conversion tracking. However, please be aware that Revive Adserver does not support server-side conversion tracking.
  7. If you're website runs on a server with an outdated PHP version, and you include the Revive Adserver invocation code in that site, then it should work. Note: you will not integrate the Revive Adserver source code in the site, just some snippets of javascript code.
  8. If you're running an out of date version of PHP, it might be recommended to upgrade that too (for your own safety).
  9. Why would you install an outdated version if the newer one is available already? See https://www.revive-adserver.com/download/
  10. You should be able to upgrade from OpenX Source v2.8.11 straight to Revive Adserver v4.0.0.
  11. If you publish your WordPress plugin in their directory at https://wordpress.org/plugins/ we'll consider linking to it.
  12. The message is pretty clear, the MySQL username you're using doesn't have sufficient permissions to create new tables. I suggest given the user "all privileges" (as described in the installation documentation). By the way, why do you intend to upgrade to an already out of date version? I recommend using the newest v4.0.0, see https://www.revive-adserver.com/download/
  13. @soehlblaze You misspelled the product name of the software on your site. It's "Revive Adserver" (no extra space, no uppercase S).
  14. The password recovery process starts by entering an e-mail address. So that's where it was sent to...
  15. It is not possible to reduce that, the statistics will update once per hour, not faster.
  16. The data logged during ad delivery is stored in the tables with names ending in "bkt" (which is short for "bucket").
  17. See: https://www.revive-adserver.com/faq/geotargeting-with-revive-adserver/
  18. Exactly, that's how. Correct, since WordPress won't accept javascript code by default. You're going to have to search for a WordPress plugin to achieve this. Revive Adserver software won't even be aware that the code is going into a WordPress site, nor where.
  19. Both of your questions are more about WordPress than about Revive Adserver. Revive Adserver is the official successor of OpenX Source. See https://www.revive-adserver.com/blog/openx-announces-sale-of-openx-source/
  20. Perhaps look at a different solution for that device and screen size detection. I've heard people mentioning mobiledetect.net.
  21. My recommendation would be to stop using that custom lazy loading you developed and instead start using the built-in asynchronous tags that have been part of Revive Adserver for more than 1.5 years. Those async tags already automatically bundle all ad zones into a single ad server call.
  22. Is your error_log completely empty? Or just not logging anything about this particular situation?
  23. As I said, the first and best place to look for information is the Apache error log (or the equivalent if you're using some other sort of web server software).
  24. Hacking the code to work around an issue might sound like a nice fix, but it is at best fixing the symptoms, not the actual cause. I wouldn't be surprised if other functionality is now broken as well. I would recommend looking for the actual cause and fixing that.
  25. Looks like either something went rather wrong during the upgrade process, or your server isn't entirely compatible.
×
×
  • Create New...