Digital Measurement SEI Streaming Content Viewing - Revision history

DarsanaDinesh at 15:36, 31 October 2025

2025-10-31T15:36:02Z

← Older revision		Revision as of 15:36, 31 October 2025
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|~~Digital Streaming Measurement~~}} {{CurrentBreadcrumb}}		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|US DCR & DTVR}} {{CurrentBreadcrumb}}
	[[Category:Digital]]		[[Category:Digital]]

2025-10-31T15:32:47Z

← Older revision		Revision as of 15:32, 31 October 2025
Line 166:		Line 166:
	== SLA ==		== SLA ==
	The files must be delivered into the proper S3 bucket within 3 hours of the start of that hourly viewing file interval. For example, files from 1:00 AM to 2:00 AM must be delivered before 4 AM.		The files must be delivered into the proper S3 bucket within 3 hours of the start of that hourly viewing file interval. For example, files from 1:00 AM to 2:00 AM must be delivered before 4 AM.

			== Accuracy of Measurement ==
			The reported “wall clock” time of viewing needs to be within 25 seconds of the actual viewing time.

			The reported content “reference” time needs to match the actual content that was played out with plus/minus 10 seconds (for clarity: start and end times can each be off by up to 10 seconds, so the combined under/over reporting for each individual viewing segment should be no greater than 20 seconds)

	== CTV, Mirroring, and Casting ==		== CTV, Mirroring, and Casting ==

2025-10-30T12:59:28Z

@@ Line 295: / Line 295: @@
 Example:
 <code>VID123456789</code>
 |-
 | colspan="2" |dma

2025-10-30T12:57:55Z

Accuracy of Measurement

← Older revision		Revision as of 12:57, 30 October 2025
Line 166:		Line 166:
	== SLA ==		== SLA ==
	The files must be delivered into the proper S3 bucket within 3 hours of the start of that hourly viewing file interval. For example, files from 1:00 AM to 2:00 AM must be delivered before 4 AM.		The files must be delivered into the proper S3 bucket within 3 hours of the start of that hourly viewing file interval. For example, files from 1:00 AM to 2:00 AM must be delivered before 4 AM.

	~~== Accuracy of Measurement ==~~
	~~The reported “wall clock” time of viewing needs to be within 25 seconds of the actual viewing time.~~

	The reported content “reference” time needs to match the actual content that was played out with plus/minus 10 seconds ''(for clarity: start and end times can each be off by up to 10 seconds, so the combined under/over reporting for each individual viewing segment should be no greater than 20 seconds)''

	== CTV, Mirroring, and Casting ==		== CTV, Mirroring, and Casting ==
Line 484:		Line 479:
	\|{		\|{
	\|adpod		\|adpod
	\|AdPod sequence number.~~</code>~~		\|AdPod sequence number.

	Increment for each AdPod. If the same AdPod is played out twice (due to rewind), still increment the AdPod sequence to reflect the sequence the AdPods are played.		Increment for each AdPod. If the same AdPod is played out twice (due to rewind), still increment the AdPod sequence to reflect the sequence the AdPods are played.

2024-08-14T18:52:42Z

Schema Parameter Definitions

← Older revision		Revision as of 18:52, 14 August 2024
Line 418:		Line 418:
	</syntaxhighlight>		</syntaxhighlight>
	\|-		\|-
	\|		\|{
	\|referencestart		\|referencestart
	\|Wall clock reference start time		\|Wall clock reference start time

2024-06-25T18:08:57Z

Delivery Specifications: Adding preference for Parquet

← Older revision		Revision as of 18:08, 25 June 2024
Line 11:		Line 11:
	* All prefix labels and file names should be lowercase except for app ids.		* All prefix labels and file names should be lowercase except for app ids.
	* Supported format are:		* Supported format are:
	** Apache Parquet format with snappy compression; (preferred ~~format~~)		** Apache Parquet format with snappy compression; (preferred)
	** Text files with utf-8 encoding in JSON Lines format;		** Text files with utf-8 encoding in JSON Lines format;
	* All data files have extensions to indicate the file format (.json \| .parquet)		* All data files have extensions to indicate the file format (.json \| .parquet)

2024-06-25T18:07:48Z

Delivery Specifications

← Older revision		Revision as of 18:07, 25 June 2024
Line 11:		Line 11:
	* All prefix labels and file names should be lowercase except for app ids.		* All prefix labels and file names should be lowercase except for app ids.
	* Supported format are:		* Supported format are:
			** Apache Parquet format with snappy compression; (preferred format)
	** Text files with utf-8 encoding in JSON Lines format;		** Text files with utf-8 encoding in JSON Lines format;
	** Apache Parquet format with snappy compression;
	* All data files have extensions to indicate the file format (.json \| .parquet)		* All data files have extensions to indicate the file format (.json \| .parquet)
	* Data file can be partitioned into multiple parts with min size of 256MB		* Data file can be partitioned into multiple parts with min size of 256MB

2024-06-22T07:39:30Z

Undo revision 6801 by Admin (talk)

← Older revision		Revision as of 07:39, 22 June 2024
Line 7:		Line 7:

	== Delivery Specifications ==		== Delivery Specifications ==
	Files should be delivered at a fixed cadence in a dedicated S3 bucket following ~~the directory structure outlined in this spec~~ prefix and object naming conventions and data formats~~. Audio files, and Asset Metadata files should exist within the same directory~~.		Files should be delivered at a fixed cadence in a dedicated S3 bucket the following prefix and object naming conventions and data formats.

	* All prefix labels and file names should be lowercase except for app ids.		* All prefix labels and file names should be lowercase except for app ids.

2024-06-22T07:36:37Z

Delivery Specifications

← Older revision		Revision as of 07:36, 22 June 2024
Line 7:		Line 7:

	== Delivery Specifications ==		== Delivery Specifications ==
	Files should be delivered at a fixed cadence in a dedicated S3 bucket following the outlined in this spec prefix and object naming conventions and data formats.		Files should be delivered at a fixed cadence in a dedicated S3 bucket following the directory structure outlined in this spec prefix and object naming conventions and data formats. Audio files, and Asset Metadata files should exist within the same directory.

	* All prefix labels and file names should be lowercase except for app ids.		* All prefix labels and file names should be lowercase except for app ids.

2024-06-22T01:06:40Z

S3 Bucket and Prefix Naming Convention

← Older revision		Revision as of 01:06, 22 June 2024
Line 18:		Line 18:

	=== S3 Bucket and Prefix Naming Convention ===		=== S3 Bucket and Prefix Naming Convention ===
	<code>useast1-nlsn-w-dig-sei-<'''partnerid'''>-feeds-'''<env>/<filetype>/<split>/yyyy/mm/dd/hh/<object>'''</code>		<code>useast1-nlsn-w-dig-sei-<'''partnerid'''>-feeds-'''<env>'''/'''<filetype>'''/'''<split>'''/'''yyyy/mm/dd/hh'''/'''<object>'''</code>
	{\| class="wikitable"		{\| class="wikitable"
	!'''Name'''		!'''Name'''