Party profile feed layout definition

The following table represents the feed layout definition.

Required fields are marked as (Required) in the field description column; fields not marked as required are optional.

Business name	Field name	Description	Field data type/length
System of Record Name	`sor_name`	(Required) Name of the system that is the authoritative data source for a record.	`char(100)`
Source Party Profile Id	`source_party_profile_id`	(Required) This field is a natural primary key. Unique identifier generated by legacy program systems, enrollment forms, etc. to identify the creation of the profile (can be identifier generated by the system, email address, etc.). This field is used in aggregate calculations.	`char(320)`
Source System Pk 1	`source_system_pk_1`	Unique identifier generated by legacy program systems, enrollment forms, etc. to identify the creation of the consumer profile (can be identifier generated by the system, email address, etc.).	`char(320)`
Source System Pk 2	`source_system_pk_2`	Unique identifier generated by legacy program systems, enrollment forms, etc. to identify the creation of the consumer profile (can be identifier generated by the system, email address, etc.).	`char(320)`
Source System Pk 3	`source_system_pk_3`	Unique identifier generated by legacy program systems, enrollment forms, etc. to identify the creation of the consumer profile (can be identifier generated by the system, email address, etc.).	`char(320)`
Source System Pk 4	`source_system_pk_4`	Unique identifier generated by legacy program systems, enrollment forms, etc. to identify the creation of the consumer profile (can be identifier generated by the system, email address, etc.).	`char(320)`
Source System Pk 5	`source_system_pk_5`	Unique identifier generated by legacy program systems, enrollment forms, etc. to identify the creation of the consumer profile (can be identifier generated by the system, email address, etc.).	`char(320)`
Business Unit Code	`business_unit_code`	Business Unit identifies the structure of brands within an organizational entity. It is the way in which the brands within a company’s portfolio are related to, and differentiated from, one another. Values are defined as part of on-boarding, in `BUSINESS_UNIT_LOOKUP`; `NULL` values will default to `enterprise`. Refer to Business unit for details. This field is used in aggregate calculations.	`char(50)`
Source Record Create Datetime	`source_rec_create_datetime`	The datetime when the customer record was created at source system (`YYYY-MM-DD HH:mm:ss`).	`datetime`
Source Record Update Datetime	`source_rec_update_datetime`	The datetime of the latest update of the customer record at source system (`YYYY-MM-DD HH:mm:ss`).	`datetime`
Party Profile Type Code	`party_profile_type_code`	The type of the profile: patient, customer, prospect, etc. Values are defined as part of on-boarding, in `PARTY_PROFILE_TYPE_LOOKUP`. Refer to Party profile type for details. This field is used in aggregate calculations.	`char(50)`
Party Profile Status Code	`party_profile_status_code`	Identifies a current status of the customer's account (active, not active, etc.). Values are defined as part of on-boarding, in `PARTY_PROFILE_STATUS_LOOKUP`. Refer to Party profile status for details.	`char(50)`
Source Main Location Id	`source_main_location_id`	Customer's main location assigned by the client. Should be referenced in Location ID in the location feed layout. This field is used in aggregate calculations.	`char(100)`
Language Code	`language_code`	A standard language ISO 639-3 code that customer indicated as a preferred communication language (`eng`). Values listed: ISO 639-3 language codes. This field is used in aggregate calculations.	`char(3)`
Employee Indicator	`employee_ind`	Indicates whether the customer is also an employee. `y` for yes `n` for no This field is used in aggregate calculations.	`char(1)`
Employee Id	`employee_id`	Employee Number. This field is used in aggregate calculations.	`char(20)`
Prior Employee Indicator	`prior_employee_ind`	Indicates whether the customer is a former employee. `y` for yes `n` for no This field is used in aggregate calculations.	`char(1)`
Employment Start Date	`employment_start_date`	Employment start date: `YYYY-MM-DD`.	`date`
Employment End Date	`employment_end_date`	Employment end date: `YYYY-MM-DD`.	`date`
Employer Name	`employer_name`	The name of an organization or company where person is employed.	`char(250)`
Web Registered Datetime	`web_registered_datetime`	Date and time when customer first registered on the website: `YYYY-MM-DD HH:mm:ss`.	`datetime`
Profile Origin Name	`profile_origin_name`	Name of the system that originally captured customer profile, examples: the system where the customer signed up through the email signup page, or the eComm system where customer signed up for profile creation. This field is used in aggregate calculations.	`char(250)`
Marital Status	`marital_status`	Party’s marital status.	`char(50)`
Deceased Indicator	`deceased_ind`	Indicates whether the party is deceased. `y` for yes `n` for no	`char (1)`
Business Name	`business_name`	Business name of the customer (e.g., R & J Electrical).	`char(256)`
Primary Record Indicator	`primary_record_ind`	The primary record indicator is a way for the client to indicate that this record is the primary if there are multiple records for the same source system primary key. This field is used in aggregate calculations.	`char(1)`
Full Name	`full_name`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's full name. This field is used in aggregate calculations.	`char(200)`
Prefix Name	`prefix_name`	The prefix portion of the name (Mr.). This field is used in aggregate calculations.	`char(32)`
Title	`title`	Individual's title (Dr.). This field is used in aggregate calculations.	`char(30)`
First Name	`first_name`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Individual's first name. This field is used in aggregate calculations.	`char(60)`
Middle Name	`middle_name`	Individual's middle name. This field is used in aggregate calculations.	`char(40)`
Last Name	`last_name`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Individual's last name. This field is used in aggregate calculations.	`char(70)`
Suffix Name	`suffix_name`	The suffix portion of the name (Jr.). This field is used in aggregate calculations.	`char(15)`
Birth Date	`birth_date`	Profile's date of birth (`YYYY-MM-DD`). This field is used in aggregate calculations.	`date`
Gender Code	`gender_code`	Profile's gender: `m` for male `f` for female `u` for other This field is used in aggregate calculations.	`char(1)`
Address Type Code 1	`address_type_code_1`	The type of address, such as billing, shipping, home, business, secondary mailing address, etc. Values are defined as part of on-boarding, in `ADDRESS_TYPE_LOOKUP`. Refer to Address type for details. This field is used in aggregate calculations.	`char(50)`
Type 1 Address 1	`address_1_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Type 1 address line 1. This field is used in aggregate calculations.	`char(128)`
Type 1 Address 2	`address_2_1`	Type 1 address line 2. This field is used in aggregate calculations.	`char(128)`
Type 1 Address 3	`address_3_1`	Type 1 address line 3. This field is used in aggregate calculations.	`char(128)`
Type 1 Address 4	`address_4_1`	Type 1 address line 4. This field is used in aggregate calculations.	`char(128)`
Type 1 Address 5	`address_5_1`	Type 1 address line 5. This field is used in aggregate calculations.	`char(128)`
City 1	`city_1`	Type 1 city name. This field is used in aggregate calculations.	`char(64)`
State Province 1	`state_province_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Type 1 state code. This field is used in aggregate calculations.	`char(64)`
Postal Code 1	`postal_code_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Type 1 postal code. This field is used in aggregate calculations.	`char(16)`
Country Code 1	`country_code_1`	Type 1 ISO 3166 (alpha-2) 2-character country code. Defaults to `US` if not populated. This field is used in aggregate calculations.	`char(2)`
Address Type Code 2	`address_type_code_2`	The type of address, such as billing, shipping, home, business, secondary mailing address, etc. Values are defined as part of on-boarding, in `ADDRESS_TYPE_LOOKUP`. Refer to Address type for details.	`char(50)`
Type 2 Address 1	`address_1_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Type 2 address line 1.	`char(128)`
Type 2 Address 2	`address_2_2`	Type 2 address line 2.	`char(128)`
Type 2 Address 3	`address_3_2`	Type 2 address line 3.	`char(128)`
Type 2 Address 4	`address_4_2`	Type 2 address line 4.	`char(128)`
Type 2 Address 5	`address_5_2`	Type 2 address line 5.	`char(128)`
City 2	`city_2`	Type 2 city name.	`char(64)`
State Province 2	`state_province_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Type 2 state code.	`char(64)`
Postal Code 2	`postal_code_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Type 2 postal code.	`char(16)`
Country Code 2	`country_code_2`	Type 2 ISO 3166 (alpha-2) 2-character country code. Defaults to `US` if not populated.	`char(2)`
Home Phone Country Code	`home_phone_country_code`	ISO 3166 (alpha-2) 2-character country code of home phone. Defaults to `US` if not populated.	`char(2)`
Home Phone Number	`home_phone_num`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's home phone number, including area code. This field is used in aggregate calculations.	`char(32)`
Mobile Phone Country Code	`mobile_phone_country_code`	ISO 3166 (alpha-2) 2-character country code of mobile phone. Defaults to `US` if not populated.	`char(2)`
Mobile Phone Number	`mobile_phone_num`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's cell phone number, including area code. This field is used in aggregate calculations.	`char(32)`
Work Phone Country Code	`work_phone_country_code`	ISO 3166 (alpha-2) 2-character country code of work phone. Defaults to `US` if not populated.	`char(2)`
Work Phone Number	`work_phone_num`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's work phone number, including area code. This field is used in aggregate calculations.	`char(32)`
Other Phone Country Code 1	`other_phone_country_code_1`	ISO 3166 (alpha-2) 2-character country code of other phone. Defaults to `US` if not populated.	`char(2)`
Other Phone Number 1	`other_phone_num_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Other phone number, including area code. This field is used in aggregate calculations.	`char(32)`
Other Phone Number Type Code 1	`other_phone_num_type_code_1`	The type of customer's other phone number. Values are defined as part of on-boarding, in `PHONE_TYPE_LOOKUP`. Refer to Phone type for details. This field is used in aggregate calculations.	`char(50)`
Other Phone Country Code 2	`other_phone_country_code_2`	ISO 3166 (alpha-2) 2-character country code of other phone. Defaults to `US` if not populated.	`char(2)`
Other Phone Number 2	`other_phone_num_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's other phone number, including area code. This field is used in aggregate calculations.	`char(32)`
Other Phone Number Type Code 2	`other_phone_num_type_code_2`	The type of customer's other phone number. Values are defined as part of on-boarding, in `PHONE_TYPE_LOOKUP`. Refer to Phone type for details. This field is used in aggregate calculations.	`char(50)`
Personal Email Address	`personal_email_address`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's personal email address. This field is used in aggregate calculations.	`char(320)`
Personal Email Original Create Datetime	`personal_email_original_create_datetime`	The very first date when the email was captured by the client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. `YYYY-MM-DD` This field is used in aggregate calculations.	`date`
Personal Email Original Create Source Code	`personal_email_original_create_source_code`	The source that captured this email for the first time. Can be client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. This field is used in aggregate calculations.	`char(100)`
Work Email Address	`work_email_address`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's work email address. This field is used in aggregate calculations.	`char(320)`
Work Email Original Create Datetime	`work_email_original_create_datetime`	The very first date when the email was captured by the client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load might be mapped from client's DW. `YYYY-MM-DD` This field is used in aggregate calculations.	`date`
Work Email Original Create Source Code	`work_email_original_create_source_code`	The source that captured this email for the first time. Can be client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. This field is used in aggregate calculations.	`char(100)`
Other Email Address 1	`other_email_address_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's other email address. This field is used in aggregate calculations.	`char(320)`
Other Email Address Type Code 1	`other_email_address_type_code_1`	The type of customer's other email address. Values are defined as part of on-boarding, in `EMAIL_TYPE_LOOKUP`. Refer to Email type for details. This field is used in aggregate calculations.	`char(50)`
Other Email Original Create Datetime 1	`other_email_original_create_datetime_1`	The very first date when the email was captured by the client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. `YYYY-MM-DD` This field is used in aggregate calculations.	`date`
Other Email Original Create Source 1	`other_email_original_create_source_code_1`	The source that captured this email for the first time. Can be client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. This field is used in aggregate calculations.	`char(100)`
Other Email Address 2	`other_email_address_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's other email address. This field is used in aggregate calculations.	`char(320)`
Other Email Address Type Code 2	`other_email_address_type_code_2`	The type of customer's other email address. Values are defined as part of on-boarding, in `EMAIL_TYPE_LOOKUP`. Refer to Email type for details. This field is used in aggregate calculations.	`char(50)`
Other Email Original Create Datetime 2	`other_email_original_create_datetime_2`	The very first date when the email was captured by the client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. `YYYY-MM-DD` This field is used in aggregate calculations.	`date`
Other Email Original Create Source 2	`other_email_original_create_source_code_2`	The source that captured this email for the first time. Can be client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. This field is used in aggregate calculations.	`char(100)`
Other Email Address 3	`other_email_address_3`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Customer's other email address. This field is used in aggregate calculations.	`char(320)`
Other Email Address Type Code 3	`other_email_address_type_code_3`	The type of customer's other email address. Values are defined as part of on-boarding, in `EMAIL_TYPE_LOOKUP`. Refer to Email type for details. This field is used in aggregate calculations.	`char(50)`
Other Email Original Create Datetime 3	`other_email_original_create_datetime_3`	The very first date when the email was captured by the client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. `YYYY-MM-DD` This field is used in aggregate calculations.	`date`
Other Email Original Create Source 3	`other_email_original_create_source_code_3`	The source that captured this email for the first time. Can be client's source system (CRM, POS, Loyalty enrollment, etc.) for ongoing feeds. For historical load, might be mapped from client's DW. This field is used in aggregate calculations.	`char(100)`
Social Login 1	`social_login_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Login used by social media.	`char(320)`
Social Platform 1	`social_platform_1`	Name of the social media that login value corresponds to, e.g., Instagram.	`char(100)`
Social Login 2	`social_login_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Login used by social media.	`char(320)`
Social Platform 2	`social_platform_2`	Name of the social media that login value corresponds to, e.g., Instagram.	`char(100)`
Social Login 3	`social_login_3`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Login used by social media.	`char(320)`
Social Platform 3	`social_platform_3`	Name of the social media that login value corresponds to, e.g., Instagram.	`char(100)`
Social Login 4	`social_login_4`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Login used by social media.	`char(320)`
Social Platform 4	`social_platform_4`	Name of the social media that login value corresponds to, e.g., Instagram.	`char(100)`
Social Login 5	`social_login_5`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. Login used by social media.	`char(320)`
Social Platform 5	`social_platform_5`	Name of the social media that login value corresponds to, e.g., Instagram.	`char(100)`
Custom Match Attribute 1	`custom_match_attribute_1`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. User defined custom match attribute.	`char(256)`
Custom Match Attribute Name 1	`custom_match_attribute_name_1`	The name of the custom match attribute.	`char(100)`
Custom Match Attribute 2	`custom_match_attribute_2`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. User defined custom match attribute.	`char(256)`
Custom Match Attribute Name 2	`custom_match_attribute_name_2`	The name of the custom match attribute.	`char(100)`
Custom Match Attribute 3	`custom_match_attribute_3`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. User defined custom match attribute.	`char(256)`
Custom Match Attribute Name 3	`custom_match_attribute_name_3`	The name of the custom match attribute.	`char(100)`
Custom Match Attribute 4	`custom_match_attribute_4`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. User defined custom match attribute.	`char(256)`
Custom Match Attribute Name 4	`custom_match_attribute_name_4`	The name of the custom match attribute.	`char(100)`
Custom Match Attribute 5	`custom_match_attribute_5`	In order for a record to be valid, some PII data needs to be included. See Identity matching for guidance. User defined custom match attribute.	`char(256)`
Custom Match Attribute Name 5	`custom_match_attribute_name_5`	The name of the custom match attribute.	`char(100)`