Skip to main content

xConnect data export tool

Abstract

Overview of the xConnect data export tool that enables you to export contact and interaction data from your collection database to data files.

The Data Export Tool enables you to export contact and interaction data from your collection database.

With the data export tool you can export contacts or interactions with all the registered contact or interaction facets in the model. The export always exports all facets. You can filter the data using a set of conditions, for example, cut-off days and percentile ranges.

For example, you can use the tool to:

  • Back up data to low-cost storage for compliance reasons, before purging the data from the collection database to reduce its load.

  • Export data to a data warehouse to perform better data analyses.

Technical details

The Data Export Tool uses the Processing Engine distributed worker together with the xConnect Data Extraction API to extract data from your collection database. It exports the filtered data to data files in the storage you configure.

You configure the storage using storage profiles that connect to specific storage providers.

The storage provider defines the mechanism used to store exported data. You use a storage profile to specify the exact location and provider settings, such as storage credentials. One storage provider can have multiple storage profiles. Each profile must specify the profile name and the target folder for the exported data.

You can add your own storage provider to, for example, upload the data files into a cloud storage.

By default, the Data Export Tool is delivered with the following providers and profiles:

Provider

Profile type

Description

Recommended for

Network Folder Provider

Network Folder Profile

Uploads data files into the network folder defined in the profile.

Local development in Docker.

Azure Blob Storage Provider

Azure Blob Storage Profile

Uploads data files into the Azure Storage Account container defined in the profile.

Deployments in Azure container.

Azure File Storage Provider

Azure File Storage Profile

Uploads data files into the Azure Storage Account share and directory defined in the profile.

Deployments in Azure container.

For local development, in the XP1 topology, we recommend using volumes mapped to one local folder and attached to both the CortexProcessing and the CortexProcessingWorker containers.

Here is an example of a docker-compose.yml configuration file with the volume attached to the CortexProcessingWorker container:

cortexprocessingworker:
 isolation: ${ISOLATION}
  image: ${SITECORE_DOCKER_REGISTRY}sitecore-xp1-cortexprocessingworker:${SITECORE_VERSION}
  volumes:
   - type: bind
   source: .\CortexWorkerDataExport
   target: c:\DataExport