Manually Importing Guest Data into Audiences

Whether Olo Engage is your first CRM or you’re moving from another system, importing data helps you create guest records and keep them up to date. Before you start importing, please review the proper file formatting and upload steps to make sure your import is successful.

Skip To:

• Preparing Your File
• Importing
• Mapping
• Review
• Creating Custom Fields
• Common Issues

Preparing Your File

All files being imported into the Engage CRM must:

• Be a .csv file--no other formats are accepted
• Have only one sheet
• Be smaller than 50MB
• Include a header row with column names
• Include either an email, phone number, or both
• Phone numbers should be in e164 format (+[country code][10 digit phone]). e.g. [phone]
  • If +[country code] is left out, and a valid 10 digit number is given, it will assume a US country code and prepend the +1 to the number
  • Be sure to remove any parentheses (), dashes -, or spaces from the phone numbers
• Each part of a specific date must have its own column. The month, date and year must all have its own individual column labeled with that corresponding title to fit the data in that row. 
  • For example, to include birthdays, you must have three separate columns: Birth Month, Birth Day and Birth Year. For a birthday labeled December 6, 1987 it must have 12 in the birth Month column, 6 in the birth day column and 1987 in the birth year column. 
• No special characters other than the '@' for email (e.g. no $ in front of dollar amounts)

Importing

• Navigate to Marketing → Segments in the Engage Dashboard
  • Select 'Import Data'
    
  • Select a file from your computer or drag and drop the file into the grey container.

• • Make sure you get a green check for confirmation that the upload was successful, and check the box to consent to our data import policy - select continue to proceed to the mapping step.
    • If you get an error on import, see the common issues section below.

Mapping

• Map the column headers in your .csv to the corresponding 'Wisely Property'
• There are certain 'reserved fields' that correspond to existing data fields in Engage. If your import contains those fields, be sure to map them to the existing Reserved Fields.
• If you're importing data that is not an existing Wisely Property, either map to an existing custom field or create a new one.
  • You have the option to exclude a column from the import by either selecting 'Don't import column' from the dropdown for that specific field, OR you can select 'Don't import data in unmatched columns' from the upper right of the screen to skip ALL unmatched columns.
    
  • When importing email or SMS marketing opt-ins to the existing Wisely Property, the data must match the format accepted by the Engage CRM. If it doesn't, you'll be shown a modal to map those values.
    
  • Once all of your fields are mapped or skipped, you may click continue to proceed to the Review step.
    

•  

•  

Review

• On the Review step, make sure everything looks correct, and select 'Finish'
  
• You'll be taken back to the main Import page, where you can view the status of your import and a breakdown of Successful, Failed, and Total records imported:
  • If you navigate away from this page and need to return, navigate back by clicking Marketing → Segments → Import Data. 

Creating Custom Fields

• • To create a new custom field, select 'Create new property' from the dropdown in the Wisely Property column
  • Choose a display name - this is what you'll see when mapping to this custom field on future imports
  • The internal name will be auto-generated from the display name - this will be the name of the column in the Engage database
    • If an internal name is already taken, you'll receive an error
  • Select a data type for this property
    • Boolean - will only accept True or False
    • Date - must be in mm/dd/yyyy format
    • Number - must not contain any special characters like '$'
    • String - best for text inputs
  • Select 'Create Property'
    
  • The data for your import will now be mapped to this new custom field, and it will also be available for all future .csv imports
    

Common Issues

You may encounter an error that looks like this: 

This can happen if you've already selected this file on the import step, continue to the mapping step, but back out or don't complete the upload. To resolve, simply rename your file and re-import.

Still having issues? 

Click HERE to reach out to Engage Support.