andrewatfornax

I think it might work with a comma separate list of emails?

https://documentation.revive-adserver.com/display/DOCS/No+Statistics https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

Yes, that's possible - how old are we talking? The site at http://www.reviveconsultant.com/articles/what-to-do-when-you-suspect-your-openx-source-system-has-been-hacked/ has some info on this.

I think there is another topic going on at the moment with this same issue, that HTTPS access to the admin UI doesn't work (assets missing). Try turning on the UI option to enforce HTTPS access only (the "requireSSL" option of the config file) and see if that fixes it?

I assume the campaign has some banners, and there are valid zones defined against which the banner type & size can be linked?

There's probably no real difference here in terms of over counting impressions that can happen with image-based delivery tags outside of emails, but I can't really say what's causing impressions to come in higher than your email open count. Perhaps it's that your email open count is low? Regardless, the following may help: https://documentation.revive-adserver.com/display/DOCS/Impressions+are+Too+High

Yes please. Your solution is to change the Revive Adserver configuration to require the use of HTTPS for the UI. This is a good idea (everyone should do that!), but nevertheless, if you have not configured the UI to require HTTPS, then it should still work, when you access it via HTTP or via HTTPS.

That could possibly be a bug - if you access the UI over HTTPS, then the assets should be given an HTTPS path. Could you please raise a ticket on GitHub about this? Thanks.

https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

Hi @bowenac, If my hosting provider updated my server's PHP and MySQL version without advising me that this was going to happen, I would be screaming down the phone at them and demanding an immediate provision of a server like I had, followed by assistance to migrate the database data and code from my server over to that new one, so that things worked again as they were. Then I would start the process of upgrading as it should be followed. To answer your other questions: 1. The upgrade documents you have linked to do not suggest doing a new install and copying the old database to a new database. They say you should copy your old database to a new database, and then upgrade using the new database. This ensure that your old database is still around in case things don't work, and you need to roll back. Doing a new install and THEN trying to copy the data from your old database will not work. 2. No, there is no way to import ads from one install to another.

Hi @bowenac, No, you can't perform a new install of Revive Adserver, and then change it to point to an old version database. The code base on disk from the new install will be set up as if it's already installed, so, there will not be the required filesystem structure in place to "trigger" the upgrade process, and it is non-trivial to reset the file system to do this. I would strongly recommend that you do not attempt a server migration + MySQL/PHP version update all in one attempt. There are too many moving parts to get things right. I would instead suggest that you take one of two approaches. Either: On your initial server, upgrade MySQL and/or PHP to match the versions that will be used on the new server. This may include needing to upgrade Revive Adserver to support the later versions of the database and PHP, if required. Once you have done this, and the MySQL and PHP versions match what you have on the new server, and Revive Adserver is working, then perform the migration to the new server. OR Ensure that your new server has the same MySQL and PHP versions as your old server. Migrate your Revive Adserver installation to the new server. Once it is working, then look into the required upgrades of MySQL and/or PHP, along with upgrades to Revive Adserver is required.

No. If Revive Adserver is generating the iFrame, then Revive Adserver is generating the content for the iFrame. In this case, because Revive Adserver has control over the content, then Revive Adserver can modify the content and perform click tracking. However, if Revive Adserver is not generating the iFrame (that is, you are getting the iFrame from a 3rd party, and putting the iFrame into Revive Adserver), then Revive Adserver will not be in control of the content of the iFrame, and Revive Adserver will not be able to perform click tracking.

Agreed!

Yes, that table should be safe to truncate. Check your database server logs & use the appropriate DB diagnostic tools first, though, to make sure that is the issue before you start truncating data. (And always take a backup before you do anything!)

Ah, sorry, I didn't understand your original post. Do you have access to the logging of your SMTP server, and can you see if Revive Adserver is actually making the requests to send emails?

1. There's an option in the global Revive Adserver configuration somewhere to enforce SSL access on the UI. It should be pretty easy to locate. 2. Well, what I mean is that if you were able to deliver banners over HTTP originally, and then you changed your webserver configuration, to add in support over HTTPS, but now the delivery over HTTP doesn't work any more, then this suggests to me that your webserver configuration is the problem. Review your webserver configuration to ensure that both HTTPS and HTTP traffic are permitted, if that's what you want. 3. No, SSL configuration of your webserver is beyond the scope of Revive Adserver documentation.

Hi @Kush Rohra, If Revive Adserver can deliver banners over HTTPS, then it can also deliver banners over HTTP - at least, at the Revive Adserver level. There's nothing in Revive Adserver that will "enforce" SSL-only at the delivery mechanism level. (You can configure the Revive Adserver UI for SSL-only access, but that's separate from banner delivery.) So, the most likely suspect here is your webserver configuration is allowing access through to Revive Adserver via SSL only. Take a look at your webserver logs and configuration.

https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken https://documentation.revive-adserver.com/display/DOCS/No+Statistics

Hi @Maro, Possibly - I'm actually not an expert in our HTML5 banner delivery mechanism - but regardless, that's a totally different thing. Revive Adserver delivering a banner that it knows about and has the details of inside an iframe that it generates itself is entirely different to Revive Adserver delivering an iframe that is hosted by someone else, which is what @Xabi has been talking about. So, yes, if you are putting an HTML5 banner into Revive Adserver, then it's not externally hosted (unless, of course, that HTML5 banner is simply an iframe, which then loads its content from somewhere else - in which case, it is externally hosted banner content), and so click tracking is possible. The comment about it being hard to make HTML5 banners responsive is, I think, a totally separate topic.

Hi @NepSter, No, sorry - you can search the site with as much ease as I can!

Well, there you go then!

Hi @Xabi, I think the answer is yes - if you want Revive Adserver to track banner clicks, then the banner can not be delivered via an externally hosted iframe. You will need to find another way of delivering the banner (e.g. putting the banner HTML inside Revive Adserver).

Yep, spot on. In fact, you can put the invocation tags from Revive Adserver on pretty much any site, regardless of where that site is hosted, or what domain it uses.

Hi @Xabi, Correct - if the banner you insert into Revive Adserver is an iframe, then Revive Adserver cannot see "inside" the iframe to modify the click URL, to tell the click to go "via" Revive Adserver to the destination, instead of going to the destination directly - so there's no way for it to count the click. Unfortunately, I don't understand what you mean by "obligatory insert the URL in my HTML code". Maybe you could explain in more detail?

I knew you were going to ask that @DonRickler, and of course, it's the Site - Variable delivery rule that you want to use, which is one of the documentation tasks that I have on my todo list... https://documentation.revive-adserver.com/display/DOCS/Site+Delivery+Rules Have a poke around the forums or on the web, I know others have done good write ups of how to do this...