Exporting customer data from Pega Customer Decision Hub
Organizations frequently need to export data such as transactional data, analytical and monitoring data, or interaction history results out of Pega Customer Decision Hub for further processing.
For example, the results of next-best-action decisions are recorded in Pega Customer Decision Hub as interaction history for each customer. You can export interaction history data out of Pega Customer Decision Hub and use it for reporting in external business intelligence tools that create insight beyond the scope of the Pega application.
Understanding the export process
You can define a data flow that exports interaction history records into a File data set. By running the data flow, you can export the data out of Pega Customer Decision Hub and into a specified repository.
Configuring the export process
To export the data associated with daily interactions into a Pega Cloud File Storage and use this data for additional analysis, configure a data flow that exports the interaction history data into a File data set.
- Create a file data set with a file path that leads to the location in which you
want to export the interaction files.For more information, see Creating a File data set record for files on repositories.
- Create a data flow with the data set that you want to export as the source and
the file data set that you created in step 1 as the destination.For more information, see Creating a data flow.
- Run the data flow.For more information, see Triggering the customer data ingestion process.
Result: During each run, the data flow exports interaction history data into files in the specified repository. The file names include a date and time stamp, as configured in the file data set. Additionally, a
.metafile is created that contains the metadata of each file saved in the repository, as in the following example:
<?xml version='1.0' encoding='UTF-8'?> <file> <name>records_2020-02-21_002003_00000.json</name> <size>28773955</size> <recordCount>11000</recordCount> </file>
Previous topic Starting file listeners to ingest customer data Next topic Exporting interaction history data from the relational database