List Loading

Loading records into systems of record often has unintended consequences: duplicates can be created, data isn’t in alignment with existing values, and unintended processes can be triggered. Openprise enables lists to be cleaned, segmented, and enriched prior to loading. In addition, leads on a list can be matched to existing records or new records can be created if they don’t already exist.

For companies with multiple processes, different list load apps can be created, such as unique processes for a given vendor or partner and for internal company use. With Openprise’s App Factory, you can also create specific apps to be used by different teams, partners, or vendors, all without logging into the Openprise platform.

Prerequisites

1. Data Essentials is recommended as a prerequisite to List Loading so that duplicates are not created by failing to match due to uncleaned data.
2. Create a template with the data columns you’ll likely have in your lists using Google Sheets. Import this template as a data source. Typical to include in your template are name, email, address, city, state, postal code, country, phone, company, source, and campaign ID (specific to Salesforce).
3. Determine matching methods you will use to match records from your list to existing records in your source system. Common match methods include matching records by email, website, company name & country, company name & first and last name. 
4. Create one Data Target to update existing records, and another to add new records. Include fields from your template that need to be updated or added. 

Create List Load Jobs

1. Prep fields - create a job that cleans and normalizes fields from your template so they have a better chance of matching to existing records. Prepping fields also helps with the creation of new records.  
2. Reject records - create a job that rejects records where required fields contained null values. Common reject reasons include, duplicate records, and records that do not contain email, or company name. Rejected records can be stored in a manual data source for further review. 
3. Match to existing records - build a job that matches records from your list to records in your source system using pre-determined match methods. Your job should contain several match methods using the Infer Value task template. Having more than one match method gives records in your list a higher chance of being matched to existing records. 
4. Update/ add records - you should create a separate job to update existing records and another job to add new records. 

Loading Lists in App Factory

Create a list loading app in App Factory to load lists. Configure the app to automatically run your list load bot each time a list is loaded. List files must be formatted exactly as the template. Build the app to display the total number of records, the number of rejected records, new records, and existing records per file. The app should also display a timestamp for when the list was submitted, the status of the list, and who it was submitted by. 

Reviewing Lists in App Factory

Create a search & edit app in App Factory to review each list in detail. Configure the app to show information about each field from the template. Include fields showing information about records that were added, updated, rejected, and records that failed to be exported. Filter the app to display records from specific lists, or by lists loaded in a specific timeframe.