Integrating with Genesys Historical Reporting

This page describes the component and configuration requirements to enable historical reporting on Genesys Co-browse activity in your deployment.

Overview: Genesys Co-browse reporting process

1. After a co-browse session is finished, Genesys Co-browse produces a reporting event, which it stores in a Kafka database. For more information about the reporting event attributes, see TABLE TO BE ADDED, below.
2. On a regular schedule, Genesys Info Mart extracts the Genesys Co-browse data from the Kafka database and transforms it into the XXX TABLE? table and supporting dimensions in the Info Mart dimensional model. For more information about the Info Mart database tables, see the Genesys Info Mart Physical Data Model for your RDBMS. For more information about managing the Genesys Info Mart ETL jobs, see the Genesys Info Mart Operations Guide.
3. In deployments that include Reporting and Analytics Aggregates (RAA) and Genesys CX Insights (GCXI), RAA summarizes and organizes the Info Mart data in ways that enable GCXI to extract meaning. For more information about RAA data, see the RAA User's Guide.
4. GCXI uses the aggregated data in the Info Mart database to produce a Co-browse Dashboard. For more information, see Co-browse reports in the GCXI User's Guide. <currently in draft form>

Enabling historical reporting on Genesys Co-browse activity

Prerequisites

The following table summarizes the minimum release requirements for the Genesys and third-party components that enable Genesys Co-browse historical reporting.

Component	Minimum release
Genesys Co-browse Server	9.0.003.02
Kafka	2.0 verify
Workspace Web Edition (Web Services and Applications)	8.5.202.51
Genesys Info Mart	8.5.011.xx
RAA	8.5.006.00
GCXI	9.0.009.xx