The data warehouse uses the Person field layout to describe visitors that have been uniquely identified with first-party cookies, their email addresses, or some other identifier.
The Person field layout uses the following tables to describe your visitors:
person table
Field name | Sortable | Description | |
|---|---|---|---|
active | BOOLEAN | ๐ | The person is a unique entity; |
anonymous_visitor | BOOLEAN | ๐ | Person without any identity information, such as an email address or account ID |
articles_remaining | INT (4 bytes) | ๐ | Number of articles available for person to access, usable with free previews or limited subscriptionsโoptional and provided externally |
do_not_track | BOOLEAN | ๐ | Indicates whether or not the person has opted out of tracking and personalization |
engagement_score | INT (4 bytes) | ๐ | Numeric representation of this personโs engagement with the brand that is calculated by customer-specific rules (for example, a visitor with a newsletter subscription is more engaged than a periodic visitor); calculated here as the sum of all engagement scores at the event level over a 90-day period |
external_score | INT (4 bytes) | ๐ | Rating value not created or defined by Personalization |
first_time_visitor | BOOLEAN | ๐ | Indicates whether person is a first-time visitor |
first_touch | DATE | โ | Time and date of the personโs first touch |
id | INT (4 bytes) | โ | Unique person ID: Personalization internal value;
|
identifiers_json | VARCHAR (65535) | ๐ | A JSON representation of all the identifiers associated with the person |
last_modified_date | TIMESTAMP | ๐ | Time and date the row was last modified |
last_subscription_plan | VARCHAR (50) | ๐ | Immediately previous subscription plan for the person (for example,
|
last_touch | DATE | โ | Time and date of the personโs last touch |
persona | VARCHAR (100) | ๐ | The top persona of the person, based on their consumed content |
primary_identifier | VARCHAR (200) | ๐ | Tracking ID assigned to a website visitor and stored in their cookies; if there are multiple identifiers, this field reflects the first assigned identifier |
primary_identifier_type_id | INT (4 bytes) | ๐ | Personโs identifier typeโthis will always have a value of 2 to reflect the first tracking ID assigned by Personalization |
subscriber_status | VARCHAR (50) | ๐ | The personโs subscription statusโoptional and provided externally |
subscription_end_date | DATE | ๐ | Date the personโs subscription expiresโoptional and provided externally |
subscription_plan | VARCHAR (50) | ๐ | Current personโs subscription planโoptional and provided externally |
subscription_start_date | DATE | ๐ | Date the personโs subscription startedโoptional and provided externally |
db_last_modified_date | TIMESTAMP | ๐ | The UTC time and date when the row was last modified in the database |
custom_field_1 | VARCHAR (1000) | ๐ | User-defined field Since this field is also used by Personalization, Acquia recommends you donโt use the field for your custom values. |
custom_field_2 | VARCHAR (1000) | ๐ | User-defined field Since this field is also used by Personalization, Acquia recommends you donโt use the field for your custom values. |
custom_field_3 | VARCHAR (1000) | ๐ | User-defined field Since this field is also used by Personalization, Acquia recommends you donโt use the field for your custom values. |
custom_field_4 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_5 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_6 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_7 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_8 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_9 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_10 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_11 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_12 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_13 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_14 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_15 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_16 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_17 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_18 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_19 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_20 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_21 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_22 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_23 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_24 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_25 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_26 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_27 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_28 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_29 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_30 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_31 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_32 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_33 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_34 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_35 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_36 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_37 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_38 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_39 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_40 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_41 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_42 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_43 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_44 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_45 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_46 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_47 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_48 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_49 | VARCHAR (1000) | ๐ | User-defined field |
custom_field_50 | VARCHAR (1000) | ๐ | User-defined field |
person_link table
Field name | Sortable | Description | |
|---|---|---|---|
db_last_modified_date | TIMESTAMP | ๐ | The UTC time and date when the row was last modified in the database |
linked_person_id | INT (4 bytes) | ๐ | Points to a person associated with the visitor listed in this recordโs
|
person_id | INT (4 bytes) | โ | Points to a specific person in Personalization records |
Note
If multiple person records have been joined together as a result of an
identity merge, only one of the person records in this table will have
an active flag set to Y. The other linked persons will have the
active flag set to N.
person_identifier table
Field name | Sortable | Description | |
|---|---|---|---|
active | BOOLEAN | ๐ | The person is a unique entity; |
db_last_modified_date | TIMESTAMP | ๐ | The UTC time and date when the row was last modified in the database |
identifier | VARCHAR (200) | โ | Personโs identifier information, based on the
|
last_modified_date | TIMESTAMP | ๐ | The timestamp of the last modification of this record |
person_id | INT (8 bytes) | โ | Points to a specific person in Personalization records |
person_identifier_type_id | INT (4 bytes) | โ | Personโs identifier type, from the following options: 1 - email Note If you have added one or more custom identifiers to your customer
information, those non-standard identifiers will have values greater
than six. Currently, there is no method to determine a custom
identifierโs descriptive name from its |
person_ranking_item table
Field name | Sortable | Description | |
|---|---|---|---|
db_last_modified_date | TIMESTAMP | ๐ | The UTC time and date when the row was last modified in the database |
item_date | INT (4 bytes) | โ | Date for which the ranking itemโs value has been accumulated |
item_name | VARCHAR (200) | โ | Name of the ranking itemโfor example, |
item_value | INT (4 bytes) | ๐ | Value assigned to the ranking item |
last_modified_date | TIMESTAMP | ๐ | Time and date that the row was last modified |
person_id | INT (8 bytes) | ๐ | Points to an associated ranking item |
person_ranking_id | INT (8 bytes) | โ | Points to an associated ranking item |
person_ranking_summary table
Field name | Sortable | Description | |
|---|---|---|---|
db_last_modified_date | TIMESTAMP | No | The UTC time and date when the row was last modified in the database |
column_meta_data_id | INT (4 bytes) | Yes | Points to the column meta data associated with the ranking in Personalization records |
column_meta_data_name | VARCHAR (50) | No | Display name of the column meta data |
customer_site_id | INT (4 bytes) | Yes | Points to the customerโs website in Personalization records |
frequency | INT (4 bytes) | No | Value assigned to the ranking summary (for example, the sum of the daily values for the last period) |
freq_rank | INT (4 bytes) | No | The rank, by frequency, when compared to other ranking summaries with
the same |
item_name | VARCHAR (200) | No | Name of the ranking summaryโfor example, |
last_modified_date | TIMESTAMP | No | Time and date the row was last modified |
person_id | INT (4 bytes) | Yes | Points to a specific person in Personalization records |
site_external_id | VARCHAR (20) | No | External identifier of the customerโs website |
site_name | VARCHAR (50) | No | Name of the customerโs website |