02. Standard Fields and Custom Fields

The Standard Fields and the Custom Fields attach a label to every column in your Contact Database. The Standard Fields are preset in the MindFire Platform and are fields that are common to many Contact Databases (e.g. First Name, Last Name, Email Address, etc.). 

Custom Fields are fields that you create manually in any subaccount. You can add any number of Custom Fields to your Contact database to hold account-specific information about your Contacts.

Tip: 

Both Standard and Custom Fields can be used to control the personalized URL or as parameters for the deduplication rules.

Note: 

There are also predefined custom fields that are required to be leveraged in the BluePrint Editor Campaigns.

Instructions:

Editing Standard Field Properties

Some properties of Standard Fields can be edited

Click the pencil next to the Field Name of the field that you would like to edit

Field Name: Cannot be modified

Type: This explains the type of data that is expected in this field

• String: Any alpha-numeric character(s)

• Integer: A number with no decimal/fraction

• Decimal: A number that may or may not have a decimal

• DateTime: A number in a date and/or time format

• Bool (aka "Boolean"): Either TRUE or FALSE

Used to create PURL: Select this if this field is to be included in generating the personalized URL for each Contact.

Used to de-dupe Contacts: Select this if this field is to be included in the deduplication group.

Required: A validation error will be displayed if a required field is empty.

Accept only certain data: Enter the regex (regular expression) validation you would like to use. If any imported Contact fails this validation, you will see a validation error message after mapping your Contact data.

Creating Custom Fields

1. Click on Contact Management

2. Click on Contact Fields

3. Click on the "New Custom Field" button

The Edit Custom Field screen appears with the following fields:

Field Name: Must be unique, cannot have spaces

Description: A brief explanation of the information is expected in this field

Type: This explains the type of data that is expected in this field

• String: Any alpha-numeric character(s)

• Integer: A number with no decimal/fraction

• Decimal: A number with a decimal

• DateTime: A number in a date and/or time format

• Bool (aka "Boolean"): Either TRUE or FALSE

Length: A limit for the number of characters this field will accept

Tip: 

A value of zero in the Length field means there is no limit.

Used to create PURL: Select this if this field is to be included in generating the personalized URL for each Contact

• NotUsedToGeneratePURL

• UsedAsFirstPartOfPURL

• UsedAsSecondPartOfPURL

• UsedAsThirdPartOfPURL

• UsedAsFourthPartOfPURL

• UsedAsFifthPartOfPURL

• UsedAsSixthPartOfPURL

• UsedAsSeventhPartOfPURL

• UsedAsEighthPartOfPURL

• UsedAsNinthPartOfPURL

Used to de-dupe Contacts: Select this if this field is to be included in the deduplication group

• NotUsedToDedupMyContacts

• IncludeThisFieldInMyFirstGroup

• IncludeThisFieldInMySecondGroup

• IncludeThisFieldInMyThirdGroup

• IncludeThisFieldInMyFourthGroup

• IncludeThisFieldInMyFifthGroup

• IncludeThisFieldInMySixthGroup

• IncludeThisFieldInMySeventhGroup

• IncludeThisFieldInMyEighthGroup

• IncludeThisFieldInMyNinthGroup

Required: A validation error will be displayed if a required field is empty

Accept only certain data: Enter the regex (regular expression) validation you would like to use. If any imported Contact fails this validation, you will see a validation error message after mapping your Contact data.

Encrypted: Check this box if you would like this field to be encrypted when stored in the database.

4. Click "OK"

Note: 

Once a Custom Field has been added, it can be edited, but it cannot be removed.