Creating a New List Mapping Template Paige Freeman May 06, 2024 12:52 Updated After analyzing your upload list and determining what changes need to be made in order to make the upload process easiest, you can begin creating your List Mapping Template. The Manage Prospect List Mapping page serves as the basis for the upload processing of purchased lists and formats. It also maps marketing lists for incorporation into ThreeSixty. The page can also delineate a list and allow you to perform the following activities, all of which are described in the proceeding steps: Create and store a mapping scheme for the standardized lists Define default data-level mapping rules Provide duplicate checking against the prospect and customer database tables with optional verification against a prospect user field or customer field Define the rules for list usage The mapping should have a name field (e.g., First Name, Last Name, Company Name, etc.), address 1 (if this field is not included in your mapping file, assign a Field Order of "0" and a Fixed Value of "[space]", address status code (if this field is not included in your mapping file, assign a Field Order of "0" and a Fixed Value of "BAD"), address type code (if this field is not included in your mapping file, assign a Field Order of "0" and a Fixed Value of "BLANK") at minimum to create the mapping and the same values should exist in the upload list. To define the List Mapping template: From the Marketing Central page or the left navigation, select Manage Prospect List Mapping.The Manage Prospect List Mapping page displays, as shown below. Select +New List Mapping.The Add Prospect List Mapping page displays. Select the List Source from the drop-down.This might be the organization from which the list was purchased. Values in the drop-down are populated based on the non-fixed codes defined for the MKT "LIST_SOURCE" system type. Enter the List Category.This is the vendor’s designation for the list. Select the Date Format from the drop-down.This indicates the format of dates being passed into the program by the source file. Values in the drop-down are populated based on the fixed codes defined for the APP "DATE_FORMAT" system type. If applicable, set the Active toggle to NO. In the Input File Information section, perform the following: Select the Delimited By format from the drop-down.This is a blank space, character, or other symbol that separates the beginning of the format or character string from the end. The system only supports CSV and TXT input files. If applicable, select the Enclosed By format from the drop-down.For a comma-delimited file, this identifies the mark(s) that surround the fields or other file features. For example, the fields in the file may be enclosed by quotation marks. Select the Load Record For customer type from the drop-down.Values in the drop-down are populated based on the fixed codes defined for the MKT "LIST_RECORD_TYPE" system type. The value you select from this drop-down will determine which fields you can edit in other sections. This includes the following values: Individuals: The process creates or loads individual records (Record Type = I) where the name of the individual is not null. No company records are created. Companies: The process creates company records where the name of the company is not null. No individual records are created. Both Individuals and Companies: The process creates, where possible, both individual and company records, depending on whether the Label Name and Company Name fields are populated and available. Additionally, if options are defined in the "Individual to Company Relationship" section, the system will create a relationship between the individual and company records.For example, any input record where a name and a company are specified, this results in two records with the same address but different record types. If both are loaded, then the defaults for the Classification and Status fields are user-entered for the company and individual record.Selecting the "Both Individual and Companies" option assumes that the individual and company data is located in the same row/line. For example, if you have an individual in row 2 and a company in row 3, the record will NOT be created and the process will fail. If applicable, set the Ignore Header toggle to NO.Select this option if the list you are using includes header information. When set to YES, the system ignores the information in the header. It is set to YES by default. If you selected “Individual” or “Both Individual and Companies” from the "Load Record For" field, in the Individual Record Defaults section, perform the following: Select the prospect class to be assigned to the individual customers from the Classification drop-down. Select the prospect Status to be assigned to the individual customers from the drop-down. If you selected “Companies” or “Both Individual and Companies” from the "Load Records for" field, in the Company Record Defaults section, perform the following: Select the prospect class to be assigned to company customers from the Classification drop-down. Select the prospect Status to be assigned to the company customers from the drop-down. If you selected "Both Individual and Companies" from the "Load Record For" field, in the Individual to Company Relationship section, perform the following: Select the Relationship Type from the drop-down.The relationship between the individual and the company is specified using the relationship type. For example, the relation type could be “Employment” with the individual working for the company. The Relationship Code and Reciprocal Code fields are enabled if a value is selected here. Select the Relationship Code from the drop-down.For example, if the Relationship Type is "Employment", then the Relationship Code would be "Employer". Select the Reciprocal from the drop-down.For example, if the Relationship Code is "Employer", then the Reciprocal code would be "Employee". Select Save.The Prospect List Mapping page displays. From this page, you can access the following: Prospect Duplicate Check Mapping Function Special Notes Upload History