Tim Vereecke

If you want to display 8 banners, you need to have 8 zones

Do you see in dev tools Errors in the Console? Any HTTP requests returning an error?

My priorities for campaigns are between 1 and 10

From https://www.revive-adserver.com/support/requirements/ "Support for the upcoming PHP 8.2 is planned for a future release of Revive Adserver."

Thx for the reply @Matteo Beccati At the CDN level I can have everything on the same domain, and based on paths I can forward to different origins. (which works) My question is basically, is asyncspc.php doing any writes? if no, primary/replica database replication would work. If it does, in that case full replication (primary/primary) is needed.

My site runs highly distributed in 15+ locations around the world. (Primary in Germany, read replicas in X other locations) This results in great performance for the dynamic HTML (80ms from US West coast to regional replica), however all my asyncspc.php request still go to Germany (463ms to Germany) I understand Revive Adserver needs Primary/Primary for full replication to work. I wonder if I can go for a setup which ONLY sends asyncspc.php to many global (read-only) replicas. Any other request which reads/writes (eg. lg.php would go to the primary) Goal: - Make asyncspc.php as fast as possible (any delay here results in ads being shown later) - Ignore the speed of lg.php, when this requests take a bit longer is not really important Does you know if such a setup will work as expected; or will there be hidden "writes" which are triggered by asyncspc.php?

hi Saria, You might have seen it in the mean time, but here is a detailed blog about this topic https://www.revive-adserver.com/blog/how-does-revive-adserver-use-third-party-cookies/

hi Steve, When you test performance of asynchronous make sure to have ALL your zones using the asynchronous method. The reason is: The asynchronous method sends the actual zone invocation request on DOMContentLoaded. However the synchronous version delays this DOMContentLoaded event. This is also true when the async zone is before any sync zone (like seen in your screenshot) For example if on your PRD site you would add a single zone using asynchronous it would for synchronous zones to load which delay the yellow line (=DOMContentLoaded)

I wonder what you want to achieve by changing this?

Unless I misunderstood your question you should still prepend {clickurl} to the actual link. (even with Do not alter HTML) <a href="{clickurl}https://www.targetsite.com/">Shop now</a>

The recording is now available (20mins) https://video.fosdem.org/2024/h2214/fosdem-2024-2266-from-google-adsense-to-foss-lightning-fast-privacy-friendly-banners.mp4

On February 4th 2024 (Noon CET) I will present at FOSDEM 2024; the topic is about how I used Revive Adserver to improve privacy and Web Performance. Maybe I will see you in Brussels? Or if you are interested there is also a live stream Kind regards; Tim From Google AdSense to FOSS: Lightning-fast privacy-friendly banners I run [link removed], the largest and fastest scale modeling website in the world. As such, I need a fast and privacy-aware advertisement solution to best serve my user base. 5 years ago, just before GDPR became applicable I decided to replace my existing Google AdSense solution. While easy to set up, AdSense and other vendors were in hindsight too slow or not meeting my privacy expectations. The cornerstone of the new architecture became the popular, free and open source (GNU GPL) Revive Adserver (formerly known as OpenX). Without leaking information, Revive Adserver allows me to serve targeted ads without degrading Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS) or other Web Vitals. In this talk you will learn about my design choices as well as interesting techniques and best practices to serve and monitor banner ads performance. More info: https://fosdem.org/2024/schedule/event/fosdem-2024-2266-from-google-adsense-to-foss-lightning-fast-privacy-friendly-banners/

Hi Wasif, Here is a link which likely answers your questions: https://www.revive-adserver.com/faq/using-google-adsense-with-revive-adserver/ Kind regards, Tim

With the new Speculation rules API browsers can prerender pages. This can lead to ad impressions being requested and logged without users navigation to the page (and not seeing ads). I think it would make sense to delay the logging to be delayed till after the prerenderingchange event to: Avoid views never seen Avoid reduction of CTR eg. if (document.prerendering) { document.addEventListener("prerenderingchange", doSomething, { once: true, }); } else { doSomething(); } Reference: https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API

Using Async JS should make the rest of the page (without the ads) load faster because rendering is not blocked while the JS snippet dowloads. Are you seeing a delay in your ads? or also a delay of the page contents? And what do you mean with considerable?