Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Hi DanFlag, The way to get to this page is to do the following: Inventory > Websites > {www.example.com} > Invocation Code. Then, select the various option(s) that you want, and click on the "Generate" button. This will take you to the page you're talking about, but with all of the relevant parameters passed into the script to make it work. Hope that helps! http://documentation.revive-adserver.com/display/DOCS/Invocation+code%3A+Website+level
  2. Hi Richard, Thank you for your comments, and I wish I had a magic wand I could help you out with! Unfortunately, the core Revive Adserver team is aware that some people have problems with "plugins" they purchase for Revive Adserver from external parties; but at the same time, there are some very reputable, reliable plugin developers for the product as well. The core team have discussed the idea that it would be good to have an official part of the Revive Adserver website where plugin developers can register to be listed, and against which users can rate them e.g. 1-5 stars, leave comments, etc. We do think this would be a good idea, but as with any open source project, the question is always - would spending the time setting that up be worth it, vs. other things we could be doing (e.g. the new Revive Adserver 3.2.0 release out today with asynchronous tags!). As always, the core team is open to suggestions - please, dear community - if this is a major problem for the masses, let us know here, and we'll do our best to listen and prioritise based on your communal feedback. Thanks! Andrew
  3. Noted, and now delivered in Revive Adserver 3.2.0.
  4. And indeed, Revive Adserver 3.2.0 has now been released, which includes native asynchronous tag support.
  5. A better solution now is to use the new asynchronous tag type available from Revive Adserver 3.2.0 onwards.
  6. Hah! You're a proper tease, Matteo! The core team hopes to have this out in the next release, which should come out as a beta, soon - all thanks to Matteo's hard work, and a generous sponsor.... Details will be announced when it's ready!
  7. Anyone else seen old stats not showing up after upgrade? So far, all the test and production upgrades I'm aware of have worked okay. Try clearing caches, restarting web server, etc.?
  8. Ah, okay, I see - shows you how little work I've done (i.e. none) for Apple devices. Sounds like something for us to add on the roadmap. Thanks.
  9. No, there is no "built in" feature in Revive Adserver to do this - but you could hand-crank this if you really needed to.
  10. No immediate plans from the core Revive Adserver team, no. Sorry!
  11. The feature to only display a banner once per page is actually impossible with iFrame tags (as opposed to "not available by default"), as iFrames load independently in the browser, so there's no way to allow them to communicate with each other to ensure that a banner only shows once. As mentioned above, though, you could set up multiple iFrame zones, and traffic your banners accordingly to ensure the situation can't arise where you show the same banner twice, but that's not the automatic, effort free solution that you can get with e.g. the JS tag type.
  12. As above - or you can just put your default banner or default network tag into a Remnant campaign, and traffic it to your zone(s) along with other campaigns, and appropriate limits/targeting as required, to ensure that the Remnant campaign is there to collect any inventory that would otherwise be unused.
  13. Simple: 1. Either you are showing blank impressions (i.e. banners are not appearing in the zone every time); and/or 2. You are getting drop off (i.e. people leave the page before a banner loads, so you see the page views in your stats recorded, but no banner impressions, because the banner didn't load in time). Cheers, Andrew
  14. Chances are the Tradetracker banner can't be altered by Revive Adserver using the "Generic HTML Banner" approach to intercept and track clicks. It may need a plugin update to support it. Is anyone else seeing the same thing?
  15. Nope, using PHP accelerators is fine, and won't affect the stats.
  16. Hi, Please see the documentation - we have a troubleshooting guide for this! Cheers, Andrew
  17. Hello! Would it be possible? Yes. Is it a good idea? I think no. The whole point of doing a separate log call per impression is that the call to log the impression happens both immediately after the banner is displayed, and only after the banner is displayed. This way, you get the most accurate view of banners that were actually displayed logged. If you move to logging all banner impressions in one call, you either need to log impressions before everything might have been displayed, and may over-count impressions, or, you log all banner impressions at the end of the page, and may under-count impressions. I think you'd have a job to convince me that doing a single, one call logs all approach is a good idea...
  18. Apologies, DNS got messed up in domain transfer. Fixed now, should propagate out over the next few hours.
  19. Your best bet would probably to get in touch via the website for that product, as it's a 3rd party thing, rather than something the "core" Revive Adserver team look after.
  20. Eliza0406 is not a member of the Revive Adserver team. The Revive Adserver team is very happy to have other people participate in the community -- indeed, we actively encourage everyone to take part! We are also happy if people want to offer paid services (consulting, support, development, plugins or anything else really) around Revive Adserver. However, it should be clear that outside of those people on listed on the Revive Adserver website, anything you may decide to pay for is outside of the Revive Adserver team's control, and is not "official". That's not to say that it may not be any good - it may very well be. However, we will not comment on that kind of thing, and the fact that there is a user on the forums offering to sell you a Revive Adserver database ERD does not constitute an official policy from the team. I hope that clarifies the matter!
  21. We took over the project a year ago. The plugin framework that exists is exactly how we inherited it - we have not worked on it at all in the last year, as there are simply too many other things that we have been trying to do. As soon as we can, we will absolutely document how to write plugins -- but be aware that even then, there will be lots of things people will want to do with plugins that the framework will not support, so it's not like documentation will automatically make everything be possible to be done as a plugin. For now, our focus is on fixing the bugs we can, adding new features where there seems to be the broadest demand (so that we can help out as many users as we possibly can) and writing user documentation first, then admin documentation, and finally developer documentation. For us, that seems to be the best way we can help out the Revive Adserver community.
  22. Hello, No, absolutely not. The Revive Adserver team do not have a policy to hide anything to force people to pay for support. We appreciate that our documentation is incomplete as at the time of this post - use documentation, admin documentation, and developer documentation. Indeed, there is simply no developer documentation for Revive Adserver at all at this point in time. As Revive Adserver is an open source project, with no financial backing, the time that the team spends working on the code, the website, the documentation and the forum is entirely voluntary, and unpaid for. While we have a few ideas for helping to raise money to pay for things like hosting, etc., at the present time, the income that the team gets from the Revive Adserver project is effectively zero. So, we'd love to have lots of developer documentation, and it's certainly on the list. When we get a chance, I am sure we will write some. Until then, we rely on the support of the community to help each other - and us - out, develop code where they can, suggest documentation improvements where they can, keep translation files up to date where they can, and support each other and answer questions on the forums where they can. All of these things will help the team spend the time they can afford to donate to the project focussed on core updates that will benefit everyone. Sincerely, Andrew
  23. I wonder if the image tag might be a better option for you? See some of the details of different tag types at: http://documentation.revive-adserver.com/display/DOCS/Invocation+code
  24. Geotargeting plugins are included by default in Revive Adserver - there's no need to "get" one for this.
  25. It's not because you've defined the targeting channels as a different manager account, or at the website level that isn't relevant to what you're currently looking at?
  • Create New...