Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. The maintenance process does have locking in place, to ensure that only once instance is triggered at a time, but personally, whenever I was managing a setup like that, I would put the Revive Adserver code on the central DB server too (even though it would not serve ads from there), and then run maintenance on that machine, so that there's no need for network traffic off-server to run maintenance. Every millisecond counts, right? 🙂
  2. Hi @AngryWarrior, Instructions for manually upgrading your plugins, if they didn't get upgraded automatically, are here: https://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded
  3. Nope, I still don't have any means of reproducing this, unfortunately.
  4. Ah, okay. Strange. What version of Revive Adserver please?
  5. In the configuration file of your Revive Adserver installation.
  6. I guess that will depend on how your web server is configured re: how .htaccess files are detected and processed!
  7. Hi @Zak, In short, Hosted Edition only supports what the download edition supports - so I think the answer is "no" to all of your questions. https://www.revive-adserver.net/faq/
  8. https://documentation.revive-adserver.com/display/DOCS/Unable+to+Link+Banner+and+Zone
  9. Hi @scott001, Okay, thanks - have you enabled debug logging in Apache and traced the logs to confirm that the rules you are putting in are being triggered, and why they are not working as expected?
  10. Hi @proa, You mentioned "aqua ad server". Do you mean https://www.aquaplatform.com/ ?
  11. The only mention I can find of SVG files in HTML5 banners is https://github.com/revive-adserver/revive-adserver/issues/924 which was an issue fixed in 4.1.2, so this should work in 4.1.4 (although I would still strongly recommend upgrading, as there have been security issues fixed since 4.1.4). Do you have more details on what's happening or how to replicate?
  12. If you are changing the path, you'll also need to change the "[webpath] admin" value in the configuration file. Alternatively, rather than making changes to the code, you could address this by using rewrite rules as appropriate in your web server.
  13. 1. Yes. It's definitely possible to have multiple servers with the same Revive Adserver code on them, all using a central DB. 2. It's simply a case of backing up the installed code, and the database.
  14. When you say it now no longer seems to work, but used to, my question is always - what changed, if anything? Was there a system or upgrade change?
  15. Why not use the async tag, instead of trying to change the non-async one? 🙂
  16. If you're trying to use that option from the report site, is mod_headers installed in your Apache service?
  17. Presumably, this is a Contract campaign that you are talking about. (Screenshot may help here.) Please bear in mind that Revive Adserver does the following to calculate the banner/zone priority for Contract campaigns: How many impressions are left to meet the target? How long until the campaign ends? => Calculate the number of impressions needed for the next hour. How many impressions for the campaign to deliver next hour? How many banners? What relative weights do the banners have? => Calculate the number of impressions for each banner. How many impressions for a banner to deliver next hour? How many zone is the banner linked to? What are the relative forecast inventories of the zones? => Calculate the number of impressions for each banner/zone pair. And then calculate a % of the forecast inventory for the banner in that zone. This is why you may see a Contract campaign's banner with what looks like a low % in a zone, even if the Campaign is running behind on delivery - Revive Adserver is expecting to meet the campaign target via banner delivering occurring on other zones. Rather than looking at zones where the Contract campaign has a small % value, I'd be more interested in zones where there are multiple Contract campaigns all competing for the same inventory, and failing, because they can't all have the inventory. This is a more likely reason for the under-delivery.
  18. Okay, thanks for letting me know - but if you'd like further help, I will need more information from you than a throw away line. I can't disagree with this. In an ideal world, yes, Revive Adserver would be able to perfectly forecast your available inventory, and then perfectly understand how much of your available inventory will be made ineligible for use because of your delivery limitations, and therefore correctly calculate the required percentage of time each ad should be shown to perfectly smoothly deliver the ads over time to meet all campaign targets perfectly. Hopefully, though, you can see why this is never going to be possible to achieve. The over-delivery option exists for users who want to force Revive Adserver to deliver more impressions than the system thinks it will need, so that campaigns deliver above the forecast rate, so that campaigns are "ahead of the game" instead of playing catch up. If that's not a solution for you, fair enough - but that's the solution that we have at the moment. I think we answered that - you DO have rules in place, and this WILL affect Revive Adserver's ability to deliver in any given hour. Each hour, when priorities are calculated, it will recognise that the impressions/hour needed to meet the campaign target has increased, if the previous hour's delivery failed to meet targets (or if you over delivered for an hour, it will recognise that the impressions/hour needed to meet the campaign target has decreased), and so the next hour's priorities that are calculated will take this into account. However, that may not be enough, depending on the percent of impressions that are ineligible. If you want, you can adjust this with the over-delivery option. Not sure how much more I can say about this!
  19. Hi @malmazan, I'm really not sure what more I can say here. 1. When you turn on the over-delivery feature, at a high level (99%), you find that campaigns are over-delivering. 2. When you don't have the feature on at all AND you are using delivery limitations (e.g. country delivery rules), you find that campaigns are under-delivering. Maybe try setting the over-delivery rule to a less aggressive value, and see what level works best for your needs?
  20. Hi @manuel, Sure, ping me a direct message via the forums.
  21. Hi @malmazan, Okay, you seem to not be understanding a basic concept here in this case. Contract campaigns are designed to deliver the contracted number of impressions over the time they are set to run. If you ask for 100,000 impressions to be delivered over a month, and that campaign is linked to a zone that has 200,000 impressions available, then the campaign only needs to deliver 50% of the impressions to meet the target set. If you then ask the campaign to over deliver by 99% in the settings.... Well, that's why it's over-delivering! If you want to stop that over-delivery from happening, turn off the 99% over-delivery setting, and hopefully, the delivery of the campaigns will be about what you need to meet the contracted requirements. If you then have unused inventory that you don't want to "waste" on Remnant campaigns.... Well, the only solution to that is to either get more Contract campaigns to use up the available inventory, or, update the Contract campaigns for more impressions.
  22. Hi @jpm, Thanks, good question! I have added a new page to the Troubleshooting Guide that I hope answers this: https://documentation.revive-adserver.com/display/DOCS/Impressions+Inconsistently+Recorded
  23. I assume that you mean that you need to keep checking to ensure that a specific Contract campaign does not under-deliver? If you mean anything other than a Contract campaign, then please note that Remnant and Override campaigns are not designed to deliver a contracted number of impressions - only Contract campaigns do this. If you mean that your Contract campaigns are over-delivering (apart from not making any sense based on your first sentence), then you need to turn down the over-delivery setting, because that will not be helping! However, if the issue is that your Contract campaigns are under-delivering.... I think that this may actually be your problem - you are describing a zone that has very little traffic, but you have 6 different Contract campaigns linked to the zone, and they are all competing for traffic! As per Step 1 of https://documentation.revive-adserver.com/display/DOCS/Contract+Campaigns+Under-Delivering - do you actually have the inventory in your zones to meet the demands of your Contract campaigns? However, if we assume that you do have enough inventory, please take a look at Step 2 of the above guide, which links through to how the delivery engine works. If you have 6 Contract campaigns banners linked to a zone, with no Override campaign banners present, then Revive Adserver is guaranteed to select one of those banners only if it believes it is required to do so to meet the delivery requirements. It does this based on a forecast of expected impressions in the zone. If the zone traffic varies wildly, then sometimes, it may not make an accurate estimate of inventory for any given hour, and may display a Remnant banner, because it is expecting there to be many more impression occurring that actually happen. However, that forecast should then be updated in the next hour, and the situation should improve. Over a long enough time period, this should even out (roughly) to meet delivery needs. Have a look through that documentation and see if that helps explain the situation?
  • Create New...