Digital Measurement SEI Data Delivery Specification - Revision history

DarsanaDinesh at 13:36, 28 October 2025

2025-10-28T13:36:52Z

← Older revision		Revision as of 13:36, 28 October 2025
Line 58:		Line 58:
	To see a list of the files in your designated folder:		To see a list of the files in your designated folder:
	<code>aws s3 ls s3://<bucket-name>/<prefix>/</code>		<code>aws s3 ls s3://<bucket-name>/<prefix>/</code>

	To list all the files in all the sub folders as well:		To list all the files in all the sub folders as well:
	<code>aws s3 ls s3://<bucket-name>/<prefix>/ --recursive</code>		<code>aws s3 ls s3://<bucket-name>/<prefix>/ --recursive</code>

	''Example:''		''Example:''
	<code>aws s3 ls s3://useast1-nlsn-w-dig-sei-partnera-feeds-prod/dar-exposure/ --recursive</code>		<code>aws s3 ls s3://useast1-nlsn-w-dig-sei-partnera-feeds-prod/dar-exposure/ --recursive</code>

DarsanaDinesh: /* Introduction */

2025-10-28T13:35:56Z

Introduction

← Older revision		Revision as of 13:35, 28 October 2025
Line 15:		Line 15:
	* Large data file can be partitioned into multiple parts with min size of 128MB - 256MB		* Large data file can be partitioned into multiple parts with min size of 128MB - 256MB
	* Data can be delivered separately in multiple splits(platforms), if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the S2S system;		* Data can be delivered separately in multiple splits(platforms), if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the S2S system;
			** For streaming content - it is important to split the data by platform as per the spec above, as today we have an internal constraint that requires OTT to be processed separately due to methodology differences. C&M platforms can be combined under one app_id.

	==Prerequisites ==		==Prerequisites ==

DarsanaDinesh at 11:44, 6 August 2025

2025-08-06T11:44:03Z

← Older revision		Revision as of 11:44, 6 August 2025
Line 13:		Line 13:
	*** PARQUET format(.parquet) --- Preferred;		*** PARQUET format(.parquet) --- Preferred;
	* All files should have extensions to indicate the file format (.json or .parquet)		* All files should have extensions to indicate the file format (.json or .parquet)
	* ~~Data~~ file can be partitioned into multiple parts with min size of 128MB - 256MB		* Large data file can be partitioned into multiple parts with min size of 128MB - 256MB
	* Data can be delivered separately in multiple splits(platforms), if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the S2S system;		* Data can be delivered separately in multiple splits(platforms), if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the S2S system;

DarsanaDinesh: /* AWS to AWS Integration */

2025-07-22T14:58:13Z

AWS to AWS Integration

← Older revision		Revision as of 14:58, 22 July 2025
Line 61:		Line 61:
	''Example:''		''Example:''
	<code>aws s3 ls s3://useast1-nlsn-w-dig-sei-partnera-feeds-prod/dar-exposure/ --recursive</code>		<code>aws s3 ls s3://useast1-nlsn-w-dig-sei-partnera-feeds-prod/dar-exposure/ --recursive</code>

	'''2. Copy a Single File (cp)'''		'''2. Copy a Single File (cp)'''

DarsanaDinesh at 14:53, 22 July 2025

2025-07-22T14:53:10Z

← Older revision		Revision as of 14:53, 22 July 2025
Line 1:		Line 1:
	~~Introduction~~		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{CurrentBreadcrumb}}
			[[Category:Digital]]

			=Introduction=
	This document outlines the data delivery specification for Ad and Content Measurement products via SEI integration.		This document outlines the data delivery specification for Ad and Content Measurement products via SEI integration.

	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 outlined in this spec 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.
	Supported ~~format~~ are:		* Supported formats are:
	Uncompressed text files with utf-8 encoding in JSON ~~lines~~ format;		** Uncompressed text files with utf-8 encoding in:
	~~Apache Parquet~~ format (~~snappy compression is optional~~);		*** JSON format(.json);
	All files should have extensions to indicate the file format (.json \| .parquet)		*** PARQUET format(.parquet) --- Preferred;
	Data file can be partitioned into multiple parts with min size of 128MB - 256MB		* All files should have extensions to indicate the file format (.json or .parquet)
	Data can be delivered separately in multiple splits, if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the ~~SEI~~ system;		* Data file can be partitioned into multiple parts with min size of 128MB - 256MB
			* Data can be delivered separately in multiple splits(platforms), if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the S2S system;

	== Prerequisites ==		==Prerequisites ==
	To get started, you will need a Nielsen App ID. The App ID is a unique ID assigned to your app. This will be provided to you by your assigned Technical Account Manager upon starting the integration.		To get started, you will need a Nielsen App ID. The App ID is a unique ID assigned to your app. This will be provided to you by your assigned Technical Account Manager upon starting the integration.
	{\| class="wikitable"		{\| class="wikitable"
	!Item		!Item
	!Description		!Description
	!Source		!Source
Line 33:		Line 36:
	\|Provided by Nielsen		\|Provided by Nielsen
	\|}		\|}
			The onboarding process varies depending on the client's cloud environment.

			=== '''AWS to AWS Integration''' ===
			'''Prerequisites'''

			* The client's IAM Role ARN to grant access to Nielsen S3 bucket provided by client.


			'''Onboarding steps to be performed by client'''

			# Create an IAM user or role in client AWS account.
			# Attach the following IAM policy to the user or role to grant necessary permissions. This policy allows the user or role to read, write, and manage object access control lists (ACLs) in the specified S3 bucket. <code>{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:GetObject", "s3:PutObject", "s3:PutObjectAcl" ], "Resource": "arn:aws:s3:::<AccountABucketName>/" } ] }</code> '''Note:''' Replace <code><AccountABucketName></code> with the bucket name provided by Nielsen. You can also restrict access to a specific folder by modifying the <code>Resource</code> element (e.g., <code>"arn:aws:s3:::AccountABucketName/FolderName/"</code>). Check <nowiki>https://repost.aws/knowledge-center/cross-account-access-s3</nowiki> for more details.
			# '''Share''' the '''IAM Role ARN''' to us.


			Once you received S3 bucket information from Nielsen, perform the following steps to test access.

			'''1. List Files (ls)'''

			To see a list of the files in your designated folder:
			<code>aws s3 ls s3://<bucket-name>/<prefix>/</code>
			To list all the files in all the sub folders as well:
			<code>aws s3 ls s3://<bucket-name>/<prefix>/ --recursive</code>
			''Example:''
			<code>aws s3 ls s3://useast1-nlsn-w-dig-sei-partnera-feeds-prod/dar-exposure/ --recursive</code>
			'''2. Copy a Single File (cp)'''

			To upload a single file from your local machine to S3:
			<code>aws s3 cp yourfile.txt s3://<bucket-name>/<prefix>/</code>
			<code>''This command copies filename.csv to your s3 bucket at prefix folder.''</code>
			'''3. Sync a Directory (sync)'''

			To upload all new or updated files from a local directory to your S3 folder:
			<code>aws s3 sync /path/to/your/local/directory s3://<bucket-name>/<prefix>/</code>
			''This command uploads all the files in your directory to your s3 bucket folder.''

DarsanaDinesh at 14:33, 22 July 2025

2025-07-22T14:33:01Z

@@ Line 1: / Line 1: @@
 Introduction
 This document outlines the data delivery specification for Ad and Content Measurement products via SEI integration.
@@ Line 11: / Line 12: @@
 Data file can be partitioned into multiple parts with min size of 128MB - 256MB
 Data can be delivered separately in multiple splits, if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the SEI system;

DarsanaDinesh: Created page with "Introduction This document outlines the data delivery specification for Ad and Content Measurement products via SEI integration. 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. All prefix labels and file names should be lowercase except for app ids. Supported format are: Uncompressed text files with utf-8 encoding in JSON lines format; Apache Parquet forma..."

2025-07-22T14:31:04Z

Created page with "Introduction This document outlines the data delivery specification for Ad and Content Measurement products via SEI integration. 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. All prefix labels and file names should be lowercase except for app ids. Supported format are: Uncompressed text files with utf-8 encoding in JSON lines format; Apache Parquet forma..."

New page

Introduction
This document outlines the data delivery specification for Ad and Content Measurement products via SEI integration.

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.

All prefix labels and file names should be lowercase except for app ids.
Supported format are:
Uncompressed text files with utf-8 encoding in JSON lines format;
Apache Parquet format (snappy compression is optional);
All files should have extensions to indicate the file format (.json | .parquet)
Data file can be partitioned into multiple parts with min size of 128MB - 256MB
Data can be delivered separately in multiple splits, if needed due to organizational, technical or privacy requirements. This allows to permission s3 access separately, to process data independently and to persist data partitioned, within the limits of the SEI system;