Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Adi

    "data-revive-id" not changing

    Thank you @andrewatfornax for your answer. I do understand that it was an idea - to change this parameter for each installation. Now I need to reconfigure the server in order to make it the same - otherwise I need to send new codes to all zones to al the websites I work with. The question is: "How can I change this ID to the previous one?" Thank you!
  3. andrewatfornax

    Control Panel Login Database Error With SSL

    Do you have a different URL (excluding the http vs https part) when accessing via different methods?
  4. andrewatfornax

    "data-revive-id" not changing

    No need to change it - the value is unique per installation. As you have created a fresh install, the ID should be different.
  5. Last week
  6. Adi

    "data-revive-id" not changing

    Hallo, @Matteo Beccati ! I've installed the fresh webserver and Revive Adserver. But the invocation code has the new data-revive-id: <ins data-revive-zoneid="1" data-revive-id="0221d5147ec0b9b881fa2c3cfd4a172c"></ins> <script async src="//ads.abagain.net/www/delivery/asyncjs.php"></script> The websites I am working with have the old one like: <ins data-revive-zoneid="1" data-revive-id="3737cf5d3d340e4fadc9904da5d61dde"></ins> <script async src="//ads.abagain.net/delivery/asyncjs.php"></script> How (if should) and were is it possible to change this parameter?
  7. Josh

    New banners not showing often enough

    It's useful to look at the zone probability report to see what Revive is calculating for current probability. As you do this and make changes remember that caching can have some impact, switch to admin user and recalc probability in maintenance.
  8. 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
  9. Hello all, We just installed a SSL certificate on our server. When attempting to access the Revive admin control panel login page over HTTPS, the following error displays: Database connection error.A fatal error occurred Revive Adserver can't connect to the database. Because of this it isn't possible to use the administrator interface. The delivery of banners might also be affected. Possible reasons for the problem are: <ul> <li>The database server isn't functioning at the moment</li> <li>The location of the database server has changed</li> <li>The username or password used to contact the database server are not correct</li> <li>PHP has not loaded the MySQL Extension</li> </ul> The login screen still works fine over HTTP. Any ideas? I'm running Revive 3.0.7. Any insight is much appreciated!
  10. I understand fully. Can I please get the data to change the code ourselves, like we had to do a dozen times before with our old programmer? It's obvious you don't have a priority on the US date format, since you are in the UK. Can you please help me get this info, I've requested it about a dozen times over the last 6 months with zero reply. Thank you.
  11. >What version of Revive Adserver? v4.1.4 >What type of campaign, what types and sized of banners are in the campaign? Remnant campaigns with dynamic HTML-banners with no specific size (0x0) >What type of zone? What size? Custom zones with * entered as size (*x*).
  12. Hi Today when i get thirdparty javascript-tags i generally use "Generic HTML Banner" and it's working pretty well but i would like to have a "Destination URL (incl. http://)" as we have in HTML5 banner(Zip package). And with that i would like to have the possibility to override / complement the location where the banner click is routed. Example: http://thirdparty.click.url?followedby=revive-server.click.url&followedby=customclick.url&followedby=landingpage.url Final landing page url can be controlled by either thirdparty ad-provider or by customclick.url depending on if landingpageurl is defined or not in external ad source. In short: I would like to be able to break into the clickchain-url before it goes to landingpage /henrik
  13. AzHousePro

    New banners not showing often enough

    No, I have been using Revive for years and never saw anything like this. I took an old offline campaign and modified for the new advertisers and the numbers were still off. I finally gave up and migrated to google ad server.
  14. andrewatfornax

    New banners not showing often enough

    Any targeting or other limitations on the new campaign or banners?
  15. andrewatfornax

    Which VAST-Version

    https://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/
  16. andrewatfornax

    Insecure Cookies Warnings - Non-SSL Cookies

    Interesting - can you describe the setup more? What tag type, how the tags have been configured for SSL, etc?
  17. andrewatfornax

    Revive Adserver free not plugins?

    If that's something you need, then yes - Revive Adserver does not support a self-service approach for external advertisers. However, please be cautious - I have seen a number of users complain about plugins that they have bought - buying plugins from an external supplier can be a great experience, or possibly a terrible one. Please do make sure you deal with someone reputable.
  18. Earlier
  19. Many thanks, everything now working great.
  20. Thanks, andrewatfornax, I tested this schema: three servers via the load balancer and generating $etag in one place for all revive instances and this works for me.
  21. I have installed Revive-Adserver on my website and i wanted to know Should i buy Plugins for making Sign up / Login / Advertiser / Publisher / feature adding my website,
  22. AngryWarrior

    Zone Invocation Options Drop-down

    Awesome! Thank you Andre. 👍
  23. Login as system administrator Go to http://rsv.londynek.net/rserver/www/admin/account-settings-user-interface.php Tick Force SSL Access on User Interface Click save.
  24. andrewatfornax

    Zone Invocation Options Drop-down

    Thanks! Now documented: https://documentation.revive-adserver.com/display/DOCS/Tag+Settings#TagSettings-Support3rdPartyServerClicktracking
  25. If using "Delivery File Names", the files need to be redirected somehow (unless one wants to manually change file names every time one updates Revive), though I guess I could have used a symlink redirect that did not specifically redirect to an "http" URL. Way back then, though, I did not imagine Google will force us to go SSL Ideally, revive could write the symlink rewrites to an .htaccess files
  26. From memory, there's no automatic purge, because Revive Adserver cannot safely tell what statistics you want to keep vs. those that you don't want to keep. I think, though, that if you have expired campaigns that you no longer want the statistics for, then if you delete them, the statistics are also deleted...
  27. I mean something different - putting the source code on three different servers, and using a load balancer to distribute the load across the three servers.
  28. andrewatfornax

    Changing or rolling Ads on website

    HELLO! (Sorry, couldn't help myself.) To answer your question - yes, you can do targeting of banners. Please see the documentation on banner delivery rules.
  1. Load more activity


×