Jump to content

gabrielt

Approved members
  • Content Count

    64
  • Joined

  • Last visited


Reputation Activity

  1. Upvote
    gabrielt got a reaction from Dofini in How To Serve Responsive Ads?   
    Fixed sizes have to do the way the web traditionally works. You have to keep in mind that "responsive" is a somewhat new concept. The web is about 20 years old and we've only seen responsive layouts in the past 2-3 years.
    That said, it would be great to have a built-in mechanism to detect the maximum width supported and display a banner that fits that space.
    For example, today we can setup a campaign with, say, two banner sizes, 728x90 and 300x250, at the same time. Revive will display the 728x90 banner when this campaign is assigned to a 728x90 zone, and will display the 300x250 banner when this campaign is assigned to a 300x250 zone.
    One step further would be the Revive tag to detect the width, and this particular zone would display (for example) the 728x90 banner when the resolution is high enough and the 300x250 banner at lower resolutions.
    Currently, there are a few known workarounds to that. You can define zones without a width and height (it is possible, just enter * x *), in this case, both banners (728x90 and 300x250) will be displayed at the zone. Then you can set up banner limitation to display the 300x250 for mobile browsers and the 728x90 banner for non-mobile browsers.
    I hope I have helped.
  2. Upvote
    gabrielt got a reaction from andrewatfornax in Stats mismatch and weird behavior - 10/2017   
    @andrewatfornax Yep, it was a zone configuration error, as the banners were linked to the wrong zones. Therefore, no need for this topic, as it was my mistake, and you can delete it. Thanks.
  3. Upvote
    gabrielt got a reaction from andrewatfornax in Stats mismatch and weird behavior - 10/2017   
    Update: I think I found the culprit: It was a zone linking issue. I had the campaigns linked to certain zones but the banners linked to different zones... It seems this mismatch caused the issue when Revive tried to obey both configurations. I will have a definitive answer after lettting it run for a couple of days, but I am pretty confident that this was the issue indeed.
  4. Upvote
    gabrielt got a reaction from mibert in Issue upgrading from 4.0.2 to 4.1.0   
    @Matteo Beccati Just to confirm that the new 4.1.1 version solved the issue. Many thanks for fixing this promptly. PS: on the downloads page, the link to the 4.1.1 tar.gz version is pointing to the 4.1.0 version.
    I am not facing the issue mentioned by @Richard Cook above. For me opening /www/admin/updates-product.php shows:
    You are currently using Revive Adserver v4.1.1 running on nginx 1.12.1, PHP 7.1.11 and MySQL 5.6.37-82.2-log.
    Cheers.
  5. Like
    gabrielt reacted to Matteo Beccati in Issue upgrading from 4.0.2 to 4.1.0   
    Hello everyone!
    Chances are that we won't be able to release a 4.1.1 final next week, but in the meantime it would be great if you could test on your staging environment this pre-release package that should fix the upgrade problems that you reported (along with the actual upgrade from phpAdsNew itself, which was broken since 3.2).
    You can download the beta packages here:
    revive-adserver-4.1.1-beta.tar.bz2 (sha256: bf515eb36f6fc00fef0ee919e9ff50e612e31b5e54d10dff7f3726db8f7d6653) revive-adserver-4.1.1-beta.tar.gz (sha256: 4315a107d5459492994c7097268ed2f10b91b0bcaf5498ff18e557f126eb81a9) revive-adserver-4.1.1-beta.zip (sha256: 4111dc824175b98833c516e57a188951d34337d93fc171ca51101329955e47b5)
  6. Like
    gabrielt reacted to Matteo Beccati in Issue upgrading from 4.0.2 to 4.1.0   
    For reference, I've created the issue on github: https://github.com/revive-adserver/revive-adserver/issues/900
  7. Like
    gabrielt reacted to Matteo Beccati in Issue upgrading from 4.0.2 to 4.1.0   
    @mibert Thanks, that should be enough. That makes two of you having the issue using a database that was originally created during the phpAdsNew era.
    I'd suggest to keep using 4.0.2 until a fix or workaround is found.
  8. Upvote
    gabrielt got a reaction from andrewatfornax in Responsive Advert View   
    Please take a look at this other topic where this is discussed
     
    http://forum.revive-adserver.com/topic/27-how-to-serve-responsive-ads/
  9. Upvote
    gabrielt got a reaction from andrewatfornax in Advanced Configuration (Return To Revive From Rtb Network)   
    Thanks! I solved this problem last week... I was not aware that we could generate a tag for a specific zone. That is exactly what I did: I created a zone that was not posted on my website, put the banners there, and generated the tag for this zone and used it at the end of the RTB stack. It is working like a charm. Thank you very much.
  10. Upvote
    gabrielt got a reaction from xtech in How To Serve Responsive Ads?   
    Fixed sizes have to do the way the web traditionally works. You have to keep in mind that "responsive" is a somewhat new concept. The web is about 20 years old and we've only seen responsive layouts in the past 2-3 years.
    That said, it would be great to have a built-in mechanism to detect the maximum width supported and display a banner that fits that space.
    For example, today we can setup a campaign with, say, two banner sizes, 728x90 and 300x250, at the same time. Revive will display the 728x90 banner when this campaign is assigned to a 728x90 zone, and will display the 300x250 banner when this campaign is assigned to a 300x250 zone.
    One step further would be the Revive tag to detect the width, and this particular zone would display (for example) the 728x90 banner when the resolution is high enough and the 300x250 banner at lower resolutions.
    Currently, there are a few known workarounds to that. You can define zones without a width and height (it is possible, just enter * x *), in this case, both banners (728x90 and 300x250) will be displayed at the zone. Then you can set up banner limitation to display the 300x250 for mobile browsers and the 728x90 banner for non-mobile browsers.
    I hope I have helped.
  11. Upvote
    gabrielt got a reaction from umarizal in How To Serve Responsive Ads?   
    Wondering on how to work that out with the new async invocation code...
     
    I played with height: 0px and display: hidden. These tricks work but I am afraid of using them as I am using banners from networks such as Google AdSense, and they might complain that we are rendering banners in a hidden <div>.
     
    I saw somewhere that we might add a data-field that would "activate" the correct code depending on the resolution, so the banner that won't be displayed won't be rendered/loaded. Still researching:
     
    http://christianheilmann.com/2012/12/19/conditional-loading-of-resources-with-mediaqueries/
     
    Please take a look under "Matchmedia to the rescue". I played with it but couldn't get it to work. I don't know where and how to "trigger" the JavaScript code. I'd appreciate any help.
  12. Upvote
    gabrielt got a reaction from andrewatfornax in Asynchronous Loading   
    That would involve hacking our CMS, and I don't have the time to play with this at the moment. But thanks for the suggestion, though.
  13. Upvote
    gabrielt got a reaction from Richard Foley in Issue With Delivering The Amount Contracted   
    andrewatfornax,
     
    I just came by to say that with the most recent version of Revive (3.1.0), this issue has been completely resolved. Thank you very much for addressing this very important issue. Here are some sample values:
     
    Amount Configured - Amount Delivered
    130.000 - 129.853 505.000 - 504.215 170.000 - 169.610 135.000 - 134.619 135.000 - 134.994   Thank you very much for your outstanding work. Please let me know if there is any way we can donate money to you project.   Gabriel.
  14. Upvote
    gabrielt reacted to andrewatfornax in Asynchronous Loading   
    Thanks so much for the feedback gabrielt! It's great to see your graph above showing that you've probably taken 30-60% off of your page load time by moving to the asynchronous tag type, which is obviously a super result, and very encouraging to see that in principle, it does what its supposed to do!
     
    However, the drop off in banner impressions is of course, worrying.
     
    What does pop into my head though, as an immediate thought is that after the move, the page load time has come down to around 5 seconds. However, that is, I assume, the load time for the page without ads, as the ads will then start to load up after the page is done. Assuming nothing else has changed performance-wise, I would guess this means that the ads are then taking something like another 5 to 10 seconds to complete loading up?
     
    If that's the case, there's now a 5 to 10 second window for your site users to move on to another page, and interrupt the loading (and therefore impression logging) of the ads.
     
    How does your average time on page look? Might this kind of behaviour explain the drop off in impressions?
     
    I think this is worth looking into - although of course, we're totally open to the fact that perhaps it's something in the tag that isn't working as we expect re: logging impressions...
  15. Upvote
    gabrielt reacted to andrewatfornax in Async Loading   
    Noted, and now delivered in Revive Adserver 3.2.0.
  16. Upvote
    gabrielt reacted to goldsky in How To Serve Responsive Ads?   
    Maybe it's not too late, I just want to share my trick.
    Just put the invocation code in an element, and modify the width/height on parsing.
    <div id="some-id"> <script type='text/javascript'> // invocation code here </script><noscript><!-- bla bla --></noscript> </div> <script> $(document).ready(function () { var img = $('#some-id').find('img'); if (typeof (img) !== 'undefined' && img.length > 0) { $(img) .removeAttr('width') .removeAttr('height') .addClass('img-responsive'); // eg: twitter bootstrap } }); </script> On this case, I didn't care about the downloading size, but only how it's being presented.
    Still, the original width + height should exactly match with the zone's size.
  17. Upvote
    gabrielt reacted to Ilya Ber in How To Serve Responsive Ads?   
    Determine the current browser resolution and load an appropriate zone based on that using JS. 
     
    Even easier, if you are using single call invocation, you can just pre-populate the Zone ID list  - here is a good example. 
  18. Upvote
    gabrielt reacted to andrewatfornax in Asynchronous Loading   
    And indeed, Revive Adserver 3.2.0 has now been released, which includes native asynchronous tag support.
  19. Upvote
    gabrielt got a reaction from andrewatfornax in Contract Campaigns Severely Under-Delivered   
    Hi,
     
    I am discussing this on another thread, FYI: http://forum.revive-adserver.com/topic/937-issue-with-delivering-the-amount-contracted/
  20. Upvote
    gabrielt got a reaction from andrewatfornax in Issue With Delivering The Amount Contracted   
    That is a good question.
     
    I will try to clean-up the database, deleting old advertisers and campaigns, and see if this gets better. Wait for a new contact by the beginning of June.
     
    Thanks.
  21. Upvote
    gabrielt got a reaction from andrewatfornax in How To Stop Receiving Emails?   
    Thanks a lot! Worked like a charm!
×
×
  • Create New...