New pages
- 18:47, 28 August 2025 Third Party Encoding Vendors (hist | edit) [197 bytes] DavidPortalatin (talk | contribs) (Created page with "{| class="wikitable sortable" |- ! Client Name !! Client Type !! |- | '''7Miles''' || '''Third_Party_Encoding_Facilities_2025-06-30''' |-")
- 17:12, 28 August 2025 Third Party Encoding Facilities (hist | edit) [19 bytes] AmySockanathan (talk | contribs) (Creating new page for Third Party Encoding Facilities)
- 12:15, 26 August 2025 Digital Measurement SEI User File (hist | edit) [3,776 bytes] DarsanaDinesh (talk | contribs) (Created page with "Identity parameters can be provided in a separate User File updated each time a new user enters the subset of users exposed to an ad or upon updating an existing users registration records. The User file maps the publisher_user_id to the pertinent identity parameters. The User file appends new rows for each new publisher_user_id. Note: All parameters are case sensitive. JSON Examples Formatted Sample JSON Exposure file (header + 1 record): { "schemaversion": "S2SV1....")
- 18:45, 23 July 2025 Nielsen Audio Code Analysis Tool 3 for TV (hist | edit) [1,586 bytes] AmySockanathan (talk | contribs) (NACAT3 - Nielsen Audio Code Analysis Tool page for TV)
- 14:31, 22 July 2025 Digital Measurement SEI Data Delivery Specification (hist | edit) [4,089 bytes] DarsanaDinesh (talk | contribs) (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...")
- 16:49, 16 July 2025 SEI Ad Audit Ping (hist | edit) [3,966 bytes] DarsanaDinesh (talk | contribs) (Created page with "The Nielsen Server-to-Server (S2S) solution needs audit pings for audience validation. The audit pings are https requests that are fired at least once per session. It primarily contains URL parameters with a randomly generated Session Identifier, Integration Identifier, and a timestamp that is matched to the server-side traffic.")
- 16:47, 16 July 2025 Digital Measurement Ads Audit Beacon (hist | edit) [330 bytes] DarsanaDinesh (talk | contribs) (Created page with "The Nielsen Server-to-Server (S2S) solution needs audit pings for audience validation. The audit pings are https requests that are fired at least once per session. It primarily contains URL parameters with a randomly generated Session Identifier, Integration Identifier, and a timestamp that is matched to the server-side traffic.")