The PSDK contacts an ad delivery service, such as Primetime
Ad Serving (Auditude), and attempts to obtain the primary playlist
file corresponding to the video stream for the ad. During the ad-resolving
phase, the PSDK makes an HTTP call to the remote ad-delivery server
and parses the server's response.
The PSDK supports the following types of ad providers:
- Metadata ad provider:
The ad data is encoded in plain-text JSON files.
- Auditude ad provider:
A request is sent to the Auditude back-end server including a set
of targeting parameters and an asset identification number. Auditude
responds with a SMIL document that contains the ad information that
the PSDK requires.
- Custom
ad markers provider: Handles the situation where ads are burned
into the stream, from the server side. The PSDK does not perform the
actual ad insertion, but it needs to keep track of the ads that
were inserted on the server side. This provider sets the ad markers
that are used by the PSDK to perform the ad tracking.
Two failover scenarios can occur during this phase:
- The data cannot be
retrieved for reasons such as lack of connectivity or a server-side
error (resource cannot be found and so on).
- The data was retrieved,
but the format is invalid (that is, the parsing of the inbound data
fails). The PSDK issues a warning notification about the error and
continues processing.
The PSDK issues a warning notification about the error and continues processing.