LIVE AD PROCESSING ENGINE SERVICE
Techniques described herein provide for a live advertising processing engine service to act as an intermediary between client applications and advertising networks. The live advertising processing engine service can provide an interface with which the client can interact, via an application programming interface (API) or directly through the use of a standardized language, thereby allowing client applications to receive advertisement data without the need to be customized to communicate with specific advertising networks. The live advertising processing engine service can further track where, in playback the live content, a client currently is, to indicate to the client—or other application—when advertisement breaks are and/or provide supplemental advertisement information to enable the client to provide a rich user experience.
1 . (canceled)
2 . A method comprising:
receiving, by an application executing on a user device, a first manifest file from at least one of a plurality of servers associated with a content provider, wherein the first manifest file comprises:
a list of a plurality of segments corresponding to media content; and
a first ad break marker indicating a first ad insertion opportunity in the list of the plurality of segments corresponding to the media content;
playing, by the application, a first subset of the plurality of segments corresponding to the media content using data from the first manifest file;
during the playing of the first subset of the plurality of segments corresponding to the media content, transmitting, by the application, a first request to at least one of the plurality of servers for a second manifest file associated with at least one first advertisement, wherein the first request is transmitted based at least in part on a position of the first ad break marker in the list of the plurality of segments corresponding to the media content;
receiving, by the application, the second manifest file from at least one of the plurality of servers, wherein the second manifest file comprises a list of plurality of segments corresponding to the at least one first advertisement;
playing, by the application, the plurality of segments corresponding to the at least one first advertisement using data from the second manifest file; and
after conclusion of the playing the plurality of segments corresponding to the at least one first advertisement, playing, by the application, a second subset the plurality of segments corresponding to the media content using the data from the first manifest file.
3 . The method of claim 2 , further comprising:
receiving an identification of a second ad break marker indicating a second ad insertion opportunity;
transmitting, while playing another segment of the plurality of segments corresponding to the media content and before reaching the second ad break marker, a second request to one of the plurality of servers; and
receiving, based at least in part on transmitting the second request to the one of the plurality of servers, a third manifest file comprising a list of a plurality of segments corresponding to at least one second advertisement for display at the second ad insertion opportunity, wherein the third manifest file is dynamically generated based at least in part on information associated with the user device.
4 . The method of claim 3 , further comprising:
generating a play session token for consumption of the media content; and
wherein a generation of the second manifest file comprising the plurality of segments corresponding to the at least one first advertisement and the generation of the third manifest file comprising the plurality of segments corresponding to the at least one second advertisement are coordinated based on the play session token.
5 . The method of claim 2 , further comprising:
configuring a tracking beacon for monitoring playback parameters of the media content; and
transmitting data gathered by the tracking beacon to at least one server of the plurality of servers.
6 . The method of claim 2 , wherein the second manifest file is dynamically generated based at least in part on client state metadata.
7 . The method of claim 2 , wherein the second manifest file comprises one or more instructions for predetermined behaviors to be implemented on the user device while playing the plurality of segments of the at least one first advertisement, the predetermined behaviors comprising at least one of:
displaying an interstitial banner, displaying an overlay advertisement, blocking fast-forward controls, enabling interactive content, or providing a tracking beacon.
8 . The method of claim 2 , wherein the second manifest file is generated based on stored rules and identifying information associated with a client device.
9 . The method of claim 8 , wherein the identifying information comprises geographical data associated with the user device.
10 . The method of claim 2 , further comprising:
transmitting a request for a list of one or more additional segments of the media content generated at one of the plurality of servers;
receiving data for updating the first manifest file, wherein the updated first manifest file comprises the list of one or more additional segments.
11 . The method of claim 2 , wherein the second manifest file comprises one or more tracking URLs for monitoring at least one of:
playing performance of the at least one first advertisement, advertisement impressions, or user interactions with the at least one first advertisement.
12 . A system comprising:
input/output circuitry configured to:
receive, by an application executing on a user device, a first manifest file from at least one of a plurality of servers associated with a content provider, wherein the first manifest file comprises:
a list of a plurality of segments corresponding to media content; and
a first ad break marker indicating a first ad insertion opportunity in the list of the plurality of segments corresponding to the media content;
control circuitry configured to:
play, by the application, a first subset of the plurality of segments corresponding to the media content using data from the first manifest file; and
wherein the input/output circuitry is further configured to:
during the playing of the first subset of the plurality of segments corresponding to the media content, transmit, by the application, a first request to at least one of the plurality of servers for a second manifest file associated with at least one first advertisement, wherein the first request is transmitted based at least in part on a position of the first ad break marker in the list of the plurality of segments corresponding to the media content;
receive, by the application, the second manifest file from at least one of the plurality of servers, wherein the second manifest file comprises a list of plurality of segments corresponding to the at least one first advertisement; and
wherein the control circuitry is further configured to:
play, by the application, the plurality of segments corresponding to the at least one first advertisement using data from the second manifest file; and
after conclusion of the playing the plurality of segments corresponding to the at least one first advertisement, play, by the application, a second subset the plurality of segments corresponding to the media content using the data from the first manifest file.
13 . The system of claim 12 , wherein the input/output circuitry is further configured to:
receiving an identification of a second ad break marker indicating a second ad insertion opportunity;
transmit, while playing another segment of the plurality of segments corresponding to the media content and before reaching the second ad break marker, a second request to one of the plurality of servers; and
receive, based at least in part on transmitting the second request to the one of the plurality of servers, a third manifest file comprising a list of a plurality of segments corresponding to at least one second advertisement for display at the second ad insertion opportunity, wherein the third manifest file is dynamically generated based at least in part on information associated with the user device.
14 . The system of claim 13 , wherein the control circuitry is further configured to:
generate a play session token for consumption of the media content; and
wherein a generation of the second manifest file comprising the plurality of segments corresponding to the at least one first advertisement and the generation of the third manifest file comprising the plurality of segments corresponding to the at least one second advertisement are coordinated based on the play session token.
15 . The system of claim 12 , wherein:
the control circuitry is further configured to:
configuring a tracking beacon for monitoring playback parameters of the media content; and
the input/output circuitry is further configured to:
transmitting data gathered by the tracking beacon to at least one server of the plurality of servers.
16 . The system of claim 12 , wherein the control circuitry is configured to dynamically generate the second manifest file based at least in part on client state metadata.
17 . The system of claim 12 , wherein the second manifest file comprises one or more instructions for predetermined behaviors to be implemented on the user device while playing the plurality of segments of the at least one first advertisement, the predetermined behaviors comprising at least one of:
displaying an interstitial banner, displaying an overlay advertisement, blocking fast-forward controls, enabling interactive content, or providing a tracking beacon.
18 . The system of claim 12 , the control circuitry is configured to generate the second manifest file based on stored rules and identifying information associated with a client device.
19 . The system of claim 18 , wherein the identifying information comprises geographical data associated with the user device.
20 . The system of claim 12 , wherein the input/output circuitry is further configured to:
transmitting a request for a list of one or more additional segments of the media content generated at one of the plurality of servers;
receiving data for updating the first manifest file, wherein the updated first manifest file comprises the list of one or more additional segments.
21 . The system of claim 12 , wherein the second manifest file comprising one or more tracking URLs for monitoring at least one of:
playing performance of the at least one first advertisement, advertisement impressions, or user interactions with the at least one first advertisement.