Appendix: Input table schema | Redpoint Documentation

The Redpoint Identity Studio (RIS) INPUT table (snapshot) must contain the following columns. All columns are optional except for ID.

Column	Type	Description
`ID`	`NVARCHAR(32)`	(Required) Unique ID of record
`CUST_GID`	`NVARCHAR(32)`	Customer group ID (optional; used to compare match results to legacy)
`NAME1`	`NVARCHAR(64)`	Name (may contain multiples)
`FNAME1`	`NVARCHAR(32)`	First name
`MNAME1`	`NVARCHAR(32)`	Middle name
`LNAME1`	`NVARCHAR(32)`	Last name
`GENERATION1`	`NVARCHAR(8)`	JR, SR, etc.
`GENDER1`	`VARCHAR(1)`	M/F/blank
`DATE_OF_BIRTH1`	`DATE`	Date of birth
`NAME2`	`NVARCHAR(64)`	Name (may contain multiples)
`FNAME2`	`NVARCHAR(32)`	First name
`MNAME2`	`NVARCHAR(32)`	Middle name
`LNAME2`	`NVARCHAR(32)`	Last name
`GENERATION2`	`NVARCHAR(8)`	JR, SR, etc.
`GENDER2`	`VARCHAR(1)`	M/F/blank
`DATE_OF_BIRTH2`	`DATE`	Date of birth
`NAME3`	`NVARCHAR(64)`	Name (may contain multiples)
`FNAME3`	`NVARCHAR(32)`	First name
`MNAME3`	`NVARCHAR(32)`	Middle name
`LNAME3`	`NVARCHAR(32)`	Last name
`GENERATION3`	`NVARCHAR(8)`	JR, SR, etc.
`GENDER3`	`VARCHAR(1)`	M/F/blank
`DATE_OF_BIRTH3`	`DATE`	Date of birth
`ADDRESS1`	`NVARCHAR(64)`	Address first line
`CITY1`	`NVARCHAR(64)`	City name
`PROVINCE1`	`NVARCHAR(64)`	Province (state) name
`POSTCODE1`	`VARCHAR(10)`	Postal (zip) code
`COUNTRY1`	`NVARCHAR(32)`	First address country name or code This is required if you’re validating any addresses outside of the U.S.
`ADDRESS2`	`NVARCHAR(64)`	Address first line
`CITY2`	`NVARCHAR(64)`	City name
`PROVINCE2`	`NVARCHAR(64)`	Province (state) name
`POSTCODE2`	`VARCHAR(10)`	Postal (zip) code
`COUNTRY2`	`NVARCHAR(32)`	Second address country name or code If using `ADDRESS2`, this is required if you’re validating any addresses outside of the U.S.
`ADDRESS3`	`NVARCHAR(64)`	Address first line
`CITY3`	`NVARCHAR(64)`	City name
`PROVINCE3`	`NVARCHAR(64)`	Province (state) name
`POSTCODE3`	`VARCHAR(10)`	Postal (zip) code
`COUNTRY3`	`NVARCHAR(32)`	Third address country name or code If using `ADDRESS3`, this is required if you’re validating any addresses outside of the U.S.
`PHONE1`	`VARCHAR(24)`	Mobile phone or primary phone
`PHONE2`	`VARCHAR(24)`	Other phone number
`PHONE3`	`VARCHAR(24)`	Other phone number
`EMAIL1`	`NVARCHAR(320)`	Email address
`EMAIL2`	`NVARCHAR(320)`	Email address
`EMAIL3`	`NVARCHAR(320)`	Email address
`SOCIAL1`	`NVARCHAR(256)`	Social media handle
`SOCIAL2`	`NVARCHAR(256)`	Social media handle
`SOCIAL3`	`NVARCHAR(256)`	Social media handle
`ACCOUNT`	`NVARCHAR(64)`	Customer-defined account field
`OTHER1`	`NVARCHAR(256)`	Customer-defined field
`OTHER2`	`NVARCHAR(256)`	Customer-defined field
`OTHER3`	`NVARCHAR(256)`	Customer-defined field

Fields with numeric suffixes (1, 2, 3) represent alternate values for the same data type. The matching algorithm considers all alternates when comparing records; for example, if any of EMAIL1, EMAIL2, or EMAIL3 matches between two records, that contributes to the match score. Alternates are useful for capturing changed address or alternate contact methods.
Parsed name fields (FNAME, MNAME, LNAME, GENDER, GENERATION) may be used if your name data has been pre-parsed. The AI-generated SQL prompt in the onboarding wizard will guide you on the correct column mapping for your data.