Lookup tables: core
This is the set of lookup tables associated to the core data domain.
Party profile type
Party profile type indicates the type of party profile. In this example, the party profile type code is related to a prospect or consumer as it would in a retail application, but you may have patients and providers in a healthcare application.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's (IGR) |
| List of valid types of the party profile types: customer, prospect, patient, consumer, etc. |
|
|
|
| Prospect is someone that has profile information, but does not have any transactions. | ||||
| Customer (any type). |
Party profile status
This lookup is related to the status of a given profile. For example, active
and non_active
are retail-related, but deactivated
or dp_deleted
are more general and may be related to deleting a record due to a request via a California Consumer Privacy Act (CCPA) request.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's (IGR) |
| Identifies a current status of the profile (active, not active, deleted, etc.). |
|
|
|
| Active customer (transactions within N number of months). | ||||
| Non-active customer (no transactions within N number of months). | ||||
| The profile has been deactivated based on the business rules; PII (Personally Identifiable Information) erased. | ||||
| The profile has been deleted based on the DP rules; PII erased. |
Business unit (BU)
Redpoint CDP supports multiple business units if a client has that type of data where there is a BU associated to the customer. This flexibility offers the ability to load data and calculate aggregates based on a specific business unit as opposed to lumping them all together. All of the business units need to be loaded to the lookup table before data for that BU will be loaded. BU is not a required field, but it is required for processing. Due to that, there is a field for this lookup only that indicates what the default value is and that will be used when BU is not provided in a feed layout. The default is enterprise
, although that can be modified specifically for a client as well.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 | |
---|---|---|---|---|---|---|
Used in Agg Calc's (All) |
| Referenced in multiple feed layouts; BU identifies the structure of brands within an organizational entity. It is the way in which the brands within a company’s portfolio are related to, and differentiated from, one another. |
|
|
|
|
| Organizational level |
| ||||
custom value |
|
| ||||
custom value |
|
| ||||
custom value |
|
|
Address type
This indicates which address type is being loaded when you provide an address in a feed that has address as an input. This lookup table does not allow custom values.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's ( |
| The type of address, such as billing, shipping, home, business, secondary mailing address, etc. |
|
|
|
| Billing address | ||||
| Shipping address | ||||
| Home address | ||||
| Business address | ||||
| Secondary address | ||||
| Primary address | ||||
| Not provided |
Email type
These are the type codes for the “other” email values that can be provided. If someone gives a different email for shipping, it could be marked with a type indicating that.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's ( |
| The type of email address, such as billing, shipping, home, business, primary, etc. |
|
|
|
| Billing email address | ||||
| Shipping email address | ||||
| Personal email address | ||||
| Business email address | ||||
| Primary email address | ||||
| Not provided |
Phone type
This indicates the type of phone that is being provided, if it was provided for a specific reason, like billing.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's ( |
| The type of phone number, such as billing, shipping, home, business, primary, etc. |
|
|
|
| Billing phone | ||||
| Shipping phone | ||||
| Personal phone | ||||
| Business phone | ||||
| Primary phone | ||||
| Mobile phone | ||||
| Not provided |
Event disposition
Event disposition values are related to response event records. They are primarily used to identify the different email disposition values.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's ( |
| Referenced in response event feed layout. Disposition code for phone (wrong number, not valid phone, etc.), for direct mail (mail returned, undeliverable as addressed, etc.), or for email (hard bounce, soft bounce, opened, click through, delivered). |
|
|
|
| Bounced email | ||||
| Email was clicked on | ||||
| Email or mail is undeliverable | ||||
| Email was opened | ||||
| Email or Mail was processed | ||||
| Email was reported as spam | ||||
| Email was unsubscribed | ||||
| Email was sent | ||||
| Email was delivered | ||||
| Email was forwarded | ||||
| Group unsubscribes | ||||
| Group resubscribes | ||||
| Dropped email | ||||
| Not provided |
Account type
Account type code to indicate the type of account that is being provided.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
No |
| List of valid account types: ECommerce, membership, loyalty, etc. |
|
|
|
| E-commerce account | ||||
| Membership account | ||||
| Loyalty account | ||||
| Customer account | ||||
| Not provided | ||||
custom value |
| ||||
custom value |
|
Loyalty account tier
This supports the use of tiers for loyalty accounts, for example, bronze, silver, and gold. Using this lookup, you can indicate a current tier as well as the previous and next tier for a member.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's (Individual Loyalty Summary) if provided |
| Referenced in loyalty account membership feed layout; loyalty account tiers, for example: Tier Spend Range:
|
|
|
|
| Not provided | ||||
custom value |
| ||||
custom value |
| ||||
custom value |
|
Location status
This lookup indicates the status of a location. Someone may have a transaction at a closed location, and we don’t want to lose that link, so we advise clients to provide both open and closed locations. There may also be a state of “opening soon” that could be useful if you want to notify customers about a store opening near them that is not the current store that they shop at.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's |
| Identifies if the location is currently closed, open, or opening soon. |
|
|
|
| Open | ||||
| Closed | ||||
| Opening soon | ||||
| Not provided |
Location type
This indicates the type of location that is being provided. Some locations like a warehouse or headquarters may be useful to have in the CDP, but do not have a transaction or some other activity associated to them.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
Used in Agg Calc's |
| Type of location as physical, mobile, or virtual location: Examples below (could have more types):
|
|
|
|
| Brick and mortar store | ||||
| Web store | ||||
| Warehouse | ||||
| Headquarters | ||||
| Not provided | ||||
| Pharmacy | ||||
|
|
Channel
This indicates the type of channel when loading campaign event data. This helps identify the channel that the event is associated to.
Used in Agg Calc | Custom Values Allowed | Reference Information Description | Target DB object | Reference Information Data Element 1 | Reference Information Data Element 2 |
---|---|---|---|---|---|
NO |
| List of values that identify the way communications get to the end-user, the consumer (customer or prospect). |
|
|
|
| Social media | ||||
| |||||
| Direct mail | ||||
| Phone (non SMS) | ||||
| Fax | ||||
| Website | ||||
| SMS (text message) | ||||
| Channels used for data onboarding | ||||
| Other channels |