Jump to content

Revive Adserver Forum

Administrators
  • Content Count

    18
  • Joined

  • Last visited

Everything posted by Revive Adserver Forum

  1. The Revive Adserver team announces the immediate availability of Revive Adserver v4.2.1. We are pleased to announce a new release of the Revive Adserver software, which has been given version number v4.2.1. This new version fixes a number of bugs that were discovered since the last 4.2.0 release, and it also addresses one security issue that has been discovered recently. Here are the most important changes included in Revive Adserver v4.2.1: We fixed an issue with the “Active Campaigns” filter, which was incorrectly hiding campaigns if it contained at least one inactive banner, and depending on the order of active or inactive banners found for the campaign. We fixed an issue with some of the required PHP extensions for Revive Adserver not being displayed in the pre-install/upgrade check screen. Security fix This version 4.2.1 also contains a fix for one vulnerability that was recently discovered and reported to us through our HackerOne security program. We strongly advise people to upgrade to the most recent 4.2.1 version of Revive Adserver as soon as possible. In case that is not immediately feasible, we especially recommend to delete or block the www/admin/password-recovery.php script. Release notes Full release notes for Revive Adserver v4.2.0 can be found on our Github page. Download, install and upgrade Revive Adserver v4.2.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Version 4.2.1 has been sponsored by several community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. A special thanks for their contribution to this version goes to Aqua Platform, specialists in Revive Adserver hosting, for helping test the changes to the password recovery process. Another way to contribute to our project, is by using the Revive Adserver Hosted edition. The post Revive Adserver v4.2.1 released – bug & security fixes appeared first on Revive Adserver. View the full article
  2. The Revive Adserver team announces the immediate availability of Revive Adserver v4.2. We are pleased to announce the next major release of the Revive Adserver software, which has been given version number v4.2. This new version contains several enhancements and improvements, and it also addresses two security issues that have been discovered recently. Here are the most important changes included in Revive Adserver v4.2: We’ve updated the definition of “active” Advertisers and Campaigns, to also include Advertisers and Campaigns which will become active in the future (i.e. in the “Awaiting” state), to help with their management. The Zone Probability screen now includes a link to the parent campaign for each banner. We replaced the old “weight” measure on the Zone Probability screen with the actual Campaign and Banner weights, to improve clarity around probabilities of banner display in a zone. IP anonymisation is now enabled, and OAID cookie are now disabled by default on new installations, as per our plans published in the first half of 2018 around the introduction of the GDPR. For developers: we added support for hourly statistics to the XML-RPC API. This change was contributed by the makers of the Revive Adserver REST API. We have also fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes. Important: Revive Adserver v4.2 has a Non-Backwards Compatible Change. Support for PHP 5 has been dropped and Revive Adserver now requires at least PHP 7.0.8. Security fixes This version 4.2.0 also contains fixes for two vulnerabilities that were recently discovered and reported to us through our HackerOne security program. We strongly advise people to upgrade to the most recent 4.2.0 version of Revive Adserver as soon as possible. In case that is not immediately feasible, we especially recommend to delete the adxmlrpc.php, www/delivery/axmlrpc.php and www/delivery/dxmlrpc.php files. Release notes Full release notes for Revive Adserver v4.2.0 can be found on our Github page. Download, install and upgrade Revive Adserver v4.2 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Several new developments in version 4.2 have been sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. Another way to contribute to our project, is by using the Revive Adserver Hosted edition. The post Revive Adserver v4.2 released – bug & security fixes appeared first on Revive Adserver. View the full article
  3. The Revive Adserver team is immensely proud to announce the immediate availability of the Release Candidate of Revive Adserver v4.2. We are pleased to announce the next major release of the Revive Adserver software, which has been given version number v4.2. Since this new version includes a large number of changes and enhancements, including some breaking changes, we think it is appropriate to first publish it as a Release Candidate. This will enable users, administrators, plugin developers, hosting providers and consultants to put the new version to the test in all sorts of scenarios and environments. If everything goes according to plan, we expect to release the final v4.2 in 2 weeks from today, on April 23, 2019. Here are the most important changes included in this Release Candidate for Revive Adserver v4.2: We’ve updated the definition of “active” Advertisers and Campaigns, to also include Advertisers and Campaigns which will become active in the future (i.e. in the “Awaiting” state), to help with their management. The Zone Probability screen now includes a link to the parent campaign for each banner. We replaced the old “weight” measure on the Zone Probability screen with the actual Campaign and Banner weights, to improve clarity around probabilities of banner display in a zone. IP anonymisation is now enabled, and OAID cookie are now disabled by default on new installations, as per our plans published in the first half of 2018 around the introduction of the GDPR. For developers: we added support for hourly statistics to the XML-RPC API. This change was contributed by the makers of the Revive Adserver REST API. We have also fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes. Important: this release candidate and the actual v4.2 release later, will have a Non-Backwards Compatible Change. Support for PHP 5 has been dropped and Revive Adserver now requires at least PHP 7.0.8. Full release notes for v4.2.0-rc1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.2 Release Candidate is available for download now. Please keep in mind that this is a release candidate, and as such it can result in issues. If you don’t feel confident about testing beta-level software, we recommend that you wait until the final v4.2 is available. This will be announced here on the blog, on our Twitter account, and to the subscribers to our mailing list. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Several new developments in version 4.2 have been sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. Another way to contribute to our project, is by using the Revive Adserver Hosted edition. The post Release Candidate 1 for Revive Adserver v4.2 appeared first on Revive Adserver. View the full article
  4. Exactly 3 months ago, on December 7, 2018, the first subscriber opened an account on the Revive Adserver Hosted edition. We had been collecting a waiting list of eager users since the announcement of the Hosted edition back in September 2018, and immediately after soft-launching it to the waiting list, people started joining. Later in December, we officially launched the Hosted edition for everyone. Since then, we’ve been adding new subscribers every day. We are very happy and proud that so many people and companies have decided to give the Hosted edition a try. A blog post on the Revive Adserver Hosted edition website details the uptake in the first 3 months, and also lists what we’re developing for the future of the Hosted edition. We invite you to have a look at the Revive Adserver Hosted edition, review the features it has to offer, read the frequently asked questions, and consider the pricing plans available for customers of all sizes. If you like what you see, you can sign up today and be up and running in no time. The post Hosted edition 3 months since launch appeared first on Revive Adserver. View the full article
  5. A few weeks ago, on the five year anniversary of our project, we announced plans to create a Hosted edition of the Revive Adserver software. Today we’re proud to unveil the Revive Adserver Hosted edition. Anyone can download our free, open source software, and install it on their own server, or get a hosting firm to do that for them. Starting now, there’s another alternative. Just go to the new website for the Revive Adserver Hosted edition and sign up for an account. Our Software as a Service model means you can use the world’s most popular open source ad server software to manage your ad campaigns, without having to manage the servers, databases, backup facilities, software updates, technical staff, or any other technical and operational hassle. Just sign up, log in, and you’re in business! We’ve designed an attractive price offering. Our ad serving rate is one of the lowest in the entire ad tech industry, $0.01 CPM, so it costs just 1 cent for every 1,000 ad requests. Plans start as low as $10 per month, enabling you to serve up to 1,000,000 ad requests per month. But of course, with higher volumes you’re welcome as well. Despite these low fees, the Revive Adserver Hosted editions runs on a high performance hosting platform, in close collaboration with some of our most trusted partners. Users of the Hosted edition will benefit from rock solid stability, and lightning fast ad serving. We invite you to have a look at the Revive Adserver Hosted edition, review the features it has to offer, read the frequently asked questions, and consider the pricing plans available for customers of all sizes. If you like what you see, you can sign up today and be up and running in no time. The launch of the Revive Adserver Hosted edition is an exciting step for the entire team, and we look forward to welcoming you on board! The post Revive Adserver Hosted edition Launched! appeared first on Revive Adserver. View the full article
  6. Ever since we publicly announced the Revive Adserver open source project, on September 13, 2013, we kept a record of the number of installations of the software in active use. This is possible because every installation out there can do a daily check with us to find out if a newer version is available. By doing so, not only do we get a sign of life from every installation, but these checkins also include the version number of each installation. As a result, we can keep track of how many instances of each version we ever released are still being used. For the record, this is an optional feature, which is enabled by default. It can be disabled by switching a single checkbox. So, for the remainder of this post, keep in mind that the actual number of installations out there is probably higher. Every month, on the 13th, we take a snapshot of the installed base and update the chart below. This is the chart we produced on November 13, 2018: As you can see, in the first 3 years, the number of installations kept growing, but at some point midway 2016 that growth leveled off. As a matter of fact, the number peaked around 8,100 in the middle of 2017 and then started to very gradually decline. At first glance, this might seem like a bad thing. However, as with so many things in life, there are multiple sides to the same story. Just take a look at the following chart, which shows the different versions in use over time. It starts in July 2015, which is the first snapshot we kept of this break-out by version: The oldest versions 3.0, 3.1, and 3.2, while still in use for a number of installations, steadily decline and currently represent about 41% of the total installed base. Version 4.0, while still being used by around 23% of installations, is also declining steadily. And the most recent version 4.1, is being used by the largest share of the installed base, 35%, and shows impressive growth. This is more clearly visible in this chart, which shows the number of active installations for versions 4.0 and 4.1. It shows a steep growth of version 4.0 up to the moment version 4.1 was released. Version 4.1 continues to increase while 4.0 gradually decreased: Not only does this demonstrate that people continue to upgrade to v4.1, but also that new installations continue to be created with v4.1 right out of the gate. Unfortunately, this graph is a little bit low on data points because we did not collect this data for the most part of 2017. Where do the newer versions come from? We believe that a major factor for the steady growth of version 4.1 is that this is the only one that is capable of running on the newer releases of the PHP engine, PHP 7.0, 7.1, and 7.2. Therefore, as more and more hosting providers and server administrators are migrating to PHP7, it is more or less mandatory to also upgrade to the newest version of Revive Adserver. Most likely those are the installations that are used the most actively, and so there is a real sense of urgency to keep the software up to date. Why are outdated versions still running? The other side of the equation is this: why do so many installations out there still run the (by now) completed outdated versions 3.0, 3.1, or 3.2? One possible explanation is that these instances have, at some point, been installed by people that were curious about the software, and then abandoned or forgotten. Another possible explanation comes from the existence of ‘auto installers’ that are on offer at many hosting providers. While it is very appealing to be able to install an application with just a few clicks, this comes with one huge disadvantage. Most of the times, the installations created by these auto installers are impossible to upgrade. As a result, once you’re running it, you’re effectively stuck. We expect that the number of installations running these very old versions of Revive Adserver will continue to decrease, for example when hosting providers upgrade their servers to newer versions of PHP, effectively breaking ancient Revive Adserver installations that are not capable of running on PHP7 and above. Some of those ad servers will then be upgraded, hopefully to the most recent version of Revive Adserver, and ideally then kept up to date going forward. Why it’s important to always upgrade As with almost any software, it is the most sensible approach to always update to the most recent version available. Known security issues are fixed with these updates, and new features are introduced alongside fixes for newly discovered bugs. Using an outdated ad server with know security issues puts your site visitors, and your business, at risk. How to be informed when a new version is available We want to help users by informing them as soon as we release a new version of our software. To that end, we have a mailing list you can subscribe to. We’ll send a short message with a link to the blog post announcing each new version. Sign up to our update notifications mailing list, and be among the first to know about our updates! Always run the newest version, with no effort: Hosted edition Another way of always using the most up to date version of the software is by using the Hosted edition we recently announced. This Software as a Service offering, which will be unveiled in the coming weeks, is ideal for people that prefer to spend their time on other things than installing or updating software, maintaining servers, and so on. If you want to be informed as soon as the Hosted edition is available, please put your name on the waiting list. We’ll then send you an e-mail as soon as it is launched. The post Always keep your Revive Adserver installation up to date appeared first on Revive Adserver. View the full article
  7. Revive turns Five – announcing Hosted edition Today marks a special day for us, the Revive Adserver project team. Exactly 5 years ago, we announced to the world that we took what was already the world’s most popular, free, open source, ad server software, to bring it forward into the future. We called it Revive Adserver. Now, on the fifth anniversary of that memorable day, we’re proud of what we’ve achieved, and excited about the future of the project. We’ve heard from many people around the world how the Revive Adserver software enables them to display ads on their sites, in their apps, and on their video content. At at time when it seems that ad tech is more and more dominated by huge players, we feel it is important that there is an independent, open source, and free, alternative. That doesn’t mean Revive Adserver is just for small operations. As a matter of fact, we’ve seen sites running the software to display billions of ads per month. Revive Adserver has always been software that anyone can download, free of charge, in order to put it on their own server. Or to get a hosting company to put it on theirs. However, we’ve also heard time and time again, from people eager to use Revive Adserver, yet unable to install and run it themselves. There could be several reasons: lack of time, lack of skills, and so on. We’re working on offering a Hosted edition of the system in the last quarter of 2018. If there is sufficient interest, we’ll be able to operate a low cost, high performance hosting platform, in close collaboration with some of our most trusted partners. Users of the Hosted edition will benefit from rock solid stability, lightning fast ad serving, at very reasonable rates. Starting today, you can sign up for a waiting list for the Hosted edition of Revive Adserver by submitting the form below. There is no obligation by doing so, all it means is that you’re expressing in interested in this exciting new service, operated by the same people that brought you the downloadable version. We’re excited about this project and can’t wait to find out if the community is equally excited. Hosted Edition Waiting List Put yourself on the waiting list for the Hosted Edition by submitting the form below. Name* First Last Email* Number of ad impressions per month*Your best guess, please Select one from this list Between 0 and 1 million Between 1 and 10 million between 10 and 25 million more than 25 million I really don't know (yet) Ad server experience*Have you used an ad server before? Select all that apply. DFP Self-hosted Revive Adserver Some other ad server No ad server experience Location* Country Select a country from the list Afghanistan Albania Algeria American Samoa Andorra Angola Antigua and Barbuda Argentina Armenia Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia and Herzegovina Botswana Brazil Brunei Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Colombia Comoros Congo, Democratic Republic of the Congo, Republic of the Costa Rica Côte d'Ivoire Croatia Cuba Curaçao Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic East Timor Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Faroe Islands Fiji Finland France French Polynesia Gabon Gambia Georgia Germany Ghana Greece Greenland Grenada Guam Guatemala Guinea Guinea-Bissau Guyana Haiti Honduras Hong Kong Hungary Iceland India Indonesia Iran Iraq Ireland Israel Italy Jamaica Japan Jordan Kazakhstan Kenya Kiribati North Korea South Korea Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macedonia Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Mauritania Mauritius Mexico Micronesia Moldova Monaco Mongolia Montenegro Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Zealand Nicaragua Niger Nigeria Northern Mariana Islands Norway Oman Pakistan Palau Palestine, State of Panama Papua New Guinea Paraguay Peru Philippines Poland Portugal Puerto Rico Qatar Romania Russia Rwanda Saint Kitts and Nevis Saint Lucia Saint Vincent and the Grenadines Saint Martin Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa Spain Sri Lanka Sudan Sudan, South Suriname Swaziland Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand Togo Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Tuvalu Uganda Ukraine United Arab Emirates United Kingdom United States Uruguay Uzbekistan Vanuatu Vatican City Venezuela Vietnam Virgin Islands, British Virgin Islands, U.S. Yemen Zambia Zimbabwe Please confirm This iframe contains the logic required to handle Ajax powered Gravity Forms. The post Revive turns Five – announcing Hosted edition appeared first on Revive Adserver. View the full article
  8. Revive Adserver v4.1.4 is available now. This new version of the Revive Adserver software includes two new settings that can be enabled, one to prevent the creation of a unique but random ID value in the OAID cookie, and the other to anonymise IP addresses coming into Revive Adserver before they are processes. These new settings will help with GDPR compliance. To take advantage of the new settings, log in as an Administrator and go to the Configuration tab. The Banner Delivery Settings page is automatically displayed. The new settings are in a section called “Privacy Settings”: Put a checkbox in the setting(s) you want to enable and don’t forget to click the “Save changes” button at the end of the page. If the “Disable unique Viewer id cookies” setting is On, any existing OAID cookies for visiting browsers will be replaced with the same value for every visitor: 01000111010001000101000001010010. This is the binary representation of the acronym GDPR. New visitors will also receive a new OAID cookie with value 01000111010001000101000001010010. If the “Anonymise viewer IP address” setting is On, then the Revive Adserver software will turn the 4th octet of any IP address it deals with into a zero, thus making it meaningless when it comes to identifying individual visitors. For example: 192.168.1.123 will become 192.168.1.0. The anonymized IP address will subsequently be used for geotargeting (if enabled) or for recording conversion statistics. In this release v4.1.4, these two settings will be Off by default in the interest of backward compatibility. In a future release, most likely v4.2.0, the defaults will become On. Below is a list of all changes in Revive Adserver v4.1.4: New feature: Added new privacy settings under ‘banner delivery settings’ to optionally stop tagging viewers via a cookie with a unique identifier (OAID) and to anonymise IP addresses, in order to better comply with GDPR regulations. Fixed an issue with evaluating very large delivery rules that caused an internal error with the PCRE library. Reverted a change introduced in v4.1.2 that was preventing preferences from being properly saved. Full release notes for v4.1.4 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.4 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.4 released appeared first on Revive Adserver. View the full article
  9. If you work in the digital advertising industry, you must have heard about GDPR by now. So a very brief introduction should be sufficient. GDPR is an acronym for “General Data Protection Regulations”, which is a law that was adopted by the European Parliament in the autumn of 2015 and which came into force on May 25, 2016. There was a 24 month implementation period, and as a result the enforcement of GDPR commences on May 25, 2018. We want to help the community understand how GDPR and other privacy regulations apply to using the Revive Adserver open source software. That’s why we’ve published a number of articles. The first article has an introduction about GDPR and how it relates to the Revive Adserver software. The second article describes how the Revive Adserver software treats personal data. Privacy and data protection are important topics, but they are also complicated. Regulations are updated all the time and their interpretation evolves constantly, for example from jurisprudence. We will update the aforementioned articles from time to time when new insights become available. The post Revive Adserver in the age of GDPR appeared first on Revive Adserver. View the full article
  10. Help us test the upgrade of Geotargeting rules to GeoIP2 The Revive Adserver project team is looking for help from community members to test the upgrade path of geotargeting to GeoIP2. In a recent blog post, we announced our plans to modernize the Geotargeting feature in Revive Adserver. The upcoming version 4.2 of Revive Adserver will have support for the new GeoIP2 and GeoLite2 data files published by MaxMind. In the blog post, we mentioned that we intend to include a migration process for existing geotargeting rules. This would ensure that banners with existing getoargeting will be converted from the current format to the new format, as best as possible. However, we recognize that there are very many ways to use geotargeting, and even more combinations of all of those. As a result, it would be virtually impossible to define a set of test cases that cover every possible use case. The second best alternative is to enlist the help of the Revive Adserver community. If you use Revive Adserver with a few dozen, or preferably a few hundred banners, that have geotargeting rules specified, and if you’re willing and able to send us an export of the banners and targeting tables from your database, then please consider submitting the form below. Once we are ready to start testing, we will contact you (or a subset of the applicants if there is much interest) and provide instructions on how to send us the necessary table exports. Yes, I would like to contribute to the Revive Adserver project by participating in the Geotargeting upgrade path test process. My name* First name Last name My Email address* A note about your privacy: any personal data collected through this form will only be used to contact you for this particular test. The Revive Adserver project team will not share your data with anyone, and we will not contact you for anything other than this test. If you’re unable to assist us with this specific item, then please consider helping us by becoming a sponsor of the Revive Adserver project on Patreon. For as little as $10 a month or more, your financial contribution helps us to continue developing Revive Adserver so that it continues to be the world’s most popular, free, open source ad server system. The post Help us test the upgrade of Geotargeting rules to GeoIP2 appeared first on Revive Adserver. View the full article
  11. Revive Adserver has had support for geotargeting for ages, but the world has moved on (no pun intended). MaxMind, the company that creates and maintains the data files needed for the feature, is about to stop supporting the old “GeoIP” data files in favor of their newer GeoIP2 file format, and the free GeoLite2 files. We’re working on a new release, v4.2.0, of the Revive Adserver software, with support for these new GeoIP2 and GeoLite2 data files created by MaxMind. Here is what we have in mind: Starting with version 4.2, the Revive Adserver software will no longer ship with the original ‘MaxMind GeoIP’ plugin. Instead, there will be a new plugin that supports the new GeoIP2 and GeoLite2 data file formats distributed by MaxMind. It is our intention to develop a ‘migration’ so that any existing banner using a geotargeting delivery rule will automatically be converted to the new format. While upgrading from any older version of Revive Adserver to version 4.2.0, the old MaxMind GeoIP plugin will be removed automatically, to make room for the new one. The reason for this is that the new “Geo” delivery rules will not be compatible with the old rules. MaxMind no longer allow us to distribute the free GeoLite2 Country data file with our software releases. That will mean that our distributions will become a lot smaller in the future, since it no longer contains a large .dat file from MaxMind. It is our intention to add functionality to the new geotargeting plugin to enable it to download the required data files from the MaxMind website and store them on the server where the Revive Adserver software is installed. It will also be able to download subsequently updated files released by MaxMind on the first Tuesday of each new month. Please keep an eye on our blog, Twitter feed or forums to stay informed about the upcoming v4.2.0 release. The post Modernizing geotargeting in Revive Adserver appeared first on Revive Adserver. View the full article
  12. Revive Adserver v4.1.3 is available now. This is a maintenance release taking care of a single non-critical bug that was discovered in Revive Adserver v4.1.2 shortly after it was released on February 6th, 2018. Version 4.1.2 had some changes to how time zones are handled during the change to and from daylight savings time (DST). This turned out to trigger an old bit of code that caused the display of statistics with a breakdown by hour to be disfigured. See issue 949 with the fix as recorded on our Github account for more details. If you haven’t upgraded to v4.1.2 yet, we recommend that you skip that version and upgrade straight to v4.1.3, since it contains all the changes and fixes of v4.1.2 plus the fix for the new bug. If you have already upgraded to v4.1.2, and can live with this small bug, you can consider skipping this upgrade, since the fix will also be included in future releases. If you have already upgraded to v4.1.2, and would prefer to just implement the fix, see the Github issue and the code change. Below is a list of changes in Revive Adserver v4.1.3: Fixed an issue that prevented properly displaying hourly breakdown statistic screens. Full release notes for v4.1.3 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.3 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.3 released – bug fix appeared first on Revive Adserver. View the full article
  13. Revive Adserver v4.1.2 is available now. This new release fixes a number of bugs that were discovered since the release of Revive Adserver v4.1.1 on October 24, 2017, and it has a small improvement for the HTML5 banner functionality introduced with v4.1 in October 2017. Below is a list of changes in Revive Adserver v4.1.2: Improved HTML5 banner compatibility by whitelisting a few more common file extensions, e.g. “.svg”, “.txt”, “.json”, “.xml”. Fixed an issue that was sometimes preventing file/folder permission errors from being written to the debug log. Fixed an issue with the Campaign Banners page not working when the banner preview was enabled and the campaign contained a mix of HTML5 and regular HTML banners. Fixed an issue with saving account preferences on MySQL 5.7+. Fixed an issue with failing to warn users about silent delivery rule data truncation when using MySQL. Fixed an issue with the core delivery rule code failing to take into account changes to data made by delivery rule plugins, causing the UI to report an issue with delivery rules, when in fact, the rules were working. Fixed an issue with incorrect timezone conversion during DST switches, potentially affecting campaign activation/deactivation times. Fixed a broken help link for video banner invocation in the UI. Various language updates and corrections. Full release notes for v4.1.2 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.2 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.2 released – bug fixes appeared first on Revive Adserver. View the full article
  14. In January 2017, we announced that Revive Adserver had launched on Patreon, a crowdfunding site that allows Revive Adserver users to make a small financial contribution each month, to help the Revive Adserver project. Then, in May 2017, we reported that we had already met our first goal of $250/month, and how that was helping us to do more, as well as that we were approaching the next goal of $500/month. Today, we are delighted to be able to announce that we have now reached our $500/month goal, and are only $173/month away from our $1000/month goal as well. However, our next goal of $1000/month is a massive one for Revive Adserver – this is when we plan to block out guaranteed weekly development time. The income from our Patreon site is already helping us to spend more time on the project, but being able to block out guaranteed development time would be huge. To help give you an idea of what this could mean, we could: Continue with our already improved level of support via the Community Forums; Continue with our work to update the documentation to cover all areas of functionality; and Release more new features and bug fixes – in 2017, we put out a release of Revive Adserver roughly every quarter, resolving 33 bugs (4 of which fixed security issues), as well as introducing a host of important new features: HTML5 banner support; new WYSIWYG HTML editor option for HTML banners; improved security by expiring a user’s sessions when their password is changed/recovered; disable impression and click logging for expired banners, to reduce overcounting in statistics; new hostname/domain name whitelist/blacklist delivery rules; support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated; zone chaining to undefined sized zones. Imagine what we could do with guaranteed weekly development time! Please help us to do even more in 2018 by getting us to our next Patreon goal – consider supporting us at a level that you are comfortable with. Although we suggest $10/month as a starting point, you are free to sponsor us at any level, so, if a cup of coffee per month is all you can afford, then please, don’t hesitate to sign up and support us with a couple of dollars. There are over 8,000 instances of Revive Adserver in use, so if everyone contributed just a small amount each month, we could easily meet not just our next goal of $1000/month, but many of the goals after that! Thank you, The Revive Adserver Team The post Help us reach our next Patreon goal appeared first on Revive Adserver. View the full article
  15. Revive Adserver v4.1.1 is available now. This new release fixes a number of bugs that were discovered since the release of Revive Adserver v4.1.0 on October 18, 2017. Users trying to upgrade their installations reported problems when they initially installed the software before v2.8.x. These problems have now been fixed. Systems that were initially installed with v3.0 or higher, were not affected. We also fixed a small but annoying issue on the Campaign Properties screen when editing an existing campaign. Below is a list of changes in Revive Adserver v4.1.1: Removed newly added database integrity check for default values and not null constraints, that was preventing successful upgrades when the database itself was created before 2.8.x. Fixed various issues preventing a direct upgrade from phpAdsNew 2.0.11-pr1 and possibly earlier 2.4/2.6 versions. Fixed an issue that was causing the campaign radio button on the campaign edit screen to be empty and the bottom half of the form to disappear when editing an existing campaign. Full release notes for v4.1.1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.1 released – bug fixes appeared first on Revive Adserver. View the full article
  16. We’re very proud to announce the immediate release of our newest software product: Revive Adserver v4.1 is available now. This version of the world’s most popular, free, open source ad serving system contains several enhancements and improvements (described in detail below) and some bug fixes. The most important enhancements are: support for HTML5 ads (beta), new delivery rules for whitelisting and blacklisting domains, and a WYSIWYG editor for HTML banners. Below is a list of enhancements and improvements included in Revive Adserver v4.1: We added a new (optional) setting to prevent a user from being redirected to the landing page associated with a banner, when the banner has been deactivated or when the campaign it belongs to is no longer active. In such cases, impressions and clicks on those banners will no longer be counted either. When generating invocation codes (tags), there is a much shorter comment than in earlier releases (long comments can be switched on while generating tags if so desired). In the user interface, a number of terms have been renamed, to bring the language used into line with modern terminology used in the advertising industry: * ACLs are now Delivery Options; * Delivery Limitations are now Delivery Rules; * Targeting Channels are now Delivery Rule Sets. We added some new Site Delivery Rules, to enable white-listing or black-listing based on hostnames and/or registerable domain names. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new security feature to invalidate all the active sessions of the current user when changing or recovering their password. We added the option to use TinyMCE as a WYSIWYG HTML editor (just like in WordPress) when creating and editing HTML banners. The editor is switched off by default, for increased backwards compatibility, but it can be enabled by default via the user interface account preferences. This preference is ignored when editing HTML ads containing scripts or iframes in order to avoid inadvertently altering 3rd party tags. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new {img_url_prefix} magic macro that will print the configured http/https images URL during delivery, depending on the calling protocol. We added (beta) support for HTML5 banners, allowing the upload of banners in IAB compliant ZIP file formats. The development of this feature has been sponsored in part by Aqua Platform, a company specializing in Revive Adserver hosting at enterprise scale. We added support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated, on the main index page for each, to make finding recently updated entities easier in large installations. We added automatic switching to the mysqli driver when mysql is selected as the database type in the configuration file, but the mysql extension is not available (and vice versa). We added custom events for Javascript Async delivery, allowing the website to better interact with Revive Adserver, e.g. to refresh some ad placements or modifying the data that is sent to and received from the ad server. There have also been many other smaller enhancements and improvements, described in detail in the release notes. We have fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes. Important: this v4.1 release has a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0. Full release notes for v4.1.0 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1 released appeared first on Revive Adserver. View the full article
  17. The Revive Adserver team announces Release Candidate 2 of Revive Adserver v4.1. After recently publishing the first Release Candidate for v4.1, our testers found several bugs related to performing an upgrade from an earlier version, when the database server being used is PostgreSQL. These bugs have now been fixed. This matter does not affect users of the MySQL database server software (which is in use by the majority of people). We took advantage of the extra time this gave us to add one new feature: Custom events for Javascript Async delivery, allowing the website to better interact with Revive Adserver, e.g. to refresh some ad placements or modifying the data that is sent to and received from the ad server. For an overview of all the other changes, improvements and fixes in this release candidate 2, please review our blog post about Release Candidate 1. Important: these release candidates, and the actual v4.1 release later, will have a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0. Full release notes for v4.1.0-rc2 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1 Release Candidate 2 is available for download now. Please keep in mind that this is a release candidate, and as such it can result in issues. If you don’t feel confident about testing beta-level software, we recommend that you wait until the final v4.1 is available. This will be announced here on the blog. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Several new developments in version 4.1 have been sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. The post Release Candidate 2 for Revive Adserver v4.1 appeared first on Revive Adserver. View the full article
  18. The Revive Adserver team is immensely proud to announce the immediate availability of the Release Candidate of Revive Adserver v4.1. Today marks the fourth anniversary of the unveiling of the Revive Adserver project, with the release of version 3.0. We feel that this is the perfect day to announce the next major release of the Revive Adserver software, which has been given version number v4.1. Since this new version includes a large number of changes and enhancements, including some breaking changes, we think it is appropriate to first make available a Release Candidate. This will enable users, administrators, plugin developers, hosting providers and consultants to put the new version to the test in all sorts of scenarios and environments. If everything goes according to plan, we expect to release the final v4.1 in 2 weeks from today. Below is a partial list of enhancements and improvements included in this Release Candidate for Revive Adserver v4.1: We added a new (optional) setting to prevent a user from being redirected to the landing page associated with a banner, when the banner has been deactivated or when the campaign it belongs to is no longer active. In such cases, impressions and clicks on those banners will no longer be counted either. When generating invocation codes (tags), there is a much shorter comment than in earlier releases (long comments can be switched on while generating tags if so desired). In the user interface, a number of terms have been renamed, to bring the language used into line with modern terminology used in the advertising industry: * ACLs are now Delivery Options; * Delivery Limitations are now Delivery Rules; * Targeting Channels are now Delivery Rule Sets. We added some new Site Delivery Rules, to enable white-listing or black-listing based on hostnames and/or registerable domain names. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new security feature to invalidate all the active sessions of the current user when changing or recovering their password. We added the option to use TinyMCE as a WYSIWYG HTML editor (just like in WordPress) when creating and editing HTML banners. The editor is switched off by default, for increased backwards compatibility, but it can be enabled by default via the user interface account preferences. This preference is ignored when editing HTML ads containing scripts or iframes in order to avoid inadvertently altering 3rd party tags. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new {img_url_prefix} magic macro that will print the configured http/https images URL during delivery, depending on the calling protocol. We added (beta) support for HTML5 banners, allowing the upload of banners in IAB compliant ZIP file formats. The development of this feature has been sponsored in part by Aqua Platform, a company specializing in Revive Adserver hosting at enterprise scale. We added support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated, on the main index page for each, to make finding recently updated entities easier in large installations. We added automatic switching to the mysqli driver when mysql is selected as the database type in the configuration file, but the mysql extension is not available (and vice versa). There have also been many other smaller enhancements and improvements, described in detail in the release notes. We have fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes. Important: this release candidate and the actual v4.1 release later, will have a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0. Full release notes for v4.1.0-rc1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1 Release Candidate is available for download now. Please keep in mind that this is a release candidate, and as such it can result in issues. If you don’t feel confident about testing beta-level software, we recommend that you wait until the final v4.1 is available. This will be announced here on the blog. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Several new developments in version 4.1 have been sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. The post Release Candidate for Revive Adserver v4.1 appeared first on Revive Adserver. View the full article
  19. In January, we announced that Revive Adserver had launched on Patreon, a crowdfunding site that allows Revive Adserver users to make a small financial contribution each month, to help the Revive Adserver project. So far, we are delighted that members of the Revive Adserver community have started to make contributions and that, within a week of launching, we reached our first goal of $250/month – in particular, thanks to our Revive Adserver sponsors. As a result of meeting this first goal, we’ve been able to make some great progress towards doing even more with Revive Adserver: The level of support that we’re able to provide on the forums has improved greatly – not only are we now able to respond to most posts daily, but we have been able to put in a great deal of effort to go through the history of unanswered posts and respond to most of them. (If you have a post that’s waiting for a response, please comment on it and we’ll respond!). We’ve been able to spend time working on user documentation – many of the items on our documentation “todo” list have been crossed off. The core team has been able to spend more time coding and reviewing community proposed changes – this week’s Revive Adserver v4.0.2 release is a direct result of the time that our Patreon sponsors have made available through their support. Of course, there are benefits to supporting Revive Adserver on Patreon as well! Depending on your level of support, there are options to: Get a weekly update on what the Revive Adserver team have been working on; Get advance notice of upcoming software releases, to let you plan for upgrades; Participate in occasional “Ask Me Anything” sessions with the core team; Vote on (and propose) what features should be included in future releases of Revive Adserver; Get your (or your company’s) name on our list of Revive Adserver sponsors; and Help the Revive Adserver project move forward faster – especially with regards to completing documentation and developing new features! Some of the above benefits will only become available once we meet certain goals on Patreon – at the moment, we are only $152/month away from our next goal. Please help us meet our next goal – consider supporting us at a level that you are comfortable with. There are over 8,000 instances of Revive Adserver in use, so if everyone contributed just a small amount each month, we could easily meet not just our next goal of $500/month, but many of the goals after that! The post Patreon and Revive Adserver appeared first on Revive Adserver. View the full article
  20. Revive Adserver v4.0.2 is available now. This new release includes one new feature and a number of bug fixes. Below is a list of changes in Revive Adserver v4.0.2: New: Revive Adserver now supports zone chaining to zones where the dimension(s) of the zone are undefined (i.e. “*”) as well as an exact match. Improved the handling of Email/Newsletter zone linking, to ensure that disallowed HTML banners are simply not shown in the first place when linking from the zone, and to fix a bug that allowed HTML banners to be linked to Email/Newsletter zones from the banner. Fixed a JavaScript error that occurred on the Campaign Properties page when the global Enable Conversion Tracking option is disabled. Fixed an issue with the Client/Language delivery limitation not properly working when targeting specific territories (e.g. en_US) or targeting the broader locale when the browser is only sending locale + territory. Improved the warning messages used when generating Local Mode and XML-RPC invocation tags to clarify why these tags are not compliant with IAB guidelines for ad impression measurement (i.e. the ad request comes from the server, not the client). Fixed numerous instances of incomplete breadcrumb trails in statistics pages. Broken examples of Inline Video banners have been removed from the UI. Fixed an incompatibility with recent MySQL versions (5.7.5+) when acquiring advisory locks, due to their name being now limited to 64 characters. Changed misleading “Connection Window” wording to “Conversion Window” in the settings screen, to match the current usage. Full release notes for v4.0.2 can be found on our Github page. Download, install and upgrade Revive Adserver v4.0.2 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.0.2 released appeared first on Revive Adserver. View the full article
  21. Revive Adserver v4.0.1 is available now. This new release fixes a number of bugs and security issues that were discovered since the release of Revive Adserver v4.0.0 on September 28, 2016. Below is a list of changes in Revive Adserver v4.0.1: Fixed an issue in the newly introduced mysqli driver, which was preventing the delivery engine from working when using unix sockets to connect to the database. Fixed an issue with the banner properties page accepting weights of zero, negative or numbers with decimal points. Fixed an issue preventing Revive Adserver from being installed or upgraded on setups using both a custom session.save_path and open_basedir, or using a custom session handler. Fixed an issue preventing Revive Adserver from serving video ads on recent Flash Player versions when loading HTTPS resources from an HTTP website. Fixed an issue preventing the Revive Adserver XML-RPC API from working on PHP 7+. Fixed an issue preventing forms generated with HTML_QuickForm from working with PHP 7.1. Fixed an issue with the “View by day/week/month” dropdown not properly working on PHP 7+. Fixed an issue with magic macros not properly working when nested in curly brackets, e.g. within JSON or JavaScript code. Fixed an issue with parent entities names being sometimes escaped twice in the inventory header, thus displaying HTML entities on screen. Fixed a missing translation string that prevented an error message from displaying in the installer, and various community-supplied translation string updates. This version 4.0.1 also contains fixes for four vulnerabilities that were recently discovered and reported to us through our HackerOne security program. Full release notes for v4.0.1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.0.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. View the full article
  22. Did you know that the idea of Revive Adserver is nearly 4 years old? It was early 2013 when the opportunity came along to purchase the OpenX Source code base from OpenX, and Erik, Matteo and myself decided to work together to create Revive Adserver, and breathe some new life into a project that had pretty much stalled for 5 years. In the years that have followed, we’ve made terrific progress – something that we are immensely proud of. However, it’s been clear for a while now that the community and the core Revive Adserver team want more. More features, more fixes, more documentation. And, what’s more, we want to do it faster. This was something that was confirmed by the results of our community survey last year. Today, to try to make this happen, Revive Adserver has launched on Patreon. If you’re not familiar with Patreon, it’s a crowd-funding website, but (unlike, say, Kickstarter), it’s not about raising funds for a specific, one-off development or product. Instead, it’s about delivering regular, monthly funding to the project, to allow the core team to spend more time on developing the things that the community wants. If you use Revive Adserver to help generate revenue from advertising, and you’re part of the community that wants to see more development and documentation done for Revive Adserver, then we need your help. We’re not asking for a fortune – just a small amount each month. Even just $10 a month per sponsor will help us a lot. Larger contributions are of course also very welcome. Please, visit our Patreon site, see what we have to say about what we want to achieve with your help, and sign up as a patron. Together, we will take Revive Adserver forward to another level, and see where the next 4 years takes us! View the full article
  23. In our last blog post, discussing the results of the Revive Adserver 2016 Community Survey, we highlighted the fact that, on the whole, the community would like to see more features added to Revive Adserver, but that there were mixed views on how this should happen – a mixture of improving documentation to allow more developers to contribute, as well as seeking corporate sponsorship or crowdfunding to allow the core developers to spend more time working on the project. Following on from that theme, the core Revive Adserver team would like to publicly thank Platform IQ, who have now sponsored the development work for two core features: they paid for both the development work in the Revive Adserver 4.0 release to replace the phpSniff library for browser & operating system detection with the more modern Sinergi library, and for the development of the asynchronous tags feature that was introduced in Revive Adserver v3.2 in the spring of 2015. Without Platform IQ’s sponsorship, it is likely that these features would not have been released. If you are in need of professional services for Revive Adserver, then please do consider Platform IQ, given their very generous sponsorship of the Revive Adserver development effort. You may even notice some advertising appearing from Platform IQ, across our site and forum in the near future, as we experiment with ways to generate revenue to enable us to develop new functionality in Revive Adserver. In addition, we also want to thank Aqua Platform, who are sponsoring the hosting of our website, forum site, and other sources, and the SSL certificates we use. Aqua Platform specializes in Revive Adserver hosting, and have been a great help when we were doing performance testing for the improved browser and operating system targeting functionality in Revive Adserver v4.0. We would also like to take this opportunity to let larger, corporate users of Revive Adserver know that if they have a need for new functionality to be added to Revive Adserver, then we would please ask that they get in touch with the core team. We would love to discuss your needs, particularly if it’s a commonly requested feature. It may be that even a modest contribution towards the development of the feature will help make it happen faster, especially if there are a number of corporate users looking for the same functionality. View the full article
  24. In May 2016, we asked the Revive Adserver community to take part in our first ever survey, to find out more about what the community thinks about the Revive Adserver project. Thank you all so much for taking part – we were delighted to receive just over 140 responses to the survey. Somewhat unsurprisingly, our most active and engaged members of the community were the primary respondents – over 80% of responses came from users who were (at the time of the survey) using an up to date version of Revive Adserver. Over the last few days, we have been taking a look at the results of the survey and wanted to share the following information with you all. There are both new & old engaged community members We were delighted to see a good mix of engagement from both newer arrivals to Revive Adserver, as well as old hands who have been using the software for many years. Revive Adserver is primarily used for small businesses While most Revive Adserver is mostly used by small business users, the next biggest segment is users at larger companies where there’s a team of users. It was also interesting to see that the 3rd biggest segment of Revive Adserver users are using the software in a number of different situations, suggesting multiple installations for different uses. Primary use of Revive Adserver The community thinks Revive Adserver has key missing features It’s hardly a surprise to learn that on the whole, the community thinks that it would good to have some key missing features added to the product. Project Development Speed There’s one clear winner for a key missing feature The clear and obvious winner for a key missing feature is native HTML5 banner support in Revive Adserver, with over 65% of respondents listing this feature in their “top three” missing key features. The next most requested missing feature was cookie-free banner delivery, with just under 50% of respondents listing this feature in their “top three”. It was also pleasing for the Revive Adserver team to see that the most popular “other” suggestion put forward by the community was native MySQL support in PHP 7, which the team has added with the release of Revive Adserver 4.0.0. The community wants “someone else” to fund development When respondents indicated that development on Revive Adserver could be faster, they were asked how they thought that could be achieved. Of these respondents, 46% indicated that the best way for development to be faster was for developer documentation to exist so that the community could make changes, and 32% indicated that corporate sponsorship should be found to let the team do more development. Only 22% of users indicated they would be willing to actually participate in funding the development of the open source project. How should development speed be increased? Those who do want to fund development are split on how this should happen There was an almost equal split between the top four options selected for how any possible funding should be obtained – one-off crowdfunding for a fixed set of features, monthly contributions, one-off crowd funding on a feature-by-feature basis, and purchasing commercial plugins. We hope that the above information is of interest to you all, as members of the Revive Adserver community. We’re proud of what we’ve achieved in the last 3 years of Revive Adserver’s existence, and in the coming weeks, we will be discussing the survey results in more detail within the core team, to decide on our plans for the next 3 years and beyond! View the full article
  25. When we released Revive Adserver v4.0 at the end of the September, we wrote in the release notes that: Browser and Operating system targeting was greatly improved and modernized by replacing the old phpSniff library with a modern alternative (called Sinergi Browser detector), resulting in a significant speed improvement That’s a pretty bold claim, so we were delighted when we saw a recent blog post by the team at Aqua Platform with some test results that confirm it is actually true in an operational environment. Aqua Platform is a company specializing in Revive Adserver hosting at huge scale. Their performance monitoring keeps track of the time it takes for an ad request going into the ad server to be completed and returned to the client. It does this by running a check every minute from a few dozen probe servers around the world. The performance graph below shows the average ad server response time of a 7 day period. About half way through that week, the upgrade from Revive Adserver v3.2 to v4 took place, and it is striking to see how significant the speed improvement is: Speed improvement after upgrading to Revive Adserver v4.0 Before the upgrade, an ad requests completed in about 200 milliseconds, but after the upgrade it was almost twice as fast at around 110 milliseconds. It turns out this result doesn’t even take into account the fact that Revive Adserver is now fully compatible with PHP7. A further performance improvement could still be in the works! In an industry where ad servers often take more than 500 milliseconds and sometimes even longer, the results that Aqua Platform have achieved with Revive Adserver are nothing short of remarkable. Thanks for the team at Aqua Platform for sharing these results in their blog post “Aqua Platform is (almost) twice as fast with Revive Adserver v4.0“. View the full article
×
×
  • Create New...