Digital Measurement SEI Content Viewing - Revision history

Admin at 18:28, 13 December 2024

2024-12-13T18:28:46Z

← Older revision		Revision as of 18:28, 13 December 2024
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}This interface specification depicts the file schema required to supply Nielsen with response-level Viewing data in a “Server-to-Server” relationship for incorporation into the Nielsen One Content ~~and/or Nielsen One Ads~~ products.		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}This interface specification depicts the file schema required to supply Nielsen with response-level Viewing data in a “Server-to-Server” relationship for incorporation into the Nielsen One Content measurement products.

	This document describes the log file exposures, to be used in conjunction with [[Digital Measurement SEI Content Asset Metadata]] and [[Digital Measurement Content Audit Beacon]] to enable measurement.		This document describes the log file exposures, to be used in conjunction with [[Digital Measurement SEI Content Asset Metadata]] and [[Digital Measurement Content Audit Beacon]] to enable measurement.

Admin at 18:28, 13 December 2024

2024-12-13T18:28:27Z

← Older revision		Revision as of 18:28, 13 December 2024
Line 1:		Line 1:
	{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}This interface specification depicts the file schema required to supply Nielsen with response-level Viewing data in a “Server-to-Server” relationship for incorporation into the Nielsen One Content and/or Nielsen One Ads products.		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}This interface specification depicts the file schema required to supply Nielsen with response-level Viewing data in a “Server-to-Server” relationship for incorporation into the Nielsen One Content and/or Nielsen One Ads products.

			This document describes the log file exposures, to be used in conjunction with [[Digital Measurement SEI Content Asset Metadata]] and [[Digital Measurement Content Audit Beacon]] to enable measurement.

	= Delivery Specifications =		= Delivery Specifications =

Admin: {

2024-11-18T15:27:29Z

{

← Older revision		Revision as of 15:27, 18 November 2024
Line 337:		Line 337:
	</syntaxhighlight>		</syntaxhighlight>
	\|-		\|-
	\|		\|{
	\|referencestart		\|referencestart
	\|Wall clock reference start time		\|Wall clock reference start time

Admin: /* Schema Parameter Definitions */

2024-06-22T01:17:01Z

Schema Parameter Definitions

@@ Line 295: / Line 295: @@
 Example:
 <code>VID123456789</code>
 |-
 | colspan="2" |ad_load_flag
@@ Line 479: / Line 403: @@
 |{
 |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.

Admin: /* CTV, Mirroring, and Casting */

2024-06-22T01:13:17Z

CTV, Mirroring, and Casting

Show changes

Admin: Undo revision 6789 by Admin (talk)

2024-06-22T01:11:29Z

Undo revision 6789 by Admin (talk)

Show changes

Admin: /* CTV, Mirroring, and Casting */

2024-06-22T01:10:43Z

CTV, Mirroring, and Casting

Show changes

Admin: /* Manifest File */

2024-06-22T01:10:17Z

Manifest File

← Older revision		Revision as of 01:10, 22 June 2024
Line 146:		Line 146:
	\|}		\|}

	~~'''~~Data delivery example for hour 11 (11:00:00 AM UTC to 11:59:59 PM UTC):~~'''~~		=== Data delivery example for hour 11 (11:00:00 AM UTC to 11:59:59 PM UTC): ===
	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0000.json		<code>useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0000.json

	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0001.json		useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0001.json

	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0002.json		useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0002.json

	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0003.json		useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0003.json

	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_manifest		useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_manifest

	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/_SUCCESS		useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/_SUCCESS</code>

	= SLA =		= SLA =

Admin: /* Manifest File */

2024-06-22T01:09:29Z

Manifest File

← Older revision		Revision as of 01:09, 22 June 2024
Line 77:		Line 77:

	=== Manifest File ===		=== Manifest File ===
	A manifest should be provided which contains metadata related to the uploaded file(s). The manifest is a text file in json format that implements the AWS unload manifest file format. It has the same name as the data file, but has the _manifest suffix.		A manifest should be provided which contains metadata related to the uploaded file(s). The manifest is a text file in .json format that implements the AWS unload manifest file format. It has the same name as the data file, but has the <code>'''_manifest'''</code> suffix.

	Example:		Example:
			<syntaxhighlight lang="JSON">
	{		{

	"entries": [		"entries": [

	{"url":"s3://bucket/prefix/0000_object_00.snappy.parquet", "mandatory":true},		{"url":"s3://bucket/prefix/0000_object_00.snappy.parquet", "mandatory":true},

	{"url":"s3://bucket/prefix/0001_object_00.snappy.parquet", "mandatory":true},		{"url":"s3://bucket/prefix/0001_object_00.snappy.parquet", "mandatory":true},
			{"url":"s3://bucket/prefix/0002_object_00.snappy.parquet", "mandatory":true}
	{"url":"s3://bucket/prefix/0002_object_00.snappy.parquet", "mandatory":true},

	{"url":"s3://bucket/prefix/0003_object_00.snappy.parquet", "mandatory":true}		{"url":"s3://bucket/prefix/0003_object_00.snappy.parquet", "mandatory":true}

	],		],

	"meta": {		"meta": {

	"schema_version": "S2SV1.7.0",		"schema_version": "S2SV1.7.0",

	"accreditation_status": "0",		"accreditation_status": "0",

	"start_time": "1710154800",		"start_time": "1710154800",

	"end_time": "1710158399",		"end_time": "1710158399",
			"record_count": 31337
	"record_count": 55

	}		}
			}
			</syntaxhighlight>

	}
	The manifest contains a complete list of all files provided for a given period and split, as well as a meta data (a.k.a. header) which should include the following attributes:		The manifest contains a complete list of all files provided for a given period and split, as well as a meta data (a.k.a. header) which should include the following attributes:
	{\| class="wikitable"		{\| class="wikitable"
	\|'''Parameter'''		!'''Parameter'''
	\|'''Description'''		!'''Description'''
	\|'''~~Require~~'''		!'''Required'''
	\|'''Specified'''		!'''Specified'''
	\|'''Format / Example'''		!'''Format / Example'''
	\|'''Type'''		!'''Type'''
	\|-		\|-
	\|schema_version		\|schema_version
Line 122:		Line 112:
	\|Yes		\|Yes
	\|Nielsen		\|Nielsen
	\|S2SV1.7.0		\|<code>S2SV1.7.0</code>
	\|String		\|String
	\|-		\|-
Line 129:		Line 119:
	\|No		\|No
	\|Client		\|Client
	\|MRC = 1		\|<code>MRC = 1</code>
	\|String		\|String
	\|-		\|-
Line 137:		Line 127:
	\|Client		\|Client
	\|Format:32-bit unsigned int Unix time in seconds		\|Format:32-bit unsigned int Unix time in seconds
			Example: <code>1710154800</code>
	\|String		\|String
	\|-		\|-
Line 144:		Line 135:
	\|Client		\|Client
	\|Format:32-bit unsigned int Unix time in seconds		\|Format:32-bit unsigned int Unix time in seconds
			Example: <code>1710158399</code>
	\|String		\|String
	\|-		\|-
Line 150:		Line 142:
	\|Yes		\|Yes
	\|Client		\|Client
	\|Example: 31337		\|Example: <code>31337</code>
	\|Number		\|Number
	\|}		\|}

	'''Data delivery example for hour 11 (11:00:00 AM UTC to 11:59:59 PM UTC):'''		'''Data delivery example for hour 11 (11:00:00 AM UTC to 11:59:59 PM UTC):'''
	useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0000.json		useast1-nlsn-w-dig-sei-acme-feeds-prod/dar-exposure/ios/2022/05/25/11/acme_dtvr-exposure_a9ddf15ea054ea415718767ea6_P47C2495B-BBBA-56DE-BE99-14758F92F034_2024031111_2024031112_0000.json

Admin at 01:08, 22 June 2024

2024-06-22T01:08:44Z

← Older revision		Revision as of 01:08, 22 June 2024
Line 74:		Line 74:

	=== Success File ===		=== Success File ===
	Empty _SUCCESS file should be provided to indicate that data delivery for a particular hour and split is completed (even if there is no data for that particular hour and split).		Empty <code>'''_SUCCESS'''</code> file should be provided to indicate that data delivery for a particular hour and split is completed (even if there is no data for that particular hour and split).

	=== Manifest File ===		=== Manifest File ===