| Type |
Description |
Fixed? |
| ADDRESS_USE |
This is currently not being used in the system. |
Y |
| CAMPAIGN |
The name of the fundraising campaign associated with the marketing
promotion. For example, Fund Campaign, General Campaign, or Member
Campaign. This field is located on the Market Code Maintenance
and Marketing and Communication List Maintenance screens. |
N |
| CAMPAIGN_CLASS |
This is currently not being used in the system. |
Y |
| COMMUNICATION_CHOICE |
This is currently not being used in the system. |
Y |
| COMMUNICATION_METHOD |
This is currently not being used in the system. |
Y |
| COMMUNICATION_PURPOSE |
This is currently not being used in the system. |
Y |
| COMMUNICATION_STATUS |
This is currently not being used in the system. |
Y |
| COMMUNICATION_TYPE |
This is currently not being used in the system. |
N |
| CREATION_METHOD |
This identifies how the marketing list will be created on
the List Maintenance (MKT002) screen. Personify supports the following
list-creation methods:
Data Analyzer Query – the user selects
the Data Analyzer query to be used to select customers and/or
prospects for the list Customer Import – the user creates
a csv file that contains MASTER_CUSTOMER_ID, SUB_CUSTOMER_ID
of Customer records to be included in the list Prospect Import List – used when
the organization purchases an electronic data file that contains
customer information for prospects probably not in Personify.
Typically these data files are purchased and have rules about
how often the organization can communicate to the prospects
on the list Opt-In List – used when the customers
on the marketing list will be selected from customers on an
opt-in list Merged Lists – a new list that is
created by selecting or excluding customers on other marketing
lists. |
Y |
| CUSTOMER_DUP_FIELD |
This is used on the List Mapping (MKT001) screen. Codes are
mapped to fields in the Customer table that can be used as an
additional check to identify potential duplicates when a list
is imported. EMAIL_ADDRESS is a field that is often selected as
a field to use as an additional duplicate check. |
Y |
| CUSTOMER_TYPE |
As of 7.4.2, this is used in Mkt_List_Detail table to identify
the type of customer on a list.
The following codes are delivered with base
Personify:
· C
- Company
· I
- Individual
· H
- Household
· S
- Subgroup
· T
- Committee |
Y |
| DEPARTMENT |
Optional, user-defined code used on the MKT002 List Maintenance
screen and the MKT006 List Communication screen that allows a
user to define a department for a list or a list communication.
For organizations that have hundreds of marketing lists, it is
helpful to associate department codes to help with filtering search
results. |
N |
| EMAIL_COLUMN_SOURCE |
This is currently not being used in the system. |
Y |
| EMAIL_FORMAT |
This type code is used on MKT007 Email Message definition screen
that identifies how email messages defined in the MKT007 Email
Message Maintenance screen are to be rendered in emails sent to
customers or prospects on marketing lists. Valid values are HTML
or TXT. RTF is not being used in Personify. |
Y |
| EVENT |
This is currently not being used in the system. |
Y |
| EXCLUSION_ORDER_OBJECT |
As of 7.4.2, this is a fixed type code used on the MKT006
List Communication screen to identify customers who should be
excluded from the list. Once the user selects whether to exclude
customers based on a previous donation or order, the user identifies
whether the donation or order should be identified based on a
PRODUCT, CAMPAIGN, FUND or APPEAL, which are the valid codes.
The following codes are delivered with base
Personify:
· APPEAL
· CAMPAIGN
· FUND
· PRODUCT |
Y |
| EXCLUSION_ORDER_TYPE |
As of 7.4.2, this is a fixed type code used on the MKT006
List Communication screen to identify customers who should be
excluded from the list. With this code, the user identifies whether
customers will be excluded from the list based on a previous donation
or a previous order. If the user selects DONATION, the bill-to
customer on donation orders is excluded from the list. If the
user selects ORDER, the order line ship-to customer is excluded
from the list.
The following codes are delivered with base
Personify:
· DONATION
· ORDER |
Y |
| EXCLUSION_TIMEFRAME |
As of 7.4.2, this fixed code used for marketing lists identifies
the timeframe over which customers are to be excluded from inclusion
on the marketing list based on the other exclusion conditions.
For example, if I want to exclude customers who have made fundraising
donation, if I selected “Calendar Year” as the exclusion timeframe,
it would mean exclude customers who have made fundraising donations
in this calendar year.
The following codes are delivered with base
Personify:
· CURRENT_CY
- Current Calendar Year
· CURRENT_FY
- Current Fiscal Year
· LAST_6_MONTHS
- Last 6 months
· LAST_12_MONTHS
- Last 12 months |
Y |
| EXPENSE_TYPE |
This is currently not being used in the system. |
N |
| FAX_COMMENT_FIELD |
As of 7.4.2, this is not being used in the system. |
N |
| FAX_COVER_SHEET_CODE |
As of 7.4.2, this is not being used in the system. |
N |
| HOUSEHOLD_INCLUSION_RULE |
As of 7.4.2, if an organization is using householding (i.e.,
"Use Householding" application parameter = Y), this
fixed type code identifies whether the marketing list should include
households only or whether the list should include only households
and individuals. Valid codes are HO (Households Only) and
HI (Households and Individuals).
The following codes are delivered with base
Personify:
· HO
- Household Only
· HI
- Household and Individuals
· IO
- Individuals Only
· NONE
- No rule |
Y |
| HOUSEHOLD_LIST_RULE_CODE |
As of 7.4.2,
The following codes are delivered with base
Personify:
· HO
- Household Only
· HI
- Household and Individuals
· IO
- Individuals Only |
|
| LINK_TYPE |
This is currently not being used in the system. |
Y |
| LIST_CUSTOMER_DEFINITION |
This is currently not being used in the system. |
Y |
| LIST_DESTINATION |
This identifies if the list is going to be used by Lyris
(L) or Personify. In 7.4.2, four additional codes were implemented
to support Personify's marketing partners:
HL (Higher Logic) HR (High Road) INF (Informz) RM (Real Magnet). |
Y |
| LIST_RECORD_TYPE |
This type code used on the MKT001 List Mapping screen that
identifies whether the list to be imported contains companies
only (C), individuals only or both companies and individuals (B).
|
Y |
| LIST_SOURCE |
This user-defined code used on the MKT001 List Mapping screen
identifies the source of the "List Prospect Import"
list that will be created by importing customer records purchased
from a third-party vendor. For example, if the list comes from
your Personify database, Galaxy, or if the list was purchased.
This field is located on the Marketing and Communication List
Maintenance screen. |
N |
| LIST_SUBJECT |
User-defined code that further defines a list. For example,
Annual Conference or Membership. This field is located on the
Marketing and Communication List Maintenance screen. |
N |
| LYRIS_TEMPLATE |
This optional, user-defined code used on the List Maintenance
(MKT002) screen and the List Communication (MKT006) screen that
allows a user to define a department for a list or a list communication.
For organizations that have hundreds of marketing lists, it is
helpful to associate department codes to help with filtering search
results. For example, Template Broadcast. This field is located
on the Marketing and Communication List Maintenance screen. |
N |
| MAP_FUNCTION_TYPE |
This type code used on the List Mapping (MKT001) screen. If
a value in a list that is being uploaded needs to be transformed
to another value, a function is used. This code identifies whether
the function will use a specific value or will use a range. For
example, if the value in the field is "1" then transform
to "LOW", if the value = "2" then transform
to "HIGH". This is an example of a function that is
VALUE type of function. An example of a function that is
RANGE type of function is this: if the value is from 90-100
transform to "A", if value is from 80-89 transform to
"B", if value is from 70-79 transform to "C",
if value is from 65-69 transform to "D" and if value
is from 0-64 transform to "F". |
Y |
| MKT_TIMEFRAME |
As of 7.4.2, this is a type code used on the List Communication
(MKT006) screen to identify customers who should be excluded from
the list. The user first selects whether to exclude customers
based on a previous donation or order. With this code, the
user identifies whether the donation or order occurred during
the current CALENDAR_YEAR, the current FISCAL_YEAR, the LAST_12_MONTHS
or the LAST_6_MONTHS, which are the valid codes. |
Y |
| OPT_IN_INTEREST_AREA |
The organization can define an opt-in interest area with a
marketing communication list. This demographic type is under the
Customer subsystem. This field is located on the Marketing and
Communication List Maintenance screen. |
N |
| OPT_IN_PROCESSING |
This type code used on the List Maintenance (MKT002) screen
when a criteria is being defined for a list that includes including
or excluding customers from the list based on whether the customer
is on a selected OPT_IN list. To have customers excluded from
the list if they are on the selected opt-in list, use the code
SELECT. To have customers included on the list if they are on
the selected opt-in list, use the code SELECT. |
Y |
| OPTION_TYPE |
This is currently not being used in the system. |
Y |
| PROMOTION |
This user-defined code used on the Market Code Maintenance
(MKT005) screen that allows the user to link a market code to
an organization's promotion code. For example, Brochure, Fundraising,
General, Letter, Mailing, Meeting, Membership, or the Web. This
field is located on the Market Code Maintenance screen. |
N |
| PROSPECT_DUP_FIELD |
This type code is used on the List Mapping (MKT001) screen.
Codes are mapped to fields in the Mkt_Prospect table that can
be used as an additional check to identify potential duplicates
when a list is imported. EMAIL is a field that is often selected
as a field to use as an additional duplicate check. |
Y |
| PUBLICATION_FREQUENCY |
This is currently not being used in the system. |
N |
| PURCHASED_WITHIN_PERIOD |
This is currently not being used in the system. |
N |
| REGENERATION_FREQUENCY |
This type code used on the List Maintenance (MKT002) screen
identifies how frequently the MKT600 List Regeneration batch process
should regenerate the customers on the marketing list.
The following codes are delivered with Base
Personify:
ALWAYS DAILY MONTHLY NONE WEEKLY YEARLY |
Y |
| ROLE |
This is currently not being used in the system. |
Y |
| ROLE_CODE |
This is currently not being used in the system. |
N |
| SEND_MODE |
This type code is used on the List Communication (MKT006) screen.
It identifies whether the communication should be sent using the
customer's preferred communication method (PREFERRED) or the communication
method prioritized by the staff person (PRIORITY). If the
customer doesn't have a PREFERRED communication method, the communication
will be generated using the communication methods defined by the
staff person, in the priority order defined. |
Y |
| SIGNUP_PERIOD |
This is currently not being used in the system. |
N |
| SOURCE_CODE |
This is currently not being used in the system. |
N |
| SUBJECT |
This is currently not being used in the system. |
N |
| USAGE_LIMIT |
This type code is used on the List Maintenance (MKT002) screen
to identify whether the marketing has restricted usage. Because
organizations own the rights to all customers in their database,
list usage is typically UNLIMITED whereas a purchased LIST_IMPORT
list is usually LIMITED. A merged list that contains both LIST_IMPORT
lists and one or more other types of lists created from the organization's
own Customer records would have a usage limit of MIXED. |
Y |