Originating owner fields (Originating Owner Group ID – OOGID and Originating Owner Broadcaster Content ID – OOBCID) are used to identify third party content on a particular Player. Content IDs which Player sends in tags for OD content correspond to BCIDs generated by Player owner, and it is important that Originating owner information is correctly populated in CDMF (via XML) for those BCIDs.
This check is focused on third party content, which is identified based on OOGID value – if OOGID is provided and different from BGID (Broadcaster group ID, in this case Player owner), then OOBCID column is also expected. Below is a reference table:
OOGID Provided? | OOGID matches BGID? | OOBCID expected? |
|---|---|---|
|
|
|
|
|
|
| Assume content is Player Owner’s Own Content. |
|
Records are grouped in following categories:
- Blank OOBCIDs - How many Content IDs have blank OOBCID
This could mean that 3rd party provider (Originating owner) did not share their BCIDs with Player owner, or Player owner has not submitted them correctly
This count also includes cases where Player owner did not submit a record for third party content at all:
- In this case we have identified live viewing on a player which is matched to 3rd Party TX log based on the Stream ID from tag, however there is no metadata submitted by Player owner
- Broadcaster Content ID in Detail report will be set to ‘NOT AVAILABLE’
- Please note that OOBCID value will still be set to Originating owner BCID identified based on TX log even though it was not submitted by Player Owner – for purposes of content identification.
- OOBCID matched only to CDMF - How many contents have OOGID + OOBCID matching a standalone entry in CDMF file (with BCID + BGID)
This means that OOBCIDs were populated correctly, and originator has submitted the master record via XML. OOBCIDs from this group were not matched to TX log
- OOBCID matched only in TX log – How many content ID’s were found in TX log of originating owner. OOBCIDs from this group did not have master record in CDMF
- OOBCIDs matched to both TX and CDMF – How many OOBCIDs were matched to both TX log for originating owner and also have a master record submitted in CDMF
- Not matched to anything – How many OOBCID’s were provided following an OOGID, but do not have master record in CDMF and were not matched against TX log of Originating owner
- Own content – Assumed own content - OOGIDs were not provided or OOGID=BGID, hence OOBCID check was not relevant
Recommendations and consequences of non-compliance
Recommendations
Both Originating owners and Player owners need to ensure that XMLs with appropriate metadata are submitted to Kantar on or before day of transmission or upload onto Player for on demand viewing.
- Player owner should submit BCIDs used on the Player, with OOGID and OOBCID fields populated correctly, based on data supplied by Originating owner
- Originating owner needs to submit same Content IDs (OOBCIDs from above) as BCIDs and also supply the same to Player owner in time for their submission. If possible, OOBCIDs should always refer to linear Content ID (which will be submitted in TX logs) in order to ensure linking and correct reporting in Dovetail
Consequences of non-compliance
Missing OOBCID will prevent content from being attributed from the player owner to the content owner. Correctly populated OOBCID (and OOGID) in a CDMF record of a player owner will ensure that when a programme is viewed across multiple players it is still attributed to its originating content owner.
Playtime in this check is driven by viewed 3rd party content in Census, it will not include Playtime from Originating player (if applicable).
Output columns
Column name | Description |
|---|---|
Player | Player name |
Content owner | Player owner or 3rd Party broadcaster name |
Activity** | Live or On Demand – **only applicable for playtime version |
Blank OOBCID | Count/percentage of records (or playtime) where OOGID is provided, but OOBCID is blank |
OOBCID matched only to CDMF | Count/percentage of records (or playtime) where OOBCID is only matched to CDMF |
OOBCID matched only to TX log | Count/percentage of records (or playtime) where OOBCID is only matched to TX log |
OOBCID matched to both CDMF and TX log | Count/percentage of records (or playtime) where OOBCID is present as master record in CDMF and matched to TX log |
Not matched to anything | Count/percentage of records (or playtime) where OOBCID is provided but it is not present as standalone record in CDMF or matched to TX log |
Own content | Count/percentage of records (or playtime) where OOGID is not provided, or is same as BGID, so we assume it is own content and OOBCID is not checked |
Total | Total count |