Contact authorization feed layout definition
The following table represents the feed layout definition.
Required fields are marked as (Required) in the field description column; fields not marked as required are optional.
Business name | Field name | Description | Field data type/length |
---|---|---|---|
System of Record Name |
| (Required) Name of the system that is the authoritative data source for a record. |
|
Authorization Date Time |
| (Required) This field is a natural primary key. A date time when the preference was captured by the source system: This field is used in aggregate calculations. |
|
Business Unit Code |
| This field is a natural primary key. Business Unit (BU) identifies the structure of brands within an organizational entity. When provided, permission or preference is applied only to that BU, otherwise it's enterprise-wide (in the case of multi-BU clients). This field is used in aggregate calculations. Values are defined as part of on-boarding, in |
|
Contact Level Type Code |
| (Required) This field is a natural primary key. Contact level type identifies a level the preference or permission is for: global level, email, phone, direct mail address, SMS, etc. This field is used in aggregate calculations. Valid values are:
|
|
Contact Level Value |
| (Required) This field is a natural primary key. The contact item that a permission or preference is being provided for:
This field is used in aggregate calculations. |
|
Contact Level Additional Code |
| Can be used for an ISO 3166 (alpha-2) 2-character country code when |
|
Authorization Code |
| (Required) This field is a natural primary key. Authorization values that indicate permission to contact ( This field is used in aggregate calculations. Valid values are:
|
|
Authorization Value |
| This field is a natural primary key. The value of permission or preference code, for example: Newsletter / Catalog / Specials, or any other value for preference types like preferred contact language. This field is used in aggregate calculations. |
|
Authorization Frequency |
| This field is a natural primary key. When specifically noted, the frequency at which contact is authorized through a channel defined in this record contact level type code and value. This field is used in aggregate calculations. |
|
Address 1 |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. Address Line 1 |
|
Address 2 |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. Address Line 2 |
|
Address 3 |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. Address Line 3 |
|
Address 4 |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. Address Line 4 |
|
City |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. City Name |
|
State Province |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. State Code |
|
Postal Code 1 |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. Postal Code 1 |
|
Postal Code 2 |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. Postal Code 2 |
|
Country Code |
| Combined address fields are treated as a single Contact Level Value and are a natural primary key. ISO 3166 (alpha-2) 2-character country code |
|
Double Verification Indicator |
| This field is a natural primary key. Indicates double opt-in. Double opt-in is a type of email subscription where a user should confirm his or her consent to be added to the mailing list twice. This field is used in aggregate calculations. Valid value is |
|