Data warehouse Person field types

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
person_link
person_identifier
person_ranking_item
person_ranking_summary

person table

Field name	Data type	Sortable	Description
active	BOOLEAN	𐄂	The person is a unique entity; `false` indicates this person was merged into another person during identity resolution (touches and events remain linked to the original person)
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; `person_id` fields in other tables refer to this 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, `Unlimited`, `Monthly`, or `Yearly`)—optional and provided externally
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	Data type	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`
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	Data type	Sortable	Description
active	BOOLEAN	𐄂	The person is a unique entity; `False` indicates this person was merged into another person during identity resolution (touches and events remain linked to the original person)
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 `person_identifier_type_id`
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_ranking_item table

Field name	Data type	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, `DESKTOP` for the device ranking
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_summary table

Field name	Data type	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

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
person_link
person_identifier
person_ranking_item
person_ranking_summary

person table

Field name	Data type	Sortable	Description
active	BOOLEAN	𐄂	The person is a unique entity; `false` indicates this person was merged into another person during identity resolution (touches and events remain linked to the original person)
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; `person_id` fields in other tables refer to this 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, `Unlimited`, `Monthly`, or `Yearly`)—optional and provided externally
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	Data type	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`
person_id	INT (4 bytes)	✓	Points to a specific person in Personalization records

Note

person_identifier table

Field name	Data type	Sortable	Description
active	BOOLEAN	𐄂	The person is a unique entity; `False` indicates this person was merged into another person during identity resolution (touches and events remain linked to the original person)
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 `person_identifier_type_id`
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_ranking_item table

Field name	Data type	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, `DESKTOP` for the device ranking
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_summary table

Field name	Data type	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

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
person_link
person_identifier
person_ranking_item
person_ranking_summary

person table

Field name	Data type	Sortable	Description
active	BOOLEAN	𐄂	The person is a unique entity; `false` indicates this person was merged into another person during identity resolution (touches and events remain linked to the original person)
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; `person_id` fields in other tables refer to this 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, `Unlimited`, `Monthly`, or `Yearly`)—optional and provided externally
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	Data type	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`
person_id	INT (4 bytes)	✓	Points to a specific person in Personalization records

Note

person_identifier table

Field name	Data type	Sortable	Description
active	BOOLEAN	𐄂	The person is a unique entity; `False` indicates this person was merged into another person during identity resolution (touches and events remain linked to the original person)
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 `person_identifier_type_id`
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_ranking_item table

Field name	Data type	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, `DESKTOP` for the device ranking
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_summary table

Field name	Data type	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

person table

person_link table

person_identifier table

person_ranking_item table

person_ranking_summary table

person table

person_link table

person_identifier table

person_ranking_item table

person_ranking_summary table

person table

person_link table

person_identifier table

person_ranking_item table

person_ranking_summary table

Did not find what you were looking for?

Did not find what you were looking for?