Digital Measurement SEI Data Delivery Specification

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;

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.

Item	Description	Source
App ID (AppID)	Unique ID assigned to the player/site and configured by product.	Provided by Nielsen
Integration ID (IntID)	Integration id provided by Nielsen. Used to link different integration inputs, ex. associate single audit ping integration with different viewership pipelines (dar, dtvr, dcr, etc.)	Provided by Nielsen
Partner ID (PartnerID)	Partner id provided by Nielsen. Used for the client specific S3 bucket . Please note that the sample PartnerID 'acme' used in all examples is a placeholder to be replaced with your PartnerID.	Provided by Nielsen