Digital Measurement SEI User File

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"

}