Quick Reference: Contact Import CSV
    • 3 Minutes to read
    • Dark
      Light

    Quick Reference: Contact Import CSV

    • Dark
      Light

    Article summary

    This topic gives you a quick overview of how to format a CSV file to import contacts into Mapp Engage. For more detailed information, see CSV Format for Contact Imports.

    Standard Attributes​

    Header Field

    Detailed Information

    Data Type

    user.Email

    The email must be formatted as a standard email address (localpart@domain.com).

    String

    user.MobileNumber

    The mobile number must include the area code. The plus sign (+) before the number can be included but is not required. The mobile number must not include any extra zeroes.

    String

    user.FaxNumber

    This attribute, previously used to store the fax number, now stores the mobile app alias. It accepts numbers, letters, and special characters, including periods and underscores. Mapp Engage does not validate the values in this field. The maximum character count per value is 2000 characters.

    String

    user.Identifier

    This attribute stores an external identifier (for example, from a CRM system). It accepts numbers, letters, and special characters, including periods and underscores. Mapp Engage does not validate the values in this field.

    To import files containing contacts with the external identifier, see Update Contacts with External Identifier.

    String

    user.FirstName

    This field stores the contact's first name. There are no special formatting requirements, and Mapp Engage does not validate the values in this field. The maximum character count per value is 2000 characters.

    String

    user.LastName

    This field stores the contact's last name. There are no special formatting requirements, and Mapp Engage does not validate the values in this field. The maximum character count per value is 2000 characters.

    String

    user.Nickname

    This field stores the preferred name of the contact. There are no special formatting requirements. Mapp Engage does not validate the values in this field. The maximum character count per value is 2000 characters.

    String

    user.PartnerId

    This field stores a number that identifies an external source of the contact addresses. This field is limited to a maximum of 5 numeric characters.

    Number

    user.ZipCode

    The zip code or postal code format depends on the country. In Mapp Engage, this attribute is a string field that accepts letters and numbers. Mapp Engage does not validate the values in this field. The maximum character count per value is 2000 characters.

    String

    user.ISOCountryCode

    The values must conform to the standardized ISO 3166 format.

    String

    user.ISOLanguageCode

    The values must conform to the standardized ISO 639 format.

    String

    user.TimeZone

    The values must conform to the standardized “tz“ database format, the IANA time zone database.

    For example, America/New York or Europe/Berlin.

    String

    user.Title

    These values store the preferred title as a number.

    • 1 = Mr.

    • 2 = Ms.

    • -1 = unknown

    Number

    user.DateOfBirth

    For the date of birth, use the following format: 1965-08-08 or 1965-08-08T12:00:00+00:00

    Date

    user.Gender

    These values can be set as:

    • 0 - Unset

    • 1 - Male

    • 2 - Female

    • 3- Undisclosed 

    Number

    Date formats in Mapp Engage

    Mapp Engage uses ISO-8601 date formats. Enter the time zones as follows: YYYY-MM-DDThh:mm:ss (+/-)GMT difference. For example, the time zone US/Eastern is formatted: 2012-12-25T15:15:15-05:00. ISO-8601 is recommended for formatting date information in the import file. Deprecated formats are not fully supported

    Special characters

    If your custom attribute names contain special characters, you have two options:

    • Place all items in the header in quotation marks. For example:

      • "user.CustomAttribute.My Attribute with a Space"

      • "user.CustomAttribute.Astrology / Horoscope"

    • Use square bracket notation. For example:

      • user.CustomAttribute['My Attribute with a Space']

      • user.CustomAttribute['Astrology / Horoscope']

    Do not use

    • Do not use square bracket notation for standard attributes.
      "user['Email']" causes an error during import.

    • Do not use function notation for imports.
      ${user['Email']} causes an error during import.

    Custom, Member, and Group Attributes​

    Data Type

    Reference Format

    Enumeration

    Data Type

    ​Custom Attributes​

    user.CustomAttribute.X

    Replace X with the name of the attribute.

    Custom attributes can be enumerated or not enumerated.

    String

    The maximum character count per value is 2000 characters.

    ​Member Attributes​

    user.CampaignAttribute.X

    Replace X with the name of the attribute.

    Member attributes cannot be enumerated.

    ​Group Attributes​

    The header must contain the following field names:

    "group.PropertyName","group.PropertyValue"

    The remaining rows contain the name and value of each group attribute.

    It is not possible to import group attributes as part of a CSV file that is used for contact data import. Group attributes must be imported in a separate CSV file.

    Group attributes cannot be enumerated.


    Was this article helpful?