Personalization Omnichannel provides access to a cloud-based data warehouse containing your Personalization-hosted visitor data. You can directly connect to the data warehouse to use your own business intelligence tools to analyze your visitors and discover new insights.
You can also extend your use of the visitor data warehouse by using the Using the Personalization APIs or manually Uploading import files to Personalization to import external visitor information (such as from your CRM system) into Personalization, providing you with a single location for your aggregated visitor information.
The data warehouse updates either every 10,000 records or about every 15 minutes, depending upon which threshold is first met. It may take up to 24 hours for processed data to be available in all tables.
After purchasing a license for Omnichannel, you will be provided with connection instructions to your visitor data warehouse.
Configuration
You can use your connection information for:
Field layouts
The data warehouse structure uses the following field layouts for organizing and presenting its data:
- Data warehouse Person field types: This field layout describes visitors that have been uniquely identified with first-party cookies, their email addresses, or some other identifier.
- Data warehouse Touch field types: This field layout describes a series of contiguous events (such as content views) with a duration between events of no more than 30 minutes. Each touch has a Person record as its parent.
- Data warehouse Event field types: This field layout describes discrete visitor actions, such as a content view of an article or a click-through on a subscription offer. An event has a Touch record as its parent. Events also contain information about the specific content that a visitor is consuming.
- Data warehouse Segment field types: This field layout describes the segments associated with each event for a given person, and is made up of a
segments table (for specific segment information) and the matching_segments table (links events with their associated segments).
Data warehouse
Personalization Omnichannel provides access to a cloud-based data warehouse containing your Personalization-hosted visitor data. You can directly connect to the data warehouse to use your own business intelligence tools to analyze your visitors and discover new insights.
You can also extend your use of the visitor data warehouse by using the Using the Personalization APIs or manually Uploading import files to Personalization to import external visitor information (such as from your CRM system) into Personalization, providing you with a single location for your aggregated visitor information.
The data warehouse updates either every 10,000 records or about every 15 minutes, depending upon which threshold is first met. It may take up to 24 hours for processed data to be available in all tables.
After purchasing a license for Omnichannel, you will be provided with connection instructions to your visitor data warehouse.
Configuration
You can use your connection information for:
Field layouts
The data warehouse structure uses the following field layouts for organizing and presenting its data:
- Data warehouse Person field types: This field layout describes visitors that have been uniquely identified with first-party cookies, their email addresses, or some other identifier.
- Data warehouse Touch field types: This field layout describes a series of contiguous events (such as content views) with a duration between events of no more than 30 minutes. Each touch has a Person record as its parent.
- Data warehouse Event field types: This field layout describes discrete visitor actions, such as a content view of an article or a click-through on a subscription offer. An event has a Touch record as its parent. Events also contain information about the specific content that a visitor is consuming.
- Data warehouse Segment field types: This field layout describes the segments associated with each event for a given person, and is made up of a
segments table (for specific segment information) and the matching_segments table (links events with their associated segments).
Personalization