COMMON schema reference
COMMON schema reference
This article provides a reference to the views found in the COMMON schema of the CORE data model.
CLICKED_IMPRESSIONS
This view consists of all clicked impressions (search results), as well as references to their impression data and insights.
|
Notes
|
Column name | Description |
---|---|
|
The identifier of the action that triggered the click event (for example, |
|
Reference to the click event if the item was clicked or otherwise interacted with.
Keys into |
|
Date of when the impression was clicked. |
|
Unique identifier of the impression and click combination, used as primary key. |
|
UTC timestamp of when the impression was clicked. |
|
Unique identifier of the impression.
This foreign key references the IMPRESSIONS view, establishing a many-to-one relationship, and can be |
|
Unique identifier of the insight responsible for impressing the item. This foreign key references the INSIGHTS view, establishing a many-to-one relationship, and can’t be |
|
Unique identifier of the clicked item.
This foreign key references the ITEMS view where all the items are stored, and can’t be |
|
Organization identifier for the record. |
|
Position of the clicked impression in a results list.
One-based, so position of the first item will be |
|
Unique identifier of the visit. This foreign key references the VISITS view, establishing a many-to-one relationship, and can’t be NULL. |
DEVICES
The DEVICES view provides information about identified devices, such as the browser, the operating system, and the device category.
Column name | Description |
---|---|
|
Browser used by the device. |
|
Browser with full version used by the device. |
|
Categorization of the device, such as game console, personal computer, smartphone, or other.
May be |
|
Unique identifier of the device. Used as the primary key. |
|
UTC timestamp of when the device first appeared in the organization data. |
|
UTC timestamp of when the device last appeared in the organization data. Can be updated. |
|
Operating system used by the device. |
|
Operating system with full version. |
|
Organization identifier for the record. |
EVENTS
The EVENTS view contains all the events that occurred during each visit.
It gives an overview of the user’s journey by showing the sequence of events in a visit, and also provides information such as the EVENT_TYPE
and the ACTION_CAUSE
.
Column name | Description |
---|---|
|
Date of when the event occurred. |
|
Unique identifier of the event, used as primary key. |
|
Timestamp of the event in UTC. |
|
Reported event type, either from |
|
Organization identifier for the record. |
|
Reference to the RAW event ID.
Keys into |
|
Unique identifier of the visit. This foreign key references the VISITS view, establishing a many-to-one relationship, and can’t be NULL. |
FACETS
The FACETS view provides information about the facets that were interacted with during a visit.
Column name | Description |
---|---|
|
Unique identifier of the facet. Used as the primary key. |
|
Type of the facet.
May have values such as |
|
Field name of the facet. |
|
The UTC timestamp indicating when the facet first appeared in the organization data. |
|
Identifier of the facet. |
|
The UTC timestamp indicating when the facet last appeared in the organization data. |
|
Organization identifier for the record. |
FACET_VALUES
The FACET_VALUES view provides information about the different facet and value combinations that were interacted with during a visit.
Column name | Description |
---|---|
|
Unique identifier of the facet and value combination. Used as the primary key. |
|
The UTC timestamp of when the facet and value combination first appeared in the organization data. |
|
The UTC timestamp of when the facet and value combination last appeared in the organization data. |
|
Organization identifier for the record. |
|
Value of the facet. |
GEO_LOCATIONS
The GEO_LOCATIONS view provides information about the specific geographic location, such as country, region, and city.
|
Notes
|
Column name | Description |
---|---|
|
City name of the location. |
|
Continent name of the location. |
|
Country name of the location. |
|
Whether the country is part of the European Union. |
|
UTC timestamp of when the location first appeared in the organization data. |
|
Unique identifier of the geographical location. Used as the primary key. |
|
UTC timestamp of when the location last appeared in the organization data. Can be updated. |
|
Organization identifier for the record. |
|
Time zone of the location. |
|
Region name of the location. |
INSIGHTS
Column name | Description | ||
---|---|---|---|
|
The UI-reported reason why the insight was executed. See |
||
|
Set to |
||
|
Unique identifier of the listing or recommendation configuration. Used as a primary key. |
||
|
(Optional) Corrected query expression if the query correction logic has been applied. |
||
|
(Commerce only) Name of the listing page which triggered the event. |
||
|
Date of when the insight’s execution was started. |
||
|
Unique identifier of the insight. Used as the primary key. |
||
|
The type of algorithm that was executed. Type can be either search, listing, recommendation, or other. New types may be added when required. |
||
|
External identifier for the insight.
Typically, the platform’s |
||
|
The locale of the current user. Must comply with IETF’s BCP 47 definition. |
||
|
Origin identifier for the insight.
Typically the platform’s |
||
|
Organization identifier for the record. |
||
|
Reference to the pageview which spawned the execution.
Keys into |
||
|
Basic query expression for the event. |
||
|
The name of the query pipeline that processed the query. |
||
|
Duration it took for the execution to return results. |
||
|
The number of results returned.
|
||
|
Unique identifier of the insight event.
This foreign key references the EVENTS view, establishing a one-to-one relationship, and can’t be |
||
|
UTC timestamp of when the insight’s execution was started. |
||
|
Unique identifier of the visit in which the insight was executed. This foreign key references the VISITS view, establishing a many-to-one relationship, and can’t be |
IMPRESSIONS
The IMPRESSIONS view contains all results returned following a given search event.
|
Note
We assume that all products shown after the search event were viewed by the end user, whether they originated from a recommendation component, a listing page, or a search results list. |
Column name | Description | ||
---|---|---|---|
|
The identifier of the action that triggered the click event.
|
||
|
Unique identifier of the click event.
|
||
|
Date of when the impression occurred. |
||
|
Unique identifier of the impression. Used as the primary key. |
||
|
UTC timestamp of when the impression occurred. |
||
|
Unique identifier of the insight responsible for impressing the item. This foreign key references the INSIGHTS view, establishing a many-to-one relationship, and can’t be |
||
|
Unique identifier of the item being impressed.
This foreign key references the ITEMS view where all the items are stored, and can’t be |
||
|
Organization identifier for the record. |
||
|
Position of the impression in a results list.
One-based, therefore the position of the first item will be |
||
|
Unique identifier of the visit in which the impression occurred.
This foreign key references the VISITS view, establishing a many-to-one relationship, and can’t be |
INSIGHT_FACET_STATES
The INSIGHT_FACET_STATES view contains all insights where facets were used.
Column name | Description |
---|---|
|
Unique identifier of the facet. Keys into FACETS. |
|
Position of the facet. |
|
Unique identifier of the facet and value combination. Keys into FACET_VALUES. |
|
Position of the value in the facet. |
|
Date of when the insight’s execution was started. |
|
Unique identifier of the insight. Keys into INSIGHTS. |
|
Organization identifier for the record. |
|
The UTC timestamp indicating when the insight’s execution was started. |
|
State of the facet.
The values can be either |
ITEMS
|
Note
While the ITEMS view logs details from both search and click events, the item data received may only include limited information, such as the |
Column name | Description |
---|---|
|
Any detailed information on the item. The amount and type of content may vary per use case. For commerce customers, this will include product categories and brand, which are sourced from the product catalog. |
|
Unique identifier of the item. Used as the primary key. |
|
Item name as reported by incoming events or enriched by the item catalog. |
|
Item URL as reported by incoming events. |
|
Organization identifier for the record. |
|
Index identifier of the item. |
PAGEVIEWS
The PAGEVIEWS view lists the page view events that occurred on individual web pages.
It shows the specific page_url
that was visited as well as a link to information on the specific PAGE
instance.
Column name | Description |
---|---|
|
Organization identifier for the record. |
|
Unique identifier of the viewed page.
This foreign key references the PAGES view, establishing a many-to-one relationship, and can’t be |
|
Unique identifier of the page view event, used as primary key. |
|
Page that was visited just before the page view event was logged. |
|
Unique identifier of the visit in which the page view occurred.
This foreign key references the VISITS view, establishing a many-to-one relationship, and can’t be |
|
Unique identifier of the page view event.
This foreign key references the EVENTS view, establishing a one-to-one relationship, and can’t be |
|
UTC timestamp of when the page view event occurred. |
|
URL of the page in which the page view event was recorded, including any parameters or fragments. |
PAGES
The PAGES view provides information on unique pages contained in view events.
|
Note
URL parameters and fragments aren’t taken into account. |
Column name | Description |
---|---|
|
Organization identifier for the record. |
|
Unique identifier of the page. Used as primary key. |
|
Title of the page. |
|
Type of the page. |
|
URL of the page, excluding any parameters or fragments. |
|
Index identifier of the page, if it was part of the index. |
SITES
The SITES view provides information about the different websites that Coveo serves.
Column name | Description |
---|---|
|
UTC timestamp of when the site first appeared in the organization data. |
|
UTC timestamp of when the site last appeared in the organization data. Can be updated. |
|
Organization identifier for the record. |
|
Unique identifier of the site. Used as the primary key. |
|
Passed website or tracking ID. |
|
Passed website or tracking ID. |
USERS
The USERS view provides the list of all users (excluding anonymous ones), along with information about the first and last time they generated events.
Column name | Description |
---|---|
|
UTC timestamp of when the user first appeared in the organization data. |
|
UTC timestamp of when the user last appeared in the organization data. Can be updated. |
|
Organization identifier for the record. |
|
Unique identifier of the user. Used as primary key. |
|
Unique identifier of the user, derived from passed |
VIEWED_ITEMS
The VIEWED_ITEMS view provides information about the items that were viewed during a visit.
Column name | Description |
---|---|
|
The date the event occurred. |
|
Unique identifier of the event, used as primary key. Can be used to link to EVENTS. |
|
Timestamp of the event in UTC. |
|
Unique identifier of the item being viewed. Keys into ITEMS. |
|
The type of item viewed, either product or document. |
|
Organization identifier for this record. |
|
Reference to the RAW event ID. Keys into RAW.EVENTS. |
|
Page which was visited just before the page view event was logged. |
|
Unique identifier of the visit in which the page view occurred. Keys into VISITS view |
VISITS
Column name | Description |
---|---|
|
UUID client identifier for the visit.
Equal to received |
|
Unique identifier of the device used.
Keys into |
|
Unique identifier of the visit’s origin location.
Keys into |
|
One-way hashed IP address. |
|
Whether the visit was flagged as a potential bot visit. |
|
Whether the IP address was flagged as customer internal. |
|
Organization identifier for the record. |
|
Unique identifier for the site or web property.
Keys into |
|
Unique identifier of the user and equal to the platform’s |
|
UTC end time of the visit. |
|
Unique identifier of the visit. Used as primary key. |
|
UTC start time of the visit. |