TEST 1: STANDARD PLAYBACK

Transcription

1 TEST 1: STANDARD PLAYBACK This test case is required as part of the certification request form and validates general playback and sequencing. TEST 1: PERFORM AND RECORD THE FOLLOWING ACTIONS IN THIS ORDER: 1. Load page or app 2. Start video player 3. View ad break, if available 4. Pause ad playback for at least 30 seconds, if available 5. Play main content video for 10 minutes uninterrupted 6. Pause during playback for at least 30 seconds 7. Seek/scrub video 8. Replay video ( only) 9. View next video in playlist or show boundary (live/linear) 10. Switch video or stream to a new video KEY DETAILS FOR EACH STEP 0. OVERVIEW Video implementations are composed of three types of tracking calls. 1. Video and Ad Start calls are sent directly to the AppMeasurement server 2. Heartbeat calls are sent on start and every ten seconds to the Heartbeat tracking server Video tracking will behave the same across all platforms, desktop and mobile. 1. LOAD PAGE OR APP Across all tracking calls there are a few key universal variables to be validated: Tracking Servers: On any website or mobile app, three tracking servers will be used: 1. AppMeasurement (Analytics): See more details on tracking server options. Note an RDC tracking server or CNAME resolving to an RDC server is required for Marketing Cloud Visitor ID service. The analytics tracking server should either end in.sc.omtrdc.net or be a CNAME Video Heartbeat: Always has the format [namespace].hb.omtrdc.net, where [namespace] is defined by your log-in company, provided by Adobe.

2 ADOBE Adobe Visitor ID: The mid variable is used to capture the set in the AMCV cookie. The mid variable is the primary identification for both websites and mobile apps and also indicates that the Marketing Cloud Visitor ID service is set-up properly. It will be found in both AppMeasurement and Video Heartbeat calls. Lifecycle Call pev2 ADBINTERNAL:Lifecycle mid Website Page Calls mid Video Analytics Start Call pev2 ms_s mid Heartbeat Play Call play s:user:mid *Note: On Heartbeat Start Calls (=start) the mid s may not be present. This is OK. They may not appear until the Heartbeat Play Calls (=play). Video Analytics Start Call pev2 ms_s Heartbeat Start Call start

3 2. START VIDEO PLAYER VIDEO START On start of a video player, four key calls are sent: 1. Video analytics start* 2. Heartbeat start* 3. Heartbeat analytics start *Calls contain additional metadata and variables. See details below each call. Video Analytics Start Call pev2 ms_s a.media.friendlyname Episode Title a.media.name a.media.length 120 a.media.playername HTML 5 a.media.view true a.contenttype custom.[] a.media.[] Custom metadata fields Standard metadata fields Note A: Additional context data variables should be present and contain metadata. See metadata details below. Note B: Length for linear streams should be set to the best estimate for the current show. Standard Metadata in Video Analytics Start Call a.media.show a.media.season 6 a.media.episode Show Title Episode Title a.media.asset_id

4 a.media.genre comedy a.media.first_air_date a.media.rating TV-14 a.media.originator production house a.media.network network a.media.ad_load 1 a.media.mvpd mvpd a.media.authorized unlocked a.media.feed no feed a.media.stream_format 0 Video Metadata in Video Analytics Start Call custom.metadataa custom.metadatab Heartbeat Start Call start l:event:playhead 0 l:event:duration 4 l:asset:name Episode Title l:asset:video_id

5 l:asset:length 120 main s:meta:custom.[] s:meta:a.media.[] Custom metadata fields Standard metadata fields Note A: Additional context data variables should be present and contain metadata. See metadata details below. Note B: Playhead position for linear streams on video start should be set to the seconds elapsed since the start of the current show, not 0. Standard Metadata in Video Heartbeat Start Call s:meta:a.media.show s:meta:a.media.season 6 s:meta:a.media.episode Show Episode Title s:meta:a.media.asset_id s:meta:a.media.genre comedy s:meta:a.media.first_air_date s:meta:a.media.rating s:meta:a.media.originator s:meta:a.media.network s:meta:a.media.ad_load 1 s:meta:a.media.mvpd s:meta:a.media.authorized s:meta:a.media.feed s:meta:a.media.stream_format 0 TV-14 production house network mvpd unlocked no feed

6 Video Metadata in Video Heartbeat Start Call s:meta:custom.metadata s:meta:custom.metadata Heartbeat Analytics Start Call l:event:playhead 0 l:event:duration 4 l:asset:name aa_start Episode Title l:asset:video_id l:asset:length 120 main Note A: This call indicates that the heartbeat library has requested that an analytics pev2=ms_s call be sent to the analytics server. Note B: This call does not contain custom metadata.

7 3. VIEW AD BREAK, IF AVAILABLE AD START On start of a video ad, four key calls are sent: 1. Video ad analytics start* 2. Heartbeat ad start* 3. Heartbeat ad analytics start *Calls contain additional metadata and variables. See details below each call Video Analytics Ad Start Call pev2 msa_s a.media.name a.media.ad.name 9378 a.media.ad.friendlyname Video_VPAID_DFA a.media.ad.podfriendlyname preroll a.media.ad.length 15 a.media.ad.playername HTML 5 a.media.ad.pod c27aaf3ff8224bb6b9ebfe1b2e79073d_1 a.media.ad.podposition 1 a.media.ad.podsecond 0.0 a.media.ad.view True custom.[] a.media.[] Metadata fields Standard metadata fields Note A: Additional context data variables should be present and contain metadata. See metadata details below. Standard Metadata in Video Ad Analytics Start Call a.media.show a.media.season 6 a.media.episode Show Episode a.media.asset_id a.media.genre comedy a.media.first_air_date

8 a.media.rating TV-14 a.media.originator Production house a.media.network network a.media.ad_load 1 a.media.mvpd mvpd a.media.authorized unlocked a.media.feed no feed a.media.stream_format 0 Video Metadata in Video Ad Analytics Start Call custom.metdata custom.metdata Heartbeat Ad Start Call start l:event:playhead 0 l:event:duration 0 l:asset:ad_id 9378 l:asset:length 15 ad s:meta:custom.[] Custom metadata fields

9 s:meta:a.media.[] Standard metadata fields Note A: Additional context data variables should be present and contain metadata. See metadata details below. Note B: Ad length may be set to -1 if not available on ad start. Standard Metadata in Video Ad Heartbeat Start Call s:meta:a.media.show s:meta:a.media.season 6 s:meta:a.media.episode Show Episode s:meta:a.media.asset_id s:meta:a.media.genre comedy s:meta:a.media.first_air_date s:meta:a.media.rating s:meta:a.media.originator s:meta:a.media.network s:meta:a.media.ad_load 1 s:meta:a.media.mvpd s:meta:a.media.authorized s:meta:a.media.feed s:meta:a.media.stream_format 0 TV-14 Production house Network mvpd unlocked no feed Video Metadata in Video Ad Heartbeat Start Call s:meta:custom.metadata

10 s:meta:custom.metadata Heartbeat Analytics Ad Start Call l:event:playhead 0 l:event:duration 0 l:asset:ad_id 9378 l:asset:ad_length 15 aa_ad_start ad Note A: This call indicates that the heartbeat library has requested that an analytics pev2=msa_s call be sent to the analytics server. Note B: This call does not contain custom metadata. AD PLAY During ad content playback, Heartbeat calls are sent to the Heartbeat server every ten seconds. Heartbeat Ad Play Call play l:event:playhead 15 l:event:duration 0 l:asset:ad_id 9378 l:asset:ad_length 15 ad AD COMPLETE At the 100% point on a video ad a Heartbeat complete call will be sent. Heartbeat Ad Complete Call complete l:event:playhead 15 l:event:duration 0 l:asset:ad_id 9378

11 l:asset:ad_length 15 ad 4. PAUSE AD PLAYBACK FOR AT LEAST 30 SECONDS, IF AVAILABLE AD PAUSE During ad content pause, Heartbeat calls are sent to the Heartbeat server every ten seconds. Heartbeat Ad Play Call l:event:playhead 15 l:event:duration 0 pause l:asset:ad_id 9378 l:asset:ad_length 15 ad Note A: The playhead should remain constant during the pause 5. PLAY MAIN CONTENT VIDEO FOR 10 MINUTES UNINTERRUPTED CONTENT PLAY During regular main content playback, Heartbeat calls are sent to the Heartbeat server every ten seconds. Heartbeat Play Call play l:event:playhead 29 l:event:duration l:asset:name Episode Title l:asset:video_id l:asset:length 120 main Note A: The playhead position should increment by 10 with every play call

12 Note B: The l:event:duration represents the number of milliseconds since the last tracking call and should be roughly the same on each 10 second call. Note A: Values in this call should align with Heartbeat and Video Analytics data. 6. PAUSE DURING PLAYBACK FOR AT LEAST 30 SECONDS On pause of the video player pause event calls will be sent every 10 seconds. After pause ends the play events should resume. Heartbeat Pause Call l:event:playhead 29 pause l:event:duration l:asset:name l:asset:video_id l:asset:length 120 What s New On Show? main Note A: The playhead should remain constant during the pause 7. SEEK/SCRUB VIDEO On scrubbing of video playhead, no special tracking calls are sent, however, when video playback resumes after scrubbing the playhead should reflect the new position within the main content.

13 8. REPLAY VIDEO (VOD ONLY) When a video is replayed a new set of video start calls should be sent, as if this is a fresh video view. 9. VIEW NEXT VIDEO IN PLAYLIST OR SHOW BOUNDARY (LIVE/LINEAR) On video start of the next video in a playlist, a new set of video start calls should be sent. 10. SWITCH VIDEO OR STREAM TO A NEW VIDEO When switching live streams a Heartbeat complete call for the first stream should not be sent. The video start calls and video play calls should begin with the new show and stream name and with the correct playhead and duration s for the new show.