scalemates got a reaction from Josh in Remove fl.js for better JS performance
All the banners I server are either images or HTML and there is 0% chance I serve flash.
While doing a performance review of my JS code I noted the standard Revive JS code (served via /asyncjs.php) contained a whole section of JS referencing ShockwaveFlash.ShockwaveFlash
Checking the asyncjs.php source I see it includes a reference to a required flash config file (fl.js in the /www/delivery folder)
require __DIR__.'/'.$GLOBALS['_MAX']['CONF']['file']['asyncjsjs']; require __DIR__.'/'.$GLOBALS['_MAX']['CONF']['file']['flash']; I currently commented out the inclusion of the fl.js so the JS is smaller. All seems to work fine.
My 3 questions for the community are?
Do you know any side effects of removing the fl.js inclusion? Are there better options than commenting it out? Are there other JS optimisations you are aware off? Thank you
scalemates got a reaction from andrewatfornax in Statistics by campaign type
I'm interested in overal statistics by campaign type. (eg. Remnant, contract, ...)
I want to see Revenue/Clicks/Impressions for all my contract campaigns without the noise of remnant campaigns.
I want to see the evolution of total remnant impressions compared to all impressions.
Is this possible today?
My own reply:
Sometimes you find the answer yourself the minute after posting the question. All my internal remnant campaigns belong to the same advertiser. As there are plenty of reports available by advertiser it is straight forward getting the info.
scalemates got a reaction from adus in Cookies (new EU legislation)
I was surprised to see there is a new GDPR release giving extra control on the OAID cookie since yesterday evening
Hope this helps. I'll try and to the upgrade this weekend.
scalemates reacted to tobean in Cookies (new EU legislation)
in the future it must be possible to opt out from setting cookies in Revive adserver. In the actual release cookies seem to be set for one year. In the config file I found the option
Is it possible to reduce this time to 1 hour (or for the actual browser session)? Or what is the reason that the cookie lives for 1 year?
Or can I even set permCookieSeconds=0 to get rid of all cookies? I know that some feature will no longer work in this case (e.g. display the same banner more than once).
It would be nice to get an anser from Eric or another admin because Revive will no longer be legal when the new legislation comes on may 25th.