Edge bidding system for online ads
A request for a page is received. The page is provided at least in part by determining dynamically a content element for the page. An auction to determine a winning bid is conducted prior to providing the page in response to the request and the content element determined based at least in part on the auction winner.
1. A system, comprising:
a communication interface configured to:
receive, from a client device, a request for a page;
fetch, from a content management system, the requested page;
provide, to the client device, a modified version of the page; and
a processor coupled to the communication interface and configured to provide the page at least in part by determining dynamically a content element for the page, including by:
conducting an auction in parallel with fetching the requested page, prior to providing the page in response to the request, to determine a winning bid;
determining the content element based at least in part on an auction winner, wherein determining the content element includes comparing the winning bid to a configured threshold;
in response to a determination that the winning bid is greater than the configured threshold, modifying the page to become the modified version of the page by stitching the content element corresponding to the winning bid into the page; and
in response to a determination that the winning bid is not greater than the configured threshold, modifying the page to become the modified version of the page by including data associated with the winning bid, logic to cache the content element corresponding to the winning bid, and code to initialize a pre-auction script, wherein the pre-auction script is used by the client device to render content associated with a final winning bid.
2. The system of claim 1 , wherein the request for the page is received from a browser associated with the client device.
3. The system of claim 1 , wherein the processor comprises an edge server.
4. The system of claim 1 , wherein the processor comprises a content distribution network edge server.
5. The system of claim 1 , wherein the auction is conducted by calling a header bidder server.
6. The system of claim 1 wherein the page is modified to include code to render the content element corresponding to the winning bid.
7. The system of claim 6 , wherein in response to receiving the page, a browser is configured to render the content element corresponding to the winning bid.
8. The system of claim 1 , wherein in response to receiving the page, a browser associated with the client device is configured to call an publisher ad server and load the pre-auction script, in parallel.
9. The system of claim 8 , wherein the browser associated with the client device is configured to cache the content element corresponding to the winning bid.
10. The system of claim 9 , wherein the browser associated with the client device is configured to receive the final winning bid from the publisher ad server.
11. The system of claim 10 , wherein in the event the final winning bid from the publisher ad server is the winning bid from the auction, the browser associated with the client device is configured to initialize the pre-auction script and render the cached content element corresponding to the winning bid.
12. A method, comprising:
receiving, from a client device, a request for a page;
fetching, from a content management system, the requested page; and
providing, to the client device, a modified version of the page at least in part by determining dynamically a first content element and a second content element for the page, including by:
conducting a first auction in parallel with fetching the requested page, prior to providing the page in response to the request, to determine a first winning bid for a first content spot corresponding to the first content element;
determining the first content element based at least in part on a first auction winner, wherein determining the first content element includes comparing the first winning bid to a first configured threshold;
conducting a second auction in parallel with fetching the requested page, prior to providing the page in response to the request, to determine a second winning bid for a second content spot corresponding to the second content element;
determining the second content element based at least in part on a second auction winner, wherein determining the second content element includes comparing the second winning bid to a second configured threshold; and
modifying the page to become the modified version of the page, wherein in response to determining that the first winning bid is greater than the first configured threshold, the page is modified by stitching the first content element corresponding to the first winning bid into the page, wherein in response to determining that the second winning bid is not greater than the second configured threshold, the page is modified by including data associated with the second winning bid, logic to cache the second content element corresponding to the second winning bid, and code to initialize a pre-auction script wherein the pre-auction script is used by the client device to render content associated with a final winning bid.
13. The method of claim 12 , wherein the page is modified to include code to render the first content element corresponding to the first winning bid.
14. The method of claim 12 , wherein the first auction is conducted by calling a header bidder server.
15. A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
receiving from a client device a request for a page;
fetching the requested page; and
providing a modified version of the page at least in part by determining dynamically a first content element and a second content element for the page, including by:
conducting a first auction in parallel with fetching the requested page, prior to providing the page in response to the request, to determine a first winning bid for a first content spot corresponding to the first content element;
determining the first content element based at least in part on a first auction winner, wherein determining the first content element includes comparing the first winning bid to a first configured threshold;
conducting a second auction in parallel with fetching the requested page, prior to providing the page in response to the request, to determine a second winning bid for a second content spot corresponding to the second content element;
determining the second content element based at least in part on a second auction winner, wherein determining the second content element includes comparing the second winning bid to a second configured threshold;
modifying the page to become the modified version of the page, wherein in response to determining that the first winning bid is greater than the first configured threshold, the page is modified by stitching the first content element corresponding to the first winning bid into the page, wherein in response to determining that the second winning bid is not greater than the second configured threshold, the page is modified by including data associated with the second winning bid, logic to cache the second content element corresponding to the second winning bid, and code to initialize a pre-auction script wherein the pre-auction script is used by the client device to render content associated with a final winning bid.