Repository navigation
Server-side Ad-templates (SSAT) Phase 1 #638
Description
The browser is the a slow place to run an auction. While its been wildly successful in ease of monetization, it still has limitations. It must first download and parse multiple SDKs, scan the DOM to discover what ad slots exist, and then fire SSP requests over a consumer internet connection with high and variable latency.
Trusted Server sits at the CDN edge, milliseconds from the user, with DC-DC RTT to Prebid Server (~20–30ms vs ~80–150ms from a browser). The server can know, from the request URL alone, exactly which ad slots are available on any given page with pre-configured templates for creative opportunities. There is no reason to wait for the browser outside of just being "the way it was always done."
Activity
[-]Give publishers an option to have server-side ad-templates instead of initializing client-side SDKs to scan the DOM every page load[/-][+]Server-side ad-templates in lieu of initializing client-side SDKs to scan the DOM every page load[/+][-]Server-side ad-templates in lieu of initializing client-side SDKs to scan the DOM every page load[/-][+]Server-side Ad-templates (SSAT) Phase 1[/+]