|Imported lists can be rejected by SharpSpring due to poor quality.
This article will provide information on reasons for imported list failures and rejections.
To protect the deliverability of SharpSpring's customers and platform, SharpSpring blocks imports of lists that contain an unacceptable percentage of known bad emails, spam traps, hacked emails, and the like. Each email address is being checked against a database of over 2 billion email addresses that are toxic, have typos, or have a history of being purchased.
When a new email contact list is imported, SharpSpring evaluates the overall quality of the list based on a variety of factors, including an evaluation done by a third-party verification service. If 45% or more of the list contains contacts with email addresses deemed suppressed, invalid, toxic, or purchased, SharpSpring will not allow the contact list import to continue. While any list may contain a few of these email addresses, lists that are old, purchased, or otherwise of poor quality will exceed acceptable thresholds and will be blocked prior to import.
Requirements for Importing .CSV Files
The Import Tool uses information from .CSV files and creates contact lists from this information. These files contain only alphanumeric data and are presented in a table format.
Any .CSV file that you import should be structured similar to the following:
|First Name||Last Name||Is Unsubscribed|
When importing .CSV files, be aware of the following:
- Header rows are required. Header rows are necessary for mapping SharpSpring fields to imported fields.
- Email fields are required. The Import Tool requires that your .CSV file contain a column mapped to the Email field. You will still need to include the Email column when a contact does not have an email address.
- Is Unsubscribed fields are required. For SharpSpring to successfully import a .CSV file, the file needs one column header that is labeled as Is Unsubscribed. The Is Unsubscribed field should be a boolean field, where 0 is for leads who are opted in, and 1 is for leads who are not opted in.
- Utilize first and last names. For the import to be successful, a first and last name are suggested in the event that you do not have an email address for that contact. Use both as often as possible.
- Values must match. When importing custom field values, ensure that they are formatted to match the custom field values. For example, picklist and checkbox values are case-sensitive.
- When importing data with picklist and checkbox fields, the fields must be present in the file import in order to appear. Ensure that the picklist or checkbox fields in your file exist before importing. Otherwise, the data may not import properly.
For more information on how to structure .CSV files and what they should contain, refer to the following help articles:
If a list has been rejected, evaluating the source of the list to determine if the addresses are current and have opted in to receiving email is key.
After list verification is complete, attempt importing the list again. If issues still occur, contact firstname.lastname@example.org.
Important: If the contacts in this list did not directly opt in to receiving email from you, and the addresses were purchased or scraped, sending to them is against SharpSpring's Terms of Service. Importing and sending to those types of contacts can lead to deliverability problems and account termination.
When a list is rejected, the following will occur in the Import History tool:
- The rejected list event will be viewable.
- Rejected list events cannot be deleted.
- Rejected lists will appear as Import List Name—Rejected under the Contact Imported To column.
- When hovering over Details under the Error Log column, a tooltip will display the following:
The import for the list has scored in the bottom 2.5% of all lists
and was rejected due to quality concerns. Please reach out to our
compliance team or view this support article for more information.