Adobe Primetime Manifest Server API for Ad Insertion

Transcription

1 Adobe Primetime Manifest Server API for Ad Insertion

2 Contents Manifest Server API for Ad Insertion...3 Overview of manifest server interactions...3 Send a command to the manifest server...4 Manifest server query parameters...5 Requests for ad insertion...8 Optional query parameters by client and situation...9 Facilitating HLS player switching to failover/backup streams...10 Multiple bit rate streams...11 Partial Ad Break Insertion...11 Multiple CDN support for CRS ad delivery...12 Replacing VOD timelines...12 VOD timeline format...12 Replace a VOD timeline...13 Ad tracking...14 Enable client-side ad tracking...14 Overview of non-tvsdk client-side tracking...14 API for players to interact with the manifest server...17 EXT-X-MARKER Directive...18 Cookies...22 Support for WebVTT captions...22 File formats...22 JSON format for URL for requesting variant manifest playlist...23 JSON formats for tracking URLs...23 VMAP format for tracking URLs...34 Video player requirements...40 Last updated 4/18/2018 Manifest Server API for Ad Insertion

3 3 Manifest Server API for Ad Insertion Overview of manifest server interactions The manifest server coordinates the systems that provide content, provide ads, play video, and track ads. It receives M3U8-encoded playlists (manifests) that client video players receive from content providers, stitches ads from ad providers into the manifests, and passes the stitched manifests to video players. It supports both client-side and server-side ad tracking. It conducts its interactions using an HTTP-based web service interface. A typical configuration contains: The Primetime manifest server The Primetime Creative Repackaging Service (CRS) A client, controlling a video player A publisher, usually with a Content Management System (CMS) A Content Delivery Network (CDN) An ad server A receiver for ad tracking reports The workflow varies based on a number of factors, such as if the CDN is Akamai, or if the client is performing ad tracking. For a diagram of the workflow for client-side ad tracking, see Client-side tracking workflow. The manifest server interacts with video-delivery clients by receiving and responding to HTTP GET requests. The responses are M3U8-encoded manifests describing ad-stitched content, optionally including a JSON or VMAP structure (sidecar) containing detailed ad-tracking instructions (see File formats). A typical workflow looks like the following: 1. The publisher sends the content URL and information for the ad server to the client. 2. The client uses the information from the publisher to generate a manifest server URL and sends a GET request to that URL. This is known as the. 3. The manifest server establishes a session with the client. 4. The manifest server obtains content manifests from the CDN, which may include ad break information. 5. The manifest server redirects the client to the master/variant manifest it generated for the client. Note: If the query parameters contains the pttrackingmode=simple or ptplayer=ios-mobileweb setting, the manifest server returns the master/variant manifest URL in a JSON object, and the client sends a GET request to that variant manifest URL. 6. The client chooses a stream in the generated variant manifest to play, sending ad information to the manifest server. 7. The manifest server passes the client-supplied information to the ad server and receives ads and ad-tracking URLs from the ad server. If a supplied ad is not in HLS format, the manifest server sends it to CRS for conversion to HLS. 8. The manifest server stitches ads into the content manifest and sends the new stitched manifest to the client. 9. The client plays the content with the stitched-in ads and makes requests at the specified times to the specified tracking URLs. Primetime ad insertion supports clients on many video-delivery platforms. Not all clients are built on the Primetime TVSDK package, but all clients send GET requests to the same basic URL. Query parameters distinguish one client request from another by telling the manifest server: which client is making the request,

4 4 what that client wants, and what ad-tracking information to provide. CORS The manifest server uses the Cross-Origin Resource Sharing standard (CORS). It looks for an Origin header in the requests it receives. If the header is present, it replies with Access-Control-Allow-Origin: string from the Origin header Access-Control-Allow-Credentials: true Access-Control-Allow-Methods: GET If not, it replies with: Access-Control-Allow-Origin: * Access-Control-Allow-Methods: GET Send a command to the manifest server Use the HTTP GET command to interact with the manifest server. Send an HTTP GET request for a bootstrap URL constructed using the following pattern: {PublisherAssetID}/{Content URL (base64)}.m3u8?{query parameters} PublisherAssetID Content URL Query parameters Required. Publisher's unique ID for the specific content. Required. URL of the content M3U8 file, Base64 encoded to be safe within the manifest server URL. The content URL must point to a variant M3U8 file, even if there is only one bit rate stream. Some are required, some optional. These constitute the most varied part of the request. They tell the manifest server which sort of client is making the request and what it wants the manifest server to do. For example: {publisherassetid}/{content URL (base64)}.m3u8? u={asset ID}&z={zone}&_sid_=0&pttrackingmode=simple &pttrackingversion=v2&live=false HTTP vs. HTTPS requests The manifest server creates URLs using the same HTTP protocol of the client's request. If a player makes a non-secure HTTP (http) request, the manifest server returns manifest URLs and Auditude tracking URLs with the http protocol. If a player makes a secure HTTP (https) connection, manifest server, it returns manifest URLs and Auditude tracking URLs with the https protocol. Note: The manifest server cannot change the protocol (HTTP or HTTPS) of content segments (.ts) and 3rd-party tracking beacons.you must contact the content and 3rd-party ad providers to have them configure the desired protocols.

5 5 Manifest server query parameters Query parameters tell the manifest server what sort of client sent the request and what that client wants the manifest server to do. Some are required and some have specific acceptable formats or values. The complete URL consists of the base URL followed by a question mark, then parametername=value arguments, separated by ampersands: Base URL?name1=value1&name2=value2&...&namen=valuen Recognized parameters The manifest server recognizes the following parameters. It processes them or passes them, along with all unrecognized parameters, to the ad server. Key sid g k u z enablec3 live pabimode Description Unique ID that the manifest server uses to generate the session ID. Client device type Keywords for custom ad targeting Primetime ad insertion Asset ID. Primetime ad insertion Zone ID for the asset. The client is in a C3 window. If true, replace only local avails; otherwise, replace all avails. Indicates whether the content is a Live or VOD (video on-demand) stream. Enable Partial ad break insertion support Enable if true or start Disable if false Required Yes When targeting rules depend on device type No Yes Yes No Akamai Ad Scaler or ios Safari client No (default is disabled) Valid Values Alphanumeric See list at Client Types (requires Zendesk access) URL-safe string in format key1=value1;key2=value2;... MD5 Hash value Integer Boolean Boolean start, true, or false ptadwindow Duration (seconds) of ad stitching window: how far back to look for ads when a DVR user joins the stream. No (default = 1800) 0 to 1800

6 6 Key ptassetid ptcdn ptcueformat ptfailover ptmulticall Description Unique ID of the content that is assigned and maintained by publisher. List of one or more CDNs to host transcoded assets. See Multiple CDN Support. The name of the custom ad cue format present in the M3U8. Required Akamai Ad Scaler No (default=akamai) No Signals the manifest No server to identify primary and failover streams specified in the master playlist, and to treat them as disjoint sets. This facilitates failover and prevents timing errors. (For Apple HLS devices only.) See facilitating HLS player switching. If set to true, multiple Auditude ad-calls for FER made; one for each ad-break. If absent or set to false, one ad-call is made to auditude for FER. No Valid Values URL-safe string Example: Akamai, Level3, Limelight, Comcast DPISimple, DPIScte35, Elemental,NBC, NFL, or Turner true Boolean Note: The following requirements: ptcueformat parameter must be set to nbc pttimeline parameter is ignored. ptplayer ptrendition pttagds pttimeline Player making the request. Auto-generated by ad insertion and used by Akamai. Do not add or remove. Enable #EXT-X- DISCONTINUITY- SEQUENCE tags (see HLS Draft Spec 19) A string containing the desired timeline for ad placement and content, ios/safari Akamai Ad Scaler No No ios-mobileweb true - manifest server includes a sequence tag before the content in each m3u8 file it sends; if parameter is not present or not true, manifest server does not include a sequence tag. VOD timeline (see VOD timeline format)

7 7 Key pttoken Description which overrides ad breaks in the content stream. Enable TS segment authorization tokens Note: Only Akamai CDN tokens supported Required For TS segment authorization tokens Valid Values Boolean pttrackingmode Enable ad tracking; either custom client-side (simple), server-side (sstm), or hybrid (simplesstm). No simple, sstm, or simplesstm Note: If this parameter is not included, the #EX-X-MARKER is injected into the manifest. See EXT-X-MARKER Directive. pttrackingposition Instructs the manifest server to return ad tracking information only. Do not specify this parameter in the bootstrap request. Client-side Tracking Alphanumeric Note: The manifest server ignores all passed values. However, if you pass a null or empty string, the manifest server returns the M3U8 instead of tracking information. pttrackingversion sctetracking The format version of the client-side tracking information. Fetch M3U8, before SCTE tracking information can be fetched in JSON V2 sidecar. This parameter indicates to the manifest server that the player fetching the M3U8 needs SCTE tag information to be retrieved. Client-side Tracking No (default: false) v1, v2, v3, or vmap true or false Note: The SCTE-35 data is returned in the JSON sidecar with the following combination of query parameter values: ptcueformat=turner elemental nfl DPIScte35 pttrackingversion=v2 sctetracking=true

8 8 Key Description Required Valid Values vetargetmultiplier The number of segments from the live point No (default: 3.0) Float The pre-roll offset is configured using: (vetargetmultiplier * targetduration) + vebufferlength Note: Live/Linear only vebufferlength The number of seconds from the live point No (default: 3.0) Float Note: Live/Linear only Requests for ad insertion All requests for ad insertion use the same URL structure and the same basic query parameters. Additional query parameters enable the manifest server to work with a variety of clients and situations. Parameter u Description The asset ID is an MD5 hash of the ad_request_id from the Adobe Primetime ad decisioning metadata. Provided by your Adobe Technical Account Manager. z The zone id for the asset that needs to be provided to Auditude. Provided by your Adobe Technical Account Manager. sid A unique id that the manifest server will use to generate the session id. Note: The sid parameter is surrounded by double underscore characters. The manifest server maintains sessions for individual clients or groups of clients to ensure that the sequences of API interactions for different clients stay separate. The sid that the client sends in the bootstrap URL to the manifest server should be unique within its environment. The manifest server uses it to construct a globally unique ID, which it returns to the client.

9 9 The remaining query parameters pertain to different clients and situations. Optional query parameters by client and situation Beyond the basic query parameters, optional query parameters enable the manifest server to work with different clients and situations. Ad insertion with Akamai Ad Scaler On the Akamai content delivery network (CDN), the Akamai Edge server works as an intermediary between the client and the manifest server. If you also use Ad Scaler, the ptassetid and live query parameters provide required information to Akamai Edge. The ptassetid parameter is the publisher's ID for its asset. Akamai uses this, rather than the base64-encoded URL that you supply as part of the request URL, to identify the playlist to provide to the manifest server for ad insertion. The live parameter distinguishes between live content and video on demand (VOD). The manifest server needs this information to support its streamlined interface with Akamai. Here is a sample URL showing the parameters that pertain to Akamai: Ad insertion from TVSDK on Xbox A player based on Primetime TVSDK on Xbox need not supply additional query parameters beyond the basic ones. Ad insertion from TVSDK on ios with Safari A player based on Primetime TVSDK on ios using the Safari browser must specify the ptplayer and live parameters in addition to the basic query parameters. The manifest server recognizes the ptplayer value ios-mobileweb and eliminates the pre-roll from the ad-stitched manifest it returns. The live parameter tells the manifest server whether to return live or VOD content. Here is a sample URL showing the parameters that pertain to ios with Safari: Ad insertion using a custom ad cue format Adobe provides names for ad cue formats that it does not support directly in the Primetime package. To use such a format, supply its Adobe-provided name as the value of the ptcueformat parameter. Here is a sample URL specifying a custom ad cue format: format name] Ad insertion using ad cues to create a FreeWheel timeline for VOD For VOD content containing ad cues to be parsed and included in a FreeWheel ad request, set the value of the ptcueformat parameter to DPIsimple. Here is a sample URL that specifies using a FreeWheel timeline for VOD:

10 10 Ad insertion using a custom timeline for VOD To ask the manifest server to insert ads into VOD content according to a timeline you supply, set the value of the pttimeline parameter to a string specifying the timeline. See VOD timeline format. Here is a sample URL that uses a custom timeline for VOD: It specifies an initial break of one minute containing up to two ads, followed by a two-minute content segment, followed by a 30-second break containing up to two ads, followed by a five-minute content segment. Ad stitching for a custom content timeline for VOD content behaves as follows: The ad appears at the closest break boundary after the ad placement time specified by the ad server. Segments are at least two seconds long. Authorizing TS segments Adobe supports this feature only for the Akamai CDN. HTTP live streaming (HLS) delivers transport stream (TS) segments using a stream-level M3U8 playlist. Multiple stream-level playlists are provided to the client in a variant M3U8 playlist. The client picks one playlist stream from the variant list, then downloads TS segments in that stream-level playlist one-by-one. In normal operation, the requested content can require cookie authorization, which the manifest server handles invisibly in the background. It extracts the cookie from the raw content and appends an appropriate token to the URL to be used in requesting the selected playlist stream. When the query parameters include pttoken=true, the publisher requires a cookie to be used in requesting each TS segment, rather than just once for the whole stream. The manifest server attaches this cookie as a query parameter to each TS segment URL in the stream playlist it sends back. Facilitating HLS player switching to failover/backup streams Apple HLS stack supports switching to failover/backup streams if it cannot retrieve any streams of the primary set. For Apple HLS devices, to facilitate failover, you can signal manifest server to treat primary and failover streams identified in the master playlist as disjoined sets (with their own UUIDs). To facilitate switching to failover or backup streams on Apple HLS devices, you can specify the ptfailover parameter in the. If you provide this parameter, manifest server will create separate playback sessions (which determine the ads stitched) for each failover set. Details: How SSAI Handles HLS switching to failover/backup when you include ptfailover=true in the request: When a master playlist contains primary and backup sets: The manifest server identifies AV stream URLs for different failover sets using the BANDWIDTH attribute and the parse order of AV stream URLs. It creates separate internal playback sessions (identified by separate UUIDs), and creates stream URLs pointing to manifest servers with the different UUIDs identifying different playback sessions. The manifest server identifies I-Frame stream URLs for different failover sets using the matching RESOLUTION attribute and the parse order of I-Frame stream URLs. SSAI uses the UUIDs identifying the associated AV streams for I-Frame stream URLs pointing to SSAI. For this feature, the manifest server only supports EXT-X-MEDIA groups without URI attributes in the master playlist. The manifest server detects a 404 error response from a CDN with an X-Object-Too-Old: true header, and preserves the status code and the header when sending that response to the player.

11 11 Pre-roll ads are only added to the primary set; they are completely disabled in the failover sets to avoid any erroneous and/or duplicated pre-roll ads when the player switches to failover streams. Multiple bit rate streams Client requests for ad insertion typically specify more than one bit rate in the variant M3U8-formatted playlist. The manifest server generates and returns a new variant M3U8 file containing a separate M3U8 link for each bit rate. It also generates a unique group ID to tie these M3U8s together. The manifest server uses the information in the client's request to retrieve the content variant playlist. It generates a new variant playlist containing manifest server links to the stream-level content. The client uses these to construct ad insertion requests. The manifest server's stream-level content links have the following format: {groupid}/{base64-encoded url of the bit rate stream}.[m3u8]?{query parameters} live/vod publisherassetid rendition groupid base64-encoded url of the bit rate stream Query parameters The manifest server sets this value based on the content's playlist type: Live/linear (#EXT-X-PLAYLIST-TYPE:EVENT) or VOD (#EXT-X-PLAYLIST-TYPE:VOD) Publisher's unique ID for the specific content provided in the request. The manifest server sets this based on the BANDWIDTH value of the content stream, and uses it to match the bit rate of the ad to the bit rate of the content. The ad bit rate cannot exceed the bit rate of the content unless the ad rendition with the lowest bit rate does so. The manifest server generates this value and uses it to ensure that it places ads consistently, no matter for which bit rate renditions the client requests ads. The manifest server URL-safe base64 encodes the content stream's absolute URL. Each stream has its own URL. Query parameters provided in the request. Partial Ad Break Insertion The Partial Ad Break Insertion (PABI) feature mimics a TV like experience in which if the user joins a live stream inside a mid-roll break, the user is shown mid-roll ads instead of a pre-roll ad or slate. When the ad server returns pre-roll ads for a live stream, the manifest server will inject the pre-roll ad break before the live-point and insert the EXT-X-START tag with its TIMEOFFSET value pointing to the start of the pre-roll ad break. This default behavior ensures the entire pre-roll ad break is played before the content at the live-point. If a user joins a stream when the live-point is near a mid-roll ad break, the user will be shown the pre-roll ad break before the mid-roll ad break at the live-point. The PABI feature instructs the manifest server ignore the pre-roll ad break and set the EXT-X-START:TIMEOFFSET value to the beginning of the mid-roll ad present at live-point. This ensures the user sees the entire mid-roll ad currently playing at the live-point without having to view the pre-roll ad break. Note: This functionality is only available for live streams. The manifest server inserts the pre-roll ad break atop the VOD playlist by default. Note: To enable PABI, you will need to specify the parameter in the bootstrap URL. Note: The EXT-X-START is a standard HLS tag that indicates a preferred starting point within the playlist.

12 12 Recommendations Use client-side tracking because the client has more control over the firing of tracking beacons. Partial ad breaks should only be used with server-side tracking mode if the player supports EXT-X-START. Multiple CDN support for CRS ad delivery While the default creative repackaging service (CRS) scenario is to use one Content Delivery Network (CDN), you can deploy CRS assets on more than one CDN. You can use multiple CDNs for the following reasons: A requirement to scale up for large viewing events. A requirement to match the CDN source of the CRS asset with the CDN source of the main content. A requirement to use a different CDN from the CRS default CDN (Akamai). When the manifest server makes a look-up for transcoded requests, it uses a bootstrap URL that contains a number of query parameters. If you have set up a multi-cdn environment, the bootstrap URL will also need to contain the ptcdn parameter. The manifest server uses this parameter to identify the CDN server from which to get the transcoded version of the ad. For more details, see Multi CDN Support in the CRS documentation. Replacing VOD timelines The ad timeline appropriate to one playing of VOD content may be inappropriate for subsequent plays. You can replace a VOD timeline without changing the content. Situations in which you might wish to replace a VOD timeline include: Replace local ads, but leave national ads during a C3 window. Replace burnt-in ads after the C3 window closes. Dynamically replace old C3 ads with newer ads of greater duration. Insert fewer ads or none at all. You can replace the ad timeline by submitting a new ad insertion request with the original M3U8 file and a different value of the pttimeline query parameter. VOD timeline format You can specify or override timelines for ad breaks in VOD content using a formatted list of ad and content segments called pods. Pods A pod is an ad break or a content segment. A timeline consists of a sequence of pods, separated by semicolons. The following types of pods exist:

13 13 Ad break B,duration,maximum_number_of_ads,position Duration is in seconds, with precision of.001 (milliseconds); number of ads is an integer. Position is one of the following: n p m t None no ad Pre-roll before the content Mid-roll within the content Post-roll after the content For example, B,60,2,p represents a one-minute break for up to 2 ads before the content. Content segment (chapter) C,duration,number_of_lots Duration is in seconds, with precision of.001 (milliseconds); number of lots (sections of content) is an integer. For example, C,300,1 represents a single five-minute section of content. Replace a VOD timeline Replace a VOD timeline by sending a new ad insertion request to the manifest server with an appropriately set pttimeline query parameter. 1. Prepare an ad insertion request in the usual manner. 2. Set the ptcueformat query parameter to DPIScte Set the enablec3 query parameter to true or false as appropriate. 4. Create a pttimeline parameter using the VOD timeline format: a) Specify each content block (chapter) with duration = 0 and number_of_lots = 1. b) Specify each ad block as usual, but set lots = 0 to remove a break. Set duration = 0 to use the ad break's duration (from the M3U8 file). Example: Replacing a VOD Timeline This example assumes the VOD content is in Original.m3u8 with a timeline of C,120,1;B,60,2,m;C,120,1;B,60,2,m;C,120,1; The following manifest server request replaces the breaks in Original.m3u8 with a 30-second pre-roll, followed by two breaks of duration two minutes each. &pttimeline=b,30,2,p;c,0,1;b,120,4,m;c,0,1;b,120,4,m;c,0,1; The following manifest server request removes the breaks in Original.m3u8 and adds a 30-second pre-roll and a 30-second post-roll. &pttimeline=b,30,2,p;c,0,1;b,0,0,m;c,0,1;b,0,0,m;c,0,1;b,30,2,t;

14 14 Ad tracking Most advertisers require some detailed information about when, for how long, and how successfully their ads were viewed. The most efficient approach is to have the client player send reports as it plays the ads, but the manifest server also supports server-side and hybrid ad tracking. When enabling ad tracking the client specifies one of the following approaches: Client side Server side Hybrid Along with the ad-stitched playlist, the server sends the client a JSON, VMAP, or in-manifest structure specifying tracking events and URLs. This method is Interactive Advertising Bureau (IAB) compliant The client does not participate in ad tracking. The server sends whatever ad tracking information it can. Tracking data is calculated only on the server side and may not match with client side playback activity. For example, if an end-user does not view the entire ad, after the segments are delivered, the server still considers the ad to be played. This is like client-side tracking, but the client sends its reports to the manifest server, which relays them to the appropriate URLs. Advertisers receive the same information as with client side tracking. This mode accommodates clients running with restricted internet access. Enable client-side ad tracking You can enable client-side ad tracking by adding the pttrackingmode and pttrackingversion parameters to your request. With client-side ad tracking enabled, you can also retrieve ad tracking metadata using the Tracking API URL. For more details see Query parameters. To perform client-side ad tracking, use the Tracking API URL. Add the following query parameters to the manifest server request URL: pttrackingmode=simple pttrackingversion={format version} For example: Overview of non-tvsdk client-side tracking Publishers can build HLS-compliant video players that work with the Primetime manifest server client-side ad tracking workflows. The interfaces to the manifest server for the live stream and video on demand (VOD) cases are slightly different. The manifest server provides an API to enable custom players to request the following URLs, which they can use to report ad tracking events: Ad impression Ad quartile Ad pod progress Content pod progress The manifest server API assumes that any video player using it meets the minimum requirements. See Video Player Requirements for more details.

15 15 Client-side tracking workflow 1. Player obtains a manifest server URL from the publisher. 2. Player appends query parameters specific to its ad insertion requirements and sends an HTTP GET request to the resulting. The has the following syntax: http{s}://{manifest-server:port}/auditude/variant/{publisherassetid}/{urlsafebase64({content URL})}.m3u8?{query parameters} For example: 7LTc86_kMUDFcCjoH9X7K_2auwb_gnWM/aHR0cDovL3B0ZGVtb3MuY29tL3ZpZGVvcy90b3NoZHVuZW5jcnlwdGVkL2hscy90ZXN0Mi5tM3U4.m3u8? u=9a2893fd893cab27da24059ff034b78d&z=173475&pttrackingmode=simple&pttrackingversion=v2& sid =docexample02 The URL includes the elements described in Send a command to the manifest server. 3. The manifest server establishes a session for that player and generates a unique session ID. It creates a new variant M3U8 playlist URL, which it returns to the player as a JSON response.the JSON has the following syntax: { "Master-M3U8": " {urlsafebase64(content URL)}.m3u8?u={Asset ID}&z={Zone ID}&pttrackingmode=simple&pttrackingversion=v2 &{Any other query parameters}" } For example: htp:/pcor3.manifest.auditude.com/auditude/variant/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/f958bef c-80b9-4b15417b7895/ahr0cdovl3b0zgvtb3muy29tl3zpzgvvcy90b3nozhvuzw5jcnlwdgvkl2hscy90zxn0mi5tm3u4.3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 4. Player uses the URL from the JSON response to request the new variant M3U8 master playlist from the manifest server. 5. The manifest server returns a new variant M3U8 containing stream-level playlist URLs with a syntax similar to the following: http{s}://{manifest-server:port}/auditude/{live vod}/{publisherassetid}/ {rendition}/{groupid}/{urlsafebase64(bit rate stream URL)}.m3u8?u={Ad Request Id}&z={Ad Zone Id}&{Any other query parameters} For example: #EXTM3U

16 16 #EXT-X-VERSION:5 #EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="English",AUTOSELECT=YES,DEFAULT=YES,FORCED=NO,LANGUAGE="eng",URI="htp:/pcor3.manifest.auditude.com/auditude/vod/7LTc86_kMUDFcCjoH9X7K_2auwb_gnWM/webvt/f958bef c-80b9-4b15417b7895/aHR0cDovL3d3dy5wdGRlbW9zLmNvbS92aWRlb3MvdG9zaGR1bmVuY3J5cHRlZC9obHMvd2VidnR0L1RPUy1lbjIubTN1OA.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2" #EXT-X-STREAM-INF:BANDWIDTH= ,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/1 0/f958bef c-80b9-4b15417b7895/aHR0cDovL3d3dy5wdGRlbW9zLmNvbS92aWRlb3MvdG9zaGR1bmVuY3J5cHRlZC9obHMvMTAwMDAvdG9jXzEwMDAwLm0zdTg.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH= ,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/130/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvmtmwmc90b2nfmtmwmc5tm3u4.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH= ,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/340/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvmzqwmc90b2nfmzqwmc5tm3u4.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH= ,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/210/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvmjewmc90b2nfmjewmc5tm3u4.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH=800000,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/80/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvodawl3rvy184mdaubtn1oa.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH= ,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/5 0/f958bef c-80b9-4b15417b7895/aHR0cDovL3d3dy5wdGRlbW9zLmNvbS92aWRlb3MvdG9zaGR1bmVuY3J5cHRlZC9obHMvNTAwMC90b2NfNTAwMC5tM3U4.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH= ,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/750/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvnzuwmc90b2nfnzuwmc5tm3u4.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 #EXT-X-STREAM-INF:BANDWIDTH=500000,SUBTITLES="subs" htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/50/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvntawl3rvy181mdaubtn1oa.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 6. The player selects the appropriate single bit rate, stream-level manifest URL for playing the ad-stitched content. For example: htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/50/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvntawl3rvy181mdaubtn1oa.m3u8?u=9a2893fd893cab27da24059f034b78d&z=173475&ptrackingmode=simple&ptrackingversion=v2 7. The manifest server returns a stream-level manifest containing links to the content and ad TS segment links. For example: #EXTM3U #EXT-X-VERSION:3 #EXT-X-TARGETDURATION:8 #EXT-X-PLAYLIST-TYPE:VOD #EXT-X-DISCONTINUITY #EXTINF:8, #EXTINF:7, #EXT-X-DISCONTINUITY #EXTINF:4, #EXTINF:4, #EXTINF:4.833, Note: The player selects the stream-level playlist URL to obtain the content stream. The manifest server retrieves the original playlist from the CDN. Some encoders may inject additional details into the #EXTINF title attribute, for example: #EXTINF:6.006,LTC= T13:25:47+00:00 Since the manifest server cannot infer the meaning of non-standard attributes to modify them for ad-stitched playlist, the manifest server removes all additional attributes beyond the duration information in this tag. See the EXTINF entry in the HLS spec for more details. 8. To request tracking information, the player appends the query parameter pttrackingposition with any alphanumeric value to the stream-level playlist URL for the selected bit rate. For example: htp:/pcor3.manifest.auditude.com/auditude/vod/7ltc86_kmudfccjoh9x7k_2auwb_gnwm/50/f958bef c-80b9-4b15417b7895/ahr0cdovl3d3dy5wdgrlbw9zlmnvbs92awrlb3mvdg9zagr1bmvuy3j5chrlzc9obhmvntawl3rvy181mdaubtn1oa.m3u8?u=9a2893fd893cab27da24059f034b78d &z=173475&pttrackingmode=simple&pttrackingversion=v2&pttrackingposition=1

17 17 9. The manifest server returns the playlist file populated with either a JSON or VMAP object containing the ad tracking data for the stream-level m3u8 file currently requested. Note: The manifest server will only generate ad tracking objects if ads were inserted in the currently requested stream-level playlist. If player is playing a playlist that does not contain inserted ads, the manifest server returns an HTTP Status 201 for the ad tracking playlist request. If the player makes the ad tracking request for a stream it is not playing, manifest server will return an HTTP Status 500. For example, if the current play request is for 500.m3u8, the manifest server returns a JSON VMAP in the 500.m3u8 for the ad tracking request. However, if the player subsequently switches streams to play the 800.m3u8, the ad tracking information in the 500.m3u8 becomes invalid, leading to a 404 error. Note: The manifest server generates the ad tracking object based on the pttrackingversion value in the. If the pttrackingversion is omitted or has an invalid value, then the manifest server will automatically populate the ad tracking information in the #EXT-X-MARKER tags in each requested stream-level playlist. See for more details. 10. The player requests each ad tracking URL for each ad tracking event at the appropriate time. Note: For Live streams, the player must repeat steps 6 through 10 as the packager constantly updates the playlist throughout the duration of the live event. As the video plays, the player must track the playhead position and use this position in conjunction with tracking URLs it received from Primetime ad insertion. The tracking URLs are grouped by time offset from the beginning of play. For each time offset, there is a URL for each ad system to which to send tracking information. Additional details of the format differ between live video and video on demand. API for players to interact with the manifest server Use the optional pttrackingmode, pttrackingversion, and pttrackingposition query parameters to obtain URLs to which to send ad tracking information about the current video. The responses vary with the tracking version and whether the video stream is live or on demand (VOD). Query parameters pttrackingmode Example: pttrackingmode=simple Specifying simple tells the manifest server that you want tracking information. Specify it on a request to fetch the M3U8 before you request tracking information. When you don't specify it, the manifest server returns tracking information in the #EXT-X-MARKER tags. Or, if you specify a valid value other than simple, server-side tracking is invoked. pttrackingversion Example: pttrackingversion=v2 This parameter tells the manifest server which format to use to return tracking information (see File formats). Specify it on a request to fetch the M3U8 before you request tracking information. When you don't specify it, or specify an invalid value, the manifest server uses v1.

18 18 pttrackingposition Example: pttrackingposition This parameter tells the manifest server to return tracking information of the video as a JSON or VMAP object in the M3U8 file. The manifest server ignores the specified value and sends all of the tracking information it has for that session. If no value is passed, manifest server returns the requested M3U8 file. EXT-X-MARKER Directive The manifest server returns master playlists in M3U8 format, conforming to the proposed HTTP Live Streaming standard. It consists of a set of variant transport streams (TSs), each containing renditions of the same content for different bit rates and formats. Adobe Primetime ad insertion adds the EXT-X-MARKER directive tag, to be interpreted by client video players. For details on the EXT-X-MARKER tag, see Adobe Primetime HTTP Live Streaming Profile. Note: This functionality is only available if the bootstrap manifest server URL does not contain the pttrackingmode parameter. Note: The EXT-X-MARKER tag is added to ad segments and not content segments. The draft standard at HTTP Live Streaming describes the contents and format of variant playlists. The EXT-X-MARKER tag directs the client to invoke a callback. It contains the following components: ID TYPE DURATION OFFSET DATA COUNT BREAKDUR Unique identifier (string) for this callback event within the context of the program stream. Type (string) of the callback event: PodBegin, PodEnd, PrerollPodBegin, PrerollPodEnd, or AdBegin Length of time (in seconds) from the start of the segment carrying the tag for which the directive remains valid. Optional. The offset (in seconds) relative to the beginning of the segment playback, when the callback must be invoked. PodBegin and PrerollPodBegin contain beacon information in the DATA attribute and are fired at start of the segment. So the OFFSET tag is not available here. AdBegin contains beacon information in the DATA attribute and impression tags are fired at start of that segment. So the OFFSET tag is not available here either. PodEnd and PrerollPodEnd contain beacon information in the DATA attribute but are fired at end of the current segment because these tags are expected to be fired at end of last segment of last ad in the pod. In this case, OFFSET is set to <duration of segment> to specify that the beacon be fired at end of the current segment. Base64-encoded string enclosed in double quotes containing the data to pass to the application when invoking the callback. It contains ad tracking information that conforms to VMAP1.0 and VAST3.0 specifications. Number of ads that will be stitched in the ad break. Only Applicable if the TYPE component is set to PodBegin or PrerollPodBegin. Total duration (in seconds) of the filled ad break. Only Applicable if the TYPE component is set to PodBegin or PrerollPodBegin.

19 19 When constructing the callback, interpret the EXT-X-MARKER components as follows: When the tag contains OFFSET, fire the callback at the specified offset relative to the beginning of content playback in that segment. Otherwise, fire the callback as soon as the content in that segment starts playing. Use DURATION to track the ad content's progress and to request URLs for tracking events. Pass ID, TYPE, and DATA to the callback. Use the PrerollPodBegin, and PrerollPodEnd values for TYPE to decide which TS segment to play first in live/linear streams. Note: The PrerollPodBegin, and PrerollPodEnd values are only available when a pre-roll ad is inserted into a live stream. The manifest server includes EXT-X-MARKER tags in the following segments: The first segment in the ad break, to track the beginning of an ad pod. The first segment of the ad, to track the start/complete/progress of an individual ad within an ad pod. The last segment in the ad break, to track the end of an ad pod. The manifest server sends a VMAP1.0-conformant XML document to track the start and end of each ad break. It is a filtered version of the actual VMAP1.0 response returned by the ad server, and primarily contains the tracking events as shown here: <?xml version="1.0"?> <AdTrackingFragments> <AdTrackingFragment> <vmap:vmap xmlns:vmap=" version="1.0"> <vmap:adbreak breaktype="linear" breakid="mypre" timeoffset="start"> <vmap:trackingevents> <vmap:tracking event="breakstart"> </vmap:tracking> <vmap:tracking event="breakend"> </vmap:tracking> <vmap:tracking event="error"> </vmap:tracking> </vmap:trackingevents> </vmap:adbreak> </vmap:vmap> </AdTrackingFragment> </AdTrackingFragments> For each ad creative the manifest server inserts into the program content, it sends a VAST3.0-conformant XML document to track that ad. Each XML document contains an <InLine> element describing the linear ad creative inserted, or a <Wrapper> element in the case of wrapper ads (that is, linked or redirected ads), and any associated companion ads and extensions. If the VAST response contains a sequence attribute, such as when the ad is part of an ad pod, the document includes that attribute. The following is a sample VAST3.0-conformant XML document for tracking an individual ad: <?xml version="1.0"?> <AdTrackingFragments> <AdTrackingFragment> <VAST xmlns:xsi=" version="3.0" xsi:nonamespaceschemalocation=" <Ad id="903395"> <InLine> <AdSystem version="1.0">auditude</adsystem> <AdTitle/>

20 20 <Error> <Impression id="urn:aeid:903395"> cid= & z=50183& a=903395& s=ef8c51dc& t= & w=100000& uid=_cxlm0b1sekd8kxco 5TQ& l= & u=956c3cd141086a1da44dcae8ea4ed14a& br=1& sq=1& pod=id:1,ctype:l,ptype:p,dur:400,lot:8,cpos:1,edur:400,elot:8& ax=0,0,1720,0/?contentposition=[contentplayhead]?cashcash=[cachebusting]?asset=[asseturi] </Impression> <Creatives> <Creative> <Linear> <Duration>00:00:15</Duration> <TrackingEvents>... <Tracking event="firstquartile"> a=903395& a1=105& ref=urn:asset:903395:105& unit=percent& progress=25& cid= & z=50183& a=903395& s=ef8c51dc& t= & w=100000& uid=_cxlm0b1sekd8kxco 5TQ& l= & u=956c3cd141086a1da44dcae8ea4ed14a& br=1& sq=1& pod=id:1,ctype:l,ptype:p,dur:400,lot:8,cpos:1,edur:400,elot:8& ax=0,0,1720,0/?contentposition=[contentplayhead]?cashcash=[cachebusting]?asset=[asseturi] <Tracking event="midpoint"> a=903395& a1=105& ref=urn:asset:903395:105& unit=percent& progress=50& cid= & z=50183& a=903395& s=ef8c51dc& t= & w=100000& uid=_cxlm0b1sekd8kxco 5TQ& l= & u=956c3cd141086a1da44dcae8ea4ed14a& br=1& sq=1& pod=id:1,ctype:l,ptype:p,dur:400,lot:8,cpos:1,edur:400,elot:8& ax=0,0,1720,0/?contentposition=[contentplayhead]?cashcash=[cachebusting]?asset=[asseturi]

21 21 <Tracking event="firstquartile"> <Tracking event="midpoint"> </TrackingEvents> <VideoClicks> <ClickTracking> </ClickTracking> <ClickThrough> </ClickThrough>... </VideoClicks> <AdParameters>campaign_id=7012</AdParameters> <MediaFiles>... </MediaFiles> </Linear> </Creative> <Creative> <CompanionAds> <Companion id="103" width="300" height="250"> <StaticResource creativetype="image/jpeg"> l= ; u=956c3cd141086a1da44dcae8ea4ed14a; uid=_cxlm0b1sekd8kxco 5TQ; cid= ; s=ef8c51dc; t= ; br=1; sq=1; pod=id%3a1%2cctype%3al%2cptype%3ap%2cdur %3a400%2clot%3a8%2ccpos%3a1%2cedur%3a400%2celot%3a8; ax=0%2c0%2c1720%2c0; w=100000; a=903395; a1=103/c300x250.jpeg </StaticResource> <CompanionClickThrough> %3Ba2=1%3Bz=50183%3Bl= %3Bu=956c3cd141086a1da44dcae8ea4ed14a %3Bcid= %3Bs=ef8c51dc%3Buid=_CxLm0b1SeKD8KXco 5TQ %3Bt= %3Bbr=1%3Bsq=1%3Bpod=id%3a1%2cctype%3al%2cptype %3ap%2cdur%3a400%2clot%3a8%2ccpos%3a1%2cedur%3a400%2celot%3a8 %3Bax=0%2c0%2c1720%2c0 </CompanionClickThrough> <AdParameters>campaign_id=7012</AdParameters> </Companion> </CompanionAds> </Creative>... </Creatives> <Extensions> <Extension type="behavior">...

22 22 </Extension> </Extensions> </InLine> </Ad> </VAST> </AdTrackingFragment> </AdTrackingFragments> Cookies Primetime ad insertion uses cookies for internal purposes and to facilitate working with streams and ad servers. Primetime ad insertion maintains the following cookies: ssaipub helps retrieve content URLs from streams that require cookie authentication to obtain the m3u8 file. ssai3 holds session cookies for ad servers requiring them. AWSELB and ssaisession hold internal information. Support for WebVTT captions The manifest server supports publisher-enabled WebVTT captions for all HLS video formats. When it receives requests to insert ads into WebVTT captioned content, it does so correctly. If the publisher includes WebVTT captions in the content, the manifest server sends the client a content stream with captions. WebVTT must be enabled by the publisher for the manifest server to support captions. When the client has WebVTT captions enabled, and sends a request to the manifest server, the manifest server manipulates the timeline and WebVTT track and returns content with stitched ads and captions to the client. The workflow for VOD content streams is as follows: 1. The client sends a content stream with WebVTT captions enabled to the manifest server. 2. The manifest server manipulates the timeline to stitch ads into the content stream. 3. The manifest server manipulates the WebVTT track to add captions to the content (including ads). 4. The manifest server delivers the content stream to the client, with inserted ads and captions. Note: If a WebVTT caption segment falls within a mid-roll ad, the viewer sees that caption play before and after that mid-roll ad break. For example, in a 10-second caption segment with a 30-second mid-roll ad at the 5-second mark, the viewer sees that caption segment for 5 seconds before the mid-roll ad break, and for 5 seconds after the mid-roll. Note: If a client requests that a video play in a specific language such as English, and then requests to play the video in French, manifest server cannot detect that the client requested to change the language to French. Because the client doesn't communicate with the manifest server, the manifest server inserts the ad caption into the video stream using the first language specified in the ad's M3U8 master file. File formats If the client requests tracking information, the manifest server sends back a formatted file. Its format and contents depend on the value of the query parameter pttrackingversion

23 23 JSON format for URL for requesting variant manifest playlist If pttrackingmode=simple or ptplayer=ios-mobileweb, the manifest server sends back a JSON-formatted file containing Master-M3U8, a URL for the client to use to request the M3U8 file describing the content. This is the format of the JSON file containing the Master-M3U8 URL. { "Master-M3U8": " {sessionid}/{base 64 of the url of the content}.m3u8?u={ad Request Id} &z={ad Zone Id} &pttrackingmode=simple &pttrackingversion=v1 &{other query parameters}" } JSON formats for tracking URLs If the client requests tracking information in JSON format, the manifest server sends back a file in one of the JSON formats. JSON format for tracking version 1 The JSON file that the manifest server sends if pttrackingversion=v1 has the following general format: { "start" : <start-time-of-first-sample-of-playback>, "end" : <end-time-of-last-sample-of-playback>, "adtracking" : [ { "time": <time-offset-relative-to-beginning-of-playback>, "trackingurls":[{ "adsystem": <ad-system-of-url1>, "url" : <url1> "adsystem": <ad-system-of-url2>, "url" : <url2>},...] },...]} JSON format for tracking version 2 The JSON file that the manifest server sends if pttrackingversion=v2 has the format of the following example, which comes from a typical JSON block. It has been shortened to avoid unnecessary repetition, so that the structure is clearer. An ellipsis (three dots, separated by spaces) indicates omitted information within some URLs and between some code blocks. Unshortened URLs appear on multiple lines, though they appear on a single line in the JSON file. { "starttime" : 0.0, "endtime" : , "scte35" : [ { "offset" : 31.03, "programdatetime" : 31.03, "tagname" : "EXT-X-SCTE35", "tagattributes" : { "CUE" : "/DBIAAAAAAAA/wBwBQb+D24zFgAyAhdDVUVJQAAABH+fCAgAAAAARERERBAAAAIXQ1VFSUAAAAN/nwgIAAAAADMzMzMRAAB4jsoB", "ID" : " " } "offset" : 111.1, "programdatetime" : 111.1, "tagname" : "EXT-X-SCTE35",