Jump to content

andrewatfornax

Approved members
  • Posts

    2007
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Hi @b_mon, The last time I was looking at popups/popunders in Revive Adserver (as part of writing documentation), I came to the conclusion that popunders in Revive Adserver don't seem to work any more - it's been a very long time since anyone looked at the functionality. That may be the case, but I would need to have some time to really look into it to be sure.
  2. Hi @Shorebeat, Hey, @Matteo Beccati, I think I've seen two posts now about repeat banners appearing unexpectedly with SPC. Any chance this is related to the capping issue that we've seen with AJS? Or just coincidence?
  3. Hi @superpardo, There are no immediate plans to support AMP in Revive Adserver - but could I recommend filling out our 2016 community survey, if this is something that you are interested in? We are interested in everyone's feedback!
  4. Hi @Shorebeat, Free disk space issue? Have you checked the logs of the database server to see what it says is going on?
  5. Hi @gunangler, Glad to hear that Revive Adserver does detect the version of PHP correctly :-)
  6. Hi @gameoverdude, Perhaps Delivery Capping? See: http://documentation.revive-adserver.com/display/DOCS/Creating+a+campaign#Creatingacampaign-Deliverycapping
  7. Hi @FvLW, At the moment, Revive Adserver doesn't have any kind of native support for detecting different user device sizes and then displaying different banners accordingly. I would recommend that if you're looking to deliver different content to users depending on their device size, you will need to do this outside of Revive Adserver - that is, firstly detect the user's device size, and then invoke the appropriate zone tag for the banner size that you want to display.
  8. Hi @aibo, Yes! Give your publisher a zone tag, and then you can control what banner(s) the publisher delivers - and even change what gets delivered over time, without the publisher having to change anything.
  9. Hi @Everton, Revive Adserver can definitely support the delivery both its own user interface and of banners over SSL. Maybe you could provide more detail about exactly what's not working, and link to an example site where we can see the issue?
  10. Hi @cool_recep, So, would this effectively be an HTML5 banner? If so, you can put the HTML part of the banner into Revive Adserver as an HTML banner - but you will then need to host all the other assets (CSS, images, etc.) of the banner elsewhere, and possibly edit the HTML accordingly to load those assets. Revive Adserver doesn't (as yet) have native support for HTML5 banners.
  11. Hi @sikjoy, It appears to be an account preference, under Preferences > Account Preferences > Campaign Preferences.
  12. Hi @bdamage, I would imagine that you can see what gets executed when you use the UI to call up this information?
  13. Just to double check @gunangler, pop a .php file with: <?php phpinfo(); ?> in it, and load up the file in a browser. Sometimes you have more than one version of PHP installed, and it's the wrong one set for where Revive Adserver is running...
  14. Hi @Alex R, Just to chime in - I used to have to manage a distributed system of Revive Adserver back in the day (when it was OpenX), and while horizontal scaling is definitely a good idea, the distributed statistics that was implemented for MySQL was not a lot of fun to manage - it needed a lot of manual TLC to make sure it was always up and running - so while I sympathise with your need to scale, I would avoid distributed stats at all costs, if you can!
  15. I would agree with @Erik Geurts - when looking at your SEO, you should be focusing on the site content, rather than the site advertising. You really should be excluding all advertising from your site's SEO activities.
  16. Hi @oldteacher, Correct. The way iframes work is, in effect, to spawn off a completely separate browser inside each frame, and there's no way to allow those frames to communicate with each other. So, Revive Adserver can't have the different iframes communicate with each other to stop them displaying the same banner in different places by chance. See http://documentation.revive-adserver.com/display/DOCS/Tag+settings for more details on the different tag options that control this kind of thing, and which tags they are available with.
  17. Various tag options are documented here, by the way: http://documentation.revive-adserver.com/display/DOCS/Tag+settings
  18. Hi @Francesco Spina, Having only had a very brief look at Google Amp Pages, I don't see why it would not be possible for Revive Adserver to support this. Have you actually used Revive banners in an Amp Page, though? And are there any specific things that this then causes the page to fail on re: validation?
  19. Thanks @niska, If you have not already, can you please log as a bug on GitHub (and include a link back to this post in the report)?
  20. Hi @bmanke, Depending on what version you are currently on, the upgrade may help a lot - over the last few years, we have made more than one or two bug fixes that have been around for a long time, that all help with making delivery more accurate. HTH,
  21. ... Which I am pleased to say is one of the items mentioned in the FAQ re: banner delivery not working! https://www.revive-adserver.com/faq/troubleshooting-banner-delivery/
  22. Hi @iko, I think that the answer to "Why doesn't Revive Adserver support HTML5 banners?" is two fold: 1. You can absolutely put the required HTML for an HTML5 banner into the HTML banner type, and deliver it; but you will need to sort out all of the external content for said banner yourself; and you may need to manually sort out all of the linking/click tracking URLs, depending on how complex the HTML itself is. So, Revive Adserver does support HTML5 banners; but it's certainly not as well supported as it could possibly be. 2. Why it's not better supported is basically the same answer as to the same question for VAST 2.0 support, which you can read here: https://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/ I hope that helps.
  23. For completeness, though: There were no database table changes from Revive Adserver 3.2.2 to 3.2.4; previous last table change (prior to 3.2.4) was in 3.2.1. Not the simplest thing to read without reformatting, but this is all defined in: https://github.com/revive-adserver/revive-adserver/blob/master/etc/changes/openads_upgrade_array.txt
×
×
  • Create New...