Difference between revisions of "ATC/Current/AdminGuide/About data tracking"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
m (Text replacement - "Genesys Cloud" to "Genesys Cloud CX")
 
(6 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
|DisplayName=About the data we track
 
|DisplayName=About the data we track
 
|TocName=About the data we track
 
|TocName=About the data we track
−
|Context=Learn how {{MINTYDOCSPRODUCT}} tracks user activity on your website.
+
|Context=Learn how {{MINTYDOCSPRODUCT}} tracks visitor activity on your website.
−
|Dimension=Tracking
+
|Dimension=Compliance
 
|ComingSoon=No
 
|ComingSoon=No
−
|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
+
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 
|Section={{Section
 
|Section={{Section
 
|sectionHeading=Transparency about our data tracking practices
 
|sectionHeading=Transparency about our data tracking practices
 
|anchor=DataTrackingTransparency
 
|anchor=DataTrackingTransparency
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=When visitors come to your website, {{MINTYDOCSPRODUCT}} collects data about what they do and where to 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.
+
|structuredtext=When visitors come to your website, {{MINTYDOCSPRODUCT}} 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.
  
 
{{NoteFormat|
 
{{NoteFormat|
−
* To be compliant with GDPR, it's important that you create and implement a tool (message, dialog box, etc.) to obtain each visitor's consent to be tracked.
+
 
 +
* 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.
  
−
* For more information on using {{MINTYDOCSPRODUCT}} in a GDPR-compliant manner, see {{#mintydocs_link:topic=GDPR}}.}}
+
* For more information on using {{MINTYDOCSPRODUCT}} in a GDPR-compliant manner, see {{#mintydocs_link:topic=GDPR}}.|}}
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 26: Line 27:
 
Data in a visit can include:
 
Data in a visit can include:
  
−
*Visit and visitor identifiers used to identify visit information within {{MINTYDOCSPRODUCT}}
+
*Visit and visitor identifiers that identify visit information within {{MINTYDOCSPRODUCT}}
−
*Visit timestamps, such as start time, when the visitor will be considered idle, and when the visitor was last active
+
*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
+
*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
 
*Journey information such as matched segments and outcomes achieved
−
*Referer information from where the customer accessed your website, and marketing campaign information associated with it
+
*Referrer information from where the visitor accessed your website, and marketing campaign information associated with it
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 36: Line 37:
 
|anchor=DataVIsitor
 
|anchor=DataVIsitor
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=Visitor information contains personal information gathered from submitting data to the {{MINTYDOCSPRODUCT}} system about a specific visitor. Data on a visitor can include:
+
|structuredtext=Visitor information contains personal information gathered from submitting data to the {{MINTYDOCSPRODUCT}} system about a specific visitor. Visitor data can include:
  
−
*{{MINTYDOCSPRODUCT}} specific identifiers
+
*Predictive Engagement-specific identifiers
 
*Third-party identifiers
 
*Third-party identifiers
−
*Personal details, such as name, DOB, job information, and phone numbers
+
*Personal details, such as name, date of birth, job information, and phone numbers
−
*{{MINTYDOCSPRODUCT}} visit information{{NoteFormat|In order to pass this no-default data to {{MINTYDOCSPRODUCT}}, the customer must deploy specific javascript code on their website. For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_tracking}}.|}}
+
*Predictive Engagement visit information
 +
 
 +
{{BarbFeatureTemp|Feature=Web messaging}}
 +
{{NoteFormat|To pass this no-default data to Genesys Predictive Engagement, you need specific JavaScript code on your website.
 +
 
 +
*If you are a Genesys Cloud CX customer, we encourage you to use the new {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat. For web messaging, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Messenger_configuration|display text=configure and deploy messenger}}.
 +
*For all other customers, copy and deploy the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=tracking snippet}}.|}}
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Latest revision as of 21:27, November 9, 2021

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

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.

Important

 

  • 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
Important
To pass this no-default data to Genesys Predictive Engagement, you need specific JavaScript code on your website.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/About_data_tracking (2025-06-20 22:11:37)"
Comments or questions about this documentation? Contact us for support!