Template

DCR Content Metadata

From Engineering Client Portal

Revision as of 20:56, 2 October 2018 by Admin3 (talk | contribs) (Created page with " {| class="wikitable" |- ! Keys !! Description !! Values !! Required |- | type || type of asset || <code>"content"</code> || Yes |- | assetid || unique ID assigned to asset ||...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Keys Description Values Required
type type of asset "content" Yes
assetid unique ID assigned to asset custom Yes
program name of program (25 character limit) ProgramName Yes
title name of program (40 character limit) Program S3, EP1 Yes
length length of content in seconds seconds (86400 for live stream) Yes
airdate the airdate in the linear TV YYYYMMDD HH24:MI:SS Yes
isfullepisode full episode flag "y"- full episode, "n"- non full episode Yes
adloadtype type of ad load:

"1" Linear – matches TV ad load

"2" Dynamic – Dynamic Ad Insertion (DAI)

"2" - DCR measures content with dynamic ads Yes
segB custom segment B custom
segC custom segment C custom
crossId1 standard episode ID custom
crossId2 content originator (only required for distributors) custom

Custom segments (segB and segC) can be used to aggregate video and/or static content within a single Brand to receive more granular reports within a brand.

Examples regarding usage of segments within SDK:

  • All comedy clips and stories for a Brand rolled into a “Comedy” segment
  • genre grouping content by Comedy vs. Drama
  • group related Text + Video content - i.e. for a show that has a lot of - static pages associated with it
  • packaging based on how clients sell inventory
  • grouping related types of content either by genre, category or platform.