Column Header

Details

Action

Accepted Values:

‘Add’ : to be used when a net new row is being included in the file, symbolizing a net new account

‘Update’ : to be used when an already existing row is being updated in some way

‘Delete’ : to be used when an account should be removed as an account

‘Ignore’: to be used if nothing should be done with the row. Leaving the cell blank is also accepted, defaulting to “ignore”

Company Name

Name of the account. This is the only required field when adding net new account(s).

NinjaCat ID

The unique NinjaCat ID for an existing account. This is not required when adding a net new account since a unique ID has not been given yet. This ID needs to remain for those existing accounts that you wish to update otherwise the system will not find a match to an existing account.

External ID

This field allows you to specify a unique identifier for this account.

Account Owner Email

The email associated with the user should be the Account Owner of this account. Must match the user's email or a match will not be found and an error will be thrown.

Company Website

URL of the website for the account. It needs to be in the format xyz.com

Primary Contact

Full name of account's primary contact. 

Email

Email of account's primary contact. If this is filled in and a recipient list is not defined for a report profile tied to this account, then the report will be delivered to this one Email address.

Phone Number

Phone number of account's primary contact.

Custom Field

This field allows you to specify the {@CUSTOM_FIELD} placeholder that can be used in a template or the email body of a scheduled report.

Dashboard Profile

Exact match of the Dashboard Profile name that should be assigned to this account. If a match is not found, an error will be thrown.

Date Format

If no value is given here, the system will default to the value given in the agency-level localization settings. An accepted value is an integer from 1-7. See the key below for what the integers represent: 

1 = 03/01/2000

2 = 03-01-2000

3 = 01/03/2000

4 = 01-03-2000

5 = 2000/03/01

6 = 2000-03-01

7 = 20000301

Digit Format

If no value is given here, the system will default to the value given in the agency-level localization settings. An accepted value is an integer from 1-6. See the key below for what the integers represent:

1 = 1,000.00

2 = 1.000,00

3 = 1 000.00

4 = 1 000,00

5 = 1000.00

6 = 1000,00

Time Zone

If a value is not provided here, then the system will apply the timezone that is set in the agency-level localization settings. Otherwise, an overridden timezone can be given for a particular account. Accepted timezones:

"Pacific/Samoa" "America/Adak" "Pacific/Marquesas" "America/Anchorage" "America/Los_Angeles" "America/Denver" "America/Phoenix" "America/Chicago" "America/New_York" "America/Caracas" "America/Glace_Bay" "America/St_Johns" "America/Sao_Paulo "America/Noronha" "Atlantic/Azores" "Europe/London" "Europe/Brussels" "Asia/Damascus" "Europe/Moscow" "Asia/Tehran" "Europe/Samara" "Asia/Kabul" "Asia/Yekaterinburg" "Asia/Kolkata" "Asia/Katmandu" "Asia/Novosibirsk" "Asia/Rangoon" "Asia/Krasnoyarsk" "Australia/Perth" "Australia/Eucla" "Asia/Chita" "Australia/Adelaide" "Asia/Vladivostok" "Australia/Lord_Howe" "Asia/Magadan" "Pacific/Norfolk" "Pacific/Fiji" "Pacific/Chatham" "Pacific/Tongatapu" "Pacific/Kiritimati"

Call Tracking Conversion Period

The number of days that must pass before a repeat caller is eligible to convert. Min: 0 days, Max: 90 days. Numeric value accepted, example: "30" If no value is given here, the system will default to the value given in the agency-level settings. If a value is given that doesn't fall in the accepted values, an error will be thrown.

Call Tracking Conversion Threshold

The number of seconds that must pass before a caller converts. Min: 0 seconds, Max: 99999 seconds. Numeric value accepted, example: "60" If no value is given here, the system will default to the value given in the agency-level localization settings. If a value is given that doesn't fall in the accepted values, an error will be thrown.

[Account Groups to follow in subsequent columns; 1 per column]

The shell of an Account Group must exist in the platform before values can be assigned to accounts under that Account Group. In each respective Account Group column, the appropriate value can be assigned to an account; limited to 1 value per Account Group per Account. Already existing values will be accepted, and net new values can be given here as well (as long as the Account Group already exists in the system and was given as a column header in the file). An error will be thrown if an Account Group is presented as a new column in the file when it doesn't already exist in the system.