Digital Measurement SEI User File - Revision history

DarsanaDinesh at 12:36, 26 August 2025

2025-08-26T12:36:17Z

← Older revision		Revision as of 12:36, 26 August 2025
Line 54:		Line 54:
	\|phone_number_sha256		\|phone_number_sha256
	\|Hashed phone number without country code. Remove non-numeric characters		\|Hashed phone number without country code. Remove non-numeric characters
	\|		\|Optional
	\|Example: <code>d570a9f18c3106b98dbbfc46efee736385c01464a7c47dadc5dda81ccc9fcf47</code>		\|Example: <code>d570a9f18c3106b98dbbfc46efee736385c01464a7c47dadc5dda81ccc9fcf47</code>
	\|-		\|-
	\|phone_country_code		\|phone_country_code
	\|Phone country code. Remove non-numeric characters.		\|Phone country code. Remove non-numeric characters.
	\|		\|Optional
	\|Example: <code>1</code>		\|Example: <code>1</code>
	\|-		\|-
	\|birth_date		\|birth_date
	\|Date of birth, YYYY-MM-DD		\|Date of birth, YYYY-MM-DD
	\|		\|Optional
	\|Example: <code>1970-01-01</code>		\|Example: <code>1970-01-01</code>
	\|-		\|-
	\|age_range		\|age_range
	\|Nielsen age buckets		\|Nielsen age buckets
	\|		\|Optional
	\|Example: <code>“13-17”, “18-20”, “21-24”, “25-29”, “30-34”, “35-39”, “40-44”, “45-49”, “50-54”, “55-64”, “65+”, empty if unknown</code>		\|Example: <code>“13-17”, “18-20”, “21-24”, “25-29”, “30-34”, “35-39”, “40-44”, “45-49”, “50-54”, “55-64”, “65+”, empty if unknown</code>
	\|-		\|-
Line 76:		Line 76:

	1 = male, 2 = female, 0 = other		1 = male, 2 = female, 0 = other
	\|		\|Optional
	\|Example:<code> 0, 1, 2</code>		\|Example:<code> 0, 1, 2</code>
	\|-		\|-
	\|revision_date		\|revision_date
	\|Unix epoch Date of last edit to information for this User in.Format: UTC (time in 32-bit unsigned int UTC)		\|Unix epoch Date of last edit to information for this User in.Format: UTC (time in 32-bit unsigned int UTC)
	\|		\|Optional
	\|Example: <code>1484848299</code>		\|Example: <code>1484848299</code>
	\|}		\|}

DarsanaDinesh at 12:35, 26 August 2025

2025-08-26T12:35:26Z

← Older revision		Revision as of 12:35, 26 August 2025
Line 50:		Line 50:
	\|Phone number without country code. Remove non-numeric characters.		\|Phone number without country code. Remove non-numeric characters.
	\|Optional		\|Optional
	\|Example: 4155551212		\|Example: <code>4155551212</code>
	\|-		\|-
	\|phone_number_sha256		\|phone_number_sha256
	\|Hashed phone number without country code. Remove non-numeric characters		\|Hashed phone number without country code. Remove non-numeric characters
	\|		\|
	\|Example: d570a9f18c3106b98dbbfc46efee736385c01464a7c47dadc5dda81ccc9fcf47		\|Example: <code>d570a9f18c3106b98dbbfc46efee736385c01464a7c47dadc5dda81ccc9fcf47</code>
	\|-		\|-
	\|phone_country_code		\|phone_country_code
	\|Phone country code. Remove non-numeric characters.		\|Phone country code. Remove non-numeric characters.
	\|		\|
	\|Example: 1		\|Example: <code>1</code>
	\|-		\|-
	\|birth_date		\|birth_date
	\|Date of birth, YYYY-MM-DD		\|Date of birth, YYYY-MM-DD
	\|		\|
	\|Example: 1970-01-01		\|Example: <code>1970-01-01</code>
	\|-		\|-
	\|age_range		\|age_range
	\|Nielsen age buckets		\|Nielsen age buckets
	\|		\|
	\|Example: “13-17”, “18-20”, “21-24”, “25-29”, “30-34”, “35-39”, “40-44”, “45-49”, “50-54”, “55-64”, “65+”, empty if unknown		\|Example: <code>“13-17”, “18-20”, “21-24”, “25-29”, “30-34”, “35-39”, “40-44”, “45-49”, “50-54”, “55-64”, “65+”, empty if unknown</code>
	\|-		\|-
	\|gender		\|gender
Line 77:		Line 77:
	1 = male, 2 = female, 0 = other		1 = male, 2 = female, 0 = other
	\|		\|
	\|Example: 0, 1, 2		\|Example:<code> 0, 1, 2</code>
	\|-		\|-
	\|revision_date		\|revision_date
	\|Unix epoch Date of last edit to information for this User in.Format: UTC (time in 32-bit unsigned int UTC)		\|Unix epoch Date of last edit to information for this User in.Format: UTC (time in 32-bit unsigned int UTC)
	\|		\|
	\|Example: 1484848299		\|Example: <code>1484848299</code>
	\|}		\|}
	Note: All parameters are case sensitive.		Note: All parameters are case sensitive.

DarsanaDinesh: /* Introduction */

2025-08-26T12:33:40Z

Introduction

@@ Line 5: / Line 5: @@
 This document outlines the required specification for User file if client prefers to share identity parameters in a separate file. User File  can be shared 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
+'''Example in JSON format''' (header + 1 record):
-Formatted Sample JSON Exposure file (header + 1 record):
+{
    "schemaversion": "S2SV1.0",
@@ Line 16: / Line 94: @@
    "recordcount": "1337"
+}
+{
    "publisher_user_id": "ed36968977606872e4312943c218568123786342",

DarsanaDinesh at 12:19, 26 August 2025

2025-08-26T12:19:32Z

← Older revision		Revision as of 12:19, 26 August 2025
Line 1:		Line 1:
	~~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.		{{Breadcrumb\|}} {{Breadcrumb\|Digital}} {{Breadcrumb\|Digital Ad Ratings}} {{CurrentBreadcrumb}}
			[[Category:Digital]]

			= Introduction =

			This document outlines the required specification for User file if client prefers to share identity parameters in a separate file. User File can be shared 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.		Note: All parameters are case sensitive.

DarsanaDinesh: 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...."

2025-08-26T12:15:38Z

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...."

New page

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.0",
"pid": "NLSN",
"creationtime": "1484848299",
"recordcount": "1337"
}
{
"publisher_user_id": "ed36968977606872e4312943c218568123786342",
"provider_user_id": "A769C2B-3CBD-5784-852F-C57875CC9D91A",
"first_name_sha256": "befa156f0283eb0062beb9b86e16a413e1cf8c5135e5518d5c4fa321ce0c7b6b",
"last_name_sha256": "eae8e3404182477f008479b38a6629ee86b23cefe2c418c5dc5c2f0d02af5475",
"suffix_sha256": "f04a21f9e1c244d59df2255328fb2684c83f51c09e3c53108ed766681b5f4c84",
"hem_sha256": "d120b0ef5da7458e7316ab4f25d1056575f8395d87b61b79b2cb5c9df2f5d25a",
"device_id": "A487421B-XXXX-YYYY-8343-E3BBB66E44F2",
"is_device_id_hashed": "0",
"birth_date": "1970-01-01",
"age_range": "50-54",
"gender": "2",
"revision_date": "1484848299"
}