andrewatfornax

Apart from, as @karen.mikaela mentions, there being a bug in earlier Revive Adserver versions (now fixed), there's also an option in Revive Adserver to deliberately attempt to over deliver, which some users report is giving them good results in keeping Contract campaigns on track. http://documentation.revive-adserver.com/display/DOCS/Maintenance+Settings

Hi @ssnobben, Nope, I'm still waiting for a magical Joomla developer to appear and offer their services :-)

Hi @angelfplaza, Revive Adserver can track requests, as well as impressions. It's there as an option. It may be that you simply need to enable tracking of requests, and/or including requests in the stats screen configuration.

Hi @Millhouse50, Just to clarify - no, there's currently no way to upload an HTML5 banner "bundle" that consists of the HTML, the images, the CSS, etc. For now, that's a manual process of either putting into the appropriate location in Revive Adserver, or on an external service.

Hi @Moe, I am not 100% certain, but you probably don't need the brackets in your regex, unless there's a reason for them that we can't see in the screenshot. I do wonder if you need to add the start and end forward slashes to the regex expression, though? It's worth a shot...?

Hi @bocadave, You'd need to pass that information into Revive Adserver as a Site Variable, and then target against the variable being passed in.

Hi @Velislav, I assume that maintenance is running? http://documentation.revive-adserver.com/display/DOCS/Running+Maintenance

Hi @frifri, In Revive Adserver, this is done through zone chaining - if a banner can't be displayed from those that are linked to a zone that's being called, then you can specify the next zone that Revive Adserver should go and look at for a banner - and that next zone can have a chained zone, and so on.

Hi @akaashk72, Please see also http://documentation.revive-adserver.com/display/DOCS/Invocation+code%3A+Zone+level which documents the different zone tags, including which ones are asynchronous.

Also, just FYI: http://documentation.revive-adserver.com/display/DOCS/Email

Hi @ryanqmix, I am not clear - why do you have to edit your MailChip template whenever you change banners? The idea is that with an email zone, you can set this up, and in the emails you send, the banner you have linked to the zone will be displayed. If you change that banner (either manually, or by setting appropriate campaign start/end dates), then the banner should change when users view the email (caching aside, if MailChip won't let you set a random number in the URL every time the email is sent).

Hi @Andrew S, Is your banner or campaign set up with delivery capping, or not?

Hi @Bast, No, not that I'm aware of - all of the delivery tags that exist are designed to return one banner from the zone for display, on the assumption that the delivery tag will do the displaying; not for returning all possible banners. The API might allow this to be done? But I have to admit, I'm not sure.

Hi @valay, Have you stepped through the troubleshooting? http://documentation.revive-adserver.com/display/DOCS/No+Statistics

Hi @Blinky, I think you need to sign up to the Revive Adserver project, so that you can contribute the translations directly, rather than creating your own project! Thanks, Andrew

Hi @brijeshguru99, That's how I would have suggested setting things up - linking the zones. Do you have a remnant campaign in that linked zone, with at least one uncapped, unlimited banner?

Hi @Patrick, No, you can't do this - if you have configured Revive Adserver to track impressions and clicks, then anything you serve up as a banner via Revive Adserver will be tracked in that way.

Hi @JimAtkinson, I agree - I can see that there are circumstances where having auto refresh in Javascript or Async tags would make sense - and I'm sure it would be possible. It's just not something that the core team has had time to implement yet. We're thinking about how we might be able to make more time for new features - stay tuned!

Hi @coopersita, That's entirely possible - on GitHub, there are a few issues listed about the fact the software that does the detection of browsers, operating systems, etc. is very old now, so chances are it's not detecting the operating system correctly. The core team is definitely considering a complete replacement of this library. Stay tuned!

Hi @Joe Blow, Sorry, no immediate ideas as to what might be wrong - any chance of pointing to a link where the issue is happening?

Hi @MrMyles, A 403 Forbidden error is something that comes from your webserver, not from Revive Adserver. You will need to check your webserver logs to see what the error is there.

Hi @KOUASSI GNAVOU CAMILLE, Revive Adserver can help you do this, but it won't do everything for you without effort, sorry. It can certainly host your banners, and offers a range of different tags types that have different mechanisms for displaying them in an HTML page; and it has support for time-based limitations - but it terms of how you manage that to them display on the user's mobile device, in the correct place, is up to you and your site/application. HTH!

Hi @AjCsocket, Yes, there certainly is. They are called delivery limitations. http://documentation.revive-adserver.com/display/DOCS/Time+delivery+limitations

Hi @webnomad, Possibly an ad blocker - those will definitely prevent Revive Adserver from installing correctly.

Hi @Meo, Well, PHP actually starts up and shuts down completely on each page load - so, it's not like a continuously running Java or C application or something where memory leaks are an issue. However, your web server may not start up and shut down a processing thread for every page load, for efficiency reasons, and so PHP memory management issues may build up as a result. You could look at the settings for your web server's thread management, as you can often configure things like how many web requests each web server thread should handle before it is shut down and a new one started up - this may help, if the issue is a slow growth of total memory being used. The other thing, however, may just be that your web server is configured to allow more threads to be started up (when needed) than the server can cope with, and so this issue is happening due to a periodic increase in traffic to the server?