Jump to content

Erik Geurts

Administrators
  • Posts

    752
  • Joined

Everything posted by Erik Geurts

  1. Your results will not be representative for others because the overall volume of impressions per day will also be different for others.
  2. The number is just too low to be statistically significant. It's less than 1 per hour, after all.
  3. The new async tags completely replace single page call, so both the code in the head (which is gone in its entirety) and the snippets in the body. I don't understand exactly what you mean by media query.
  4. We'll make a note of your idea. Would you be interested in being a sponsor for the development?
  5. Let's stop spending time on this, and spend it on something more valuable.
  6. 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.
  7. I'm glad you're not seeing much spam (and since recently, no spam at all I hope), that means we've done a good job. Believe me, that problem is bigger than you can imagine. We don't want to give away too much about how and what we're doing to achieve a clean space.
  8. Async tags typically only work when you access them over http(s), not if you open the HTML as a file.
  9. That article you found is about the macros you can use when you enter tags you've received from someone else into your own Revive Adserver. What you are trying to do, it seems, is the opposite, which is to give your own tags to someone else to enter into their ad server. I recommend not using the iframe invocation code but rather the async tags. That makes the tags much shorter and easier to manage, and also asynchronous. In the place of "INSERT_ENCODED_CLICKURL_HERE" the other party needs to enter the macro that their ad server uses to insert a click tracker.
  10. Duplicate of https://github.com/revive-adserver/revive-adserver/issues/754
  11. Exactly what I thought, good to hear that you managed to fix it!
  12. See: https://www.revive-adserver.com/support/requirements/
  13. Nothing is impossible, but I think it will take you as least as long as Google took to develop AdWords...
  14. This recommendation is incorrect. It should not be needed to set that "Even if GeoIP data unavailable checkbox" on, in fact, it is advised to never do that unless you know exactly what you're doing. I recommend double checking that path, and to make sure that the folder and the files in it are actually accessible.
  15. Hosting Revive Adserver takes some skill and experience. Jimmy's suggestion is one way of approaching it. Another might be to outsource the hosting to a specialist provider. Feel free to check out https://www.aquaplatform.com/revive-adserver-hosting/ (full disclosure: I'm co-founder and managing director of Aqua Platform).
  16. One should never delete statistics this way, since it will restart certain types of campaigns that have ended when they reached their target number of impressions or clicks. Moreover, the queries above will just kill all statistics, effectively wiping your database. DO NOT FOLLOW DAVE'S SUGGESTION!
  17. That will depend entirely on the specifics of the ad network in question.
  18. Most likely cause (from experience with many others) is that you've changed the folder and file permissions of your 'var' folder or any of its sub folders after the installation. Perhaps put a tail on the debug.log file and then see what lines get added at the very moment you see that message in your browser.
  19. The javascript tags for your zones that Revive Adserver generates for you generally don't need anything, they will work just fine as they are.
  20. Agreed, off topic. Ad networks are slowly dying (although perhaps not fast enough according to some) and are being replaced by exchanges using the concept of RTB.
  21. 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/
  22. That's a fairly typical fill rate for ad networks these days (apart from those that have no regard for ad quality). A much more important question is: what do they do with the unfilled spots? Did you get to send them a 'backup tag'?
  23. I still don't understand how people working in the field of advertising can even consider using an ad blocker.
  24. Looks like your upgrade failed. I suggest rolling back to the backup you have (you do have a backup, I assume), and then trying again. See https://www.revive-adserver.com/support/upgrading/
×
×
  • Create New...