About the data we track

From Genesys Documentation
Jump to: navigation, search

Learn how Genesys Predictive Engagement tracks visitor activity on your website.

Transparency about our data tracking practices

When visitors come to your website, Genesys Predictive Engagement collects data about what they do and where they go on your website. For example, we track which pages each visitor views, any forms they submit, and any searches they complete. We collect this data to improve your understanding of the effectiveness of your website and the needs of your customers.



  • To achieve compliance with GDPR, it's important that you create and implement a tool (for example, message, dialog box) to obtain each visitor's consent to be tracked.

Data we track about each visit

Visit information tracked does not contain any personal information related to the visitor, but contains information on their current session.

Data in a visit can include:

  • Visit and visitor identifiers that identify visit information within Genesys Predictive Engagement
  • Visit timestamps, such as start time, when the visitor is considered idle, and when the visitor was last active
  • Current web page information including the number of pages visited, web document properties, and device properties
  • Journey information such as matched segments and outcomes achieved
  • Referrer information from where the visitor accessed your website, and marketing campaign information associated with it

Data we track about each visitor

Visitor information contains personal information gathered from submitting data to the Genesys Predictive Engagement system about a specific visitor. Visitor data can include:

  • Predictive Engagement-specific identifiers
  • Third-party identifiers
  • Personal details, such as name, date of birth, job information, and phone numbers
  • Predictive Engagement visit information

Feature coming soon: Web messaging
To pass this no-default data to Genesys Predictive Engagement, you need specific JavaScript code on your website.
Comments or questions about this documentation? Contact us for support!