Difference between revisions of "ATC/Current/AdminGuide/Web sessions"

From Genesys Documentation
Jump to: navigation, search
(Published)
 
(2 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
|Prereq='''Prerequisites'''
 
|Prereq='''Prerequisites'''
  
−
*[https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud:]
+
*[https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud CX:]
 
**To see custom sessions and custom events, assign agents specific {{Link-AnywhereElse|product=ATC|version=Current|manual=AgentGuide|topic=GPE_Customer_journey|display text=permissions}}.
 
**To see custom sessions and custom events, assign agents specific {{Link-AnywhereElse|product=ATC|version=Current|manual=AgentGuide|topic=GPE_Customer_journey|display text=permissions}}.
  
 
*Deploy one of the following:
 
*Deploy one of the following:
−
**For Genesys Cloud customers using web messaging, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Messenger_configuration|display text=configure and deploy Genesys Messenger}}.
+
**For Genesys Cloud CX customers using web messaging, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Messenger_configuration|display text=configure and deploy Genesys Messenger}}.
 
**For all other customers, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=deploy the tracking snippet}}.
 
**For all other customers, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=deploy the tracking snippet}}.
 
|Section={{Section
 
|Section={{Section
Line 32: Line 32:
 
*We do not create contacts from cookies.
 
*We do not create contacts from cookies.
  
−
*We do add cookies to existing Genesys Cloud [https://help.mypurecloud.com/articles/?p=70936 external contacts].|}}  
+
*We do add cookies to existing Genesys Cloud CX [https://help.mypurecloud.com/articles/?p=70936 external contacts].|}}  
  
−
If you use the {{Link-SomewhereInThisVersion|manual=SDK|topic=Get_started|display text=Journey JavaScript SDK}} to capture a customer's personal data while they are on your website, it's possible for us to identify them. For example, you can use  <code>{{Link-SomewhereInThisVersion|manual=SDK|topic=Identify|display text=ac 'identify'}}</code> and {{Link-SomewhereInThisVersion|manual=SDK|topic=Traits_mapper|display text=map traits to link visitor records}}.   
+
If you deployed the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=tracking snippet}} to your website and you use the {{Link-SomewhereInThisVersion|manual=SDK|topic=Get_started|display text=Journey JavaScript SDK}} to capture a customer's personal data while they are on your website, it's possible for us to identify them. For example, you can use  <code>{{Link-SomewhereInThisVersion|manual=SDK|topic=Identify|display text=ac 'identify'}}</code> and {{Link-SomewhereInThisVersion|manual=SDK|topic=Traits_mapper|display text=map traits to link visitor records}}.   
  
 
If we are unable to verify that the customer has a corresponding customer record, the customer's name appears as "Unknown" in the session card.
 
If we are unable to verify that the customer has a corresponding customer record, the customer's name appears as "Unknown" in the session card.
Line 50: Line 50:
 
|structuredtext=As a customer navigates your website, {{MintyDocsProduct}} collects the following data about the customer's activity during a web session. Agents can view this information in the web session card. You can use this data to create {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_segments|display text=segments}}, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_outcomes|display text=outcomes}}, and {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_action_maps|display text=action maps}} that orchestrate future visitor journeys:
 
|structuredtext=As a customer navigates your website, {{MintyDocsProduct}} collects the following data about the customer's activity during a web session. Agents can view this information in the web session card. You can use this data to create {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_segments|display text=segments}}, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_outcomes|display text=outcomes}}, and {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_action_maps|display text=action maps}} that orchestrate future visitor journeys:
  
−
*{{Link-SomewhereInThisVersion|manual=SDK|topic=Pageview|display text=Page views}} (Journey JavaScript SDK users only)
+
*{{Link-SomewhereInThisVersion|manual=SDK|topic=Pageview|display text=Page views}} (only available if you deployed the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=tracking snippet}} to your website)
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_sessions|anchor=TrackMoreEvents|display text=Custom web events}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_sessions|anchor=TrackMoreEvents|display text=Custom web events}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_tracking|anchor=SiteSearchSettings|display text=Searches}}
 
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Web_tracking|anchor=SiteSearchSettings|display text=Searches}}
Line 57: Line 57:
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
−
|sectionHeading=AI-23 Add to section above
 
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=For more information about tracking limits, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Object_limits|display text=Limits for Genesys Predictive Engagement objects}}.
+
|structuredtext=AI-23 Add to section above
 +
 
 +
For more information about tracking limits, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Object_limits|display text=Limits for Genesys Predictive Engagement objects}}.
 
|Status=Yes
 
|Status=Yes
 
}}{{Section
 
}}{{Section
Line 96: Line 97:
 
*Segments matched during the session
 
*Segments matched during the session
 
*Outcomes achieved during the session
 
*Outcomes achieved during the session
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=Where agents see event-specific information
 +
|anchor=WhereAgentsSeeEvent
 +
|alignment=Vertical
 +
|structuredtext=Agents see event-related data in the journey map when they view session details. The following image shows a web session. The pages that the customer viewed appear along the left, and the specific events that occurred during the session appear in the customer journey map. When the agent rests their mouse on an icon in the map, a tooltip provides more details.
 +
 +
As the following section explains, you can change the names of the events and the information in the tooltip.[[File:TooltipExample2.png]]
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 108: Line 117:
 
*Appearance of attributes in the tooltip
 
*Appearance of attributes in the tooltip
  
−
For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Event_types|anchor=MakeItMeaningful|display text=Make event information meaningful to agents}}.
+
<br />
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Latest revision as of 12:01, October 28, 2022

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

Feature coming soon!Learn how to capture information about customer activity on your website and present it to agents.

Prerequisites

Overview

When you track your website with Genesys Predictive Engagement, we capture the history of web interactions. This history includes all the times and ways that customers visited and interacted with your website.

Each time a customer arrives on your website, a new web session begins. The web session ends when a customer is inactive for 20 minutes or longer.

How we verify contacts on your website

When a customer comes to your website, we attempt to verify their identity using their cookie. If no cookie is available, we attempt to verify their identity with identifiers that we collect from the web, such as phone or email.
Important
 
  • Successful verification requires a phone number in E164 format.
  • We do not create contacts from cookies.

If you deployed the tracking snippet to your website and you use the Journey JavaScript SDK to capture a customer's personal data while they are on your website, it's possible for us to identify them. For example, you can use ac 'identify' and map traits to link visitor records.

If we are unable to verify that the customer has a corresponding customer record, the customer's name appears as "Unknown" in the session card.

Web session type

We assign each web session the predefined web session type. You cannot change this type.

Web events

As a customer navigates your website, Genesys Predictive Engagement collects the following data about the customer's activity during a web session. Agents can view this information in the web session card. You can use this data to create segments, outcomes, and action maps that orchestrate future visitor journeys:

For more information about web event tracking for billing purposes, see Billing and usage.

AI-23 Add to section above

For more information about tracking limits, see Limits for Genesys Predictive Engagement objects.

Custom web events

You can track custom web events using one of the following:

For example:

  • Button clicks (for example, add to cart, submit a form)
  • Check out
  • Play video
  • In-page messaging (for example, wrong password, form errors)
For these custom web events, you can track custom attributes. When an agent clicks the event's icon on the customer journey map, the custom attributes and their corresponding values appear in the tooltip.

Web session cards

Agents see a separate session card for each web session. The session card includes:

  • Title
  • Icon
  • Duration
  • Current page
  • Session information
  • Journey map
  • Searches performed
  • Segments matched during the session
  • Outcomes achieved during the session

Where agents see event-specific information

Agents see event-related data in the journey map when they view session details. The following image shows a web session. The pages that the customer viewed appear along the left, and the specific events that occurred during the session appear in the customer journey map. When the agent rests their mouse on an icon in the map, a tooltip provides more details.

As the following section explains, you can change the names of the events and the information in the tooltip.TooltipExample2.png

Configure web session cards

You can configure the appearance of the web session cards:

  • Name that appears as the title on all web session cards (Ex: "Web Visit")
  • Appearance of attributes in the tooltip

Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Web_sessions (2025-06-19 06:23:10)"
Comments or questions about this documentation? Contact us for support!