Technical Requirements for Your Contact List Fields

To ensure all the contacts data is successfully matched with the contact fields built into Sendigram EMS, please ensure your CSV file fields (column headers) meet the following technical requirements and formatting rules.

If a column does not meet these rules, the system will flag the contacts with a Warning or Error during the import validation process.

General Formatting Guidelines

  • Column Headers: Your CSV headers should be clearly named to help you match them to the corresponding Sendigram system fields (e.g., use "Email," "First Name," "DOB").
  • Clean Data is Key: Ensure the data type for each column is consistent across all rows (e.g., the 'Age' column should only contain numbers, not text like "Thirty").

Field-Specific Validation Rules

Here are the strict rules for the core system fields we use for contact segmentation and personalization:

1. Email (The Mandatory Field)

Requirement Description Data Type Common Warning Example
Format Must strictly follow the standard email format (e.g., user@domain.com). String Random text or names: John Smith, 12345
Validation Checked against a Regular Expression (RegEx) to ensure validity.

2. First Name / Last Name

Requirement Description Data Type Common Warning Example
Length Values must typically be between 2 and 40 characters. String An email address, location name, or a phone number.
Format Cannot contain digits or most special characters. Hyphens (-) and apostrophes (') are generally allowed. Adam123 or John@Doe

3. Country / City

Requirement Description Data Type Common Warning Example
Matching Values must be present in our pre-loaded directory (whitelist) of countries and major cities. String Unknown location: Atlantis
Country Code Recommended: Specify countries using their ISO Code (e.g., US, DE, CA) for the highest accuracy.
Frequency A warning is raised if the column has an unusually high number of unique values, suggesting the column is not country/city data. A column of 100 unique names instead of cities.

4. Age

Requirement Description Data Type Common Warning Example
Value Type Must be a whole number (Integer). Number Text or dates: Thirty, 1990-01-01
Range Must be within a reasonable human age range (e.g., 13–120).

5. Date of Birth

Requirement Description Data Type Common Warning Example
Format Must follow a recognized date format (e.g., YYYY-MM-DD, DD.MM.YYYY, MM/DD/YYYY). Date Age in years: 30 years old
Range The date must be a valid date and must be in the past (e.g., generally after 1900).

6. Phone Number

Requirement Description Data Type Common Warning Example
Format Primarily composed of digits. Our system allows standard international formatting characters (+, (, ), -). String/Digits Non-digit characters: Support Team
Length Minimum of 7 digits is typically required for validation.

7. Gender

Requirement Description Data Type Common Warning Example
Whitelist Values must strictly match one of the approved categories: String Non-Binary, Neutral
Accepted Values Male, Female, Other, M, F (Matching is case-insensitive).
Still have questions?