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

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
(Published)
Line 3: Line 3:
 
|DisplayName=Web sessions
 
|DisplayName=Web sessions
 
|TocName=Web sessions
 
|TocName=Web sessions
−
|Context=Web sessions
+
|Context=Understand how to capture information about customer activity on your website and present it to agents.
 +
|Dimension=Session Library
 
|ComingSoon=Yes
 
|ComingSoon=Yes
 
|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
 
|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
Line 16: Line 17:
 
|anchor=WSOverview
 
|anchor=WSOverview
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=When you {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_tracking|display text=track your website with {{MINTYDOCSPRODUCT}}}}, agents can see the history of a customer's interactions with your website, including the different devices and browsers they used.
+
|structuredtext=When you {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_tracking|display text=track your website with {{MINTYDOCSPRODUCT}}}}, we capture the history of their web interactions. This history includes all of the times and ways in which 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 user has been inactive for 20 minutes or longer.  
 +
 
 +
<br />
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 22: Line 27:
 
|anchor=VerifyContacts
 
|anchor=VerifyContacts
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=When a customer comes to a website, we attempt to verify their identity by using their cookie. If no cookie is available, we attempt to verify their identity with identifiers that we collect from the web, such as a phone or an email.{{NoteFormat|Successful verification requires a phone number in E164 format.  
+
|structuredtext=When a customer comes to your website, we attempt to verify their identity by using their cookie. If no cookie is available, we attempt to verify their identity with identifiers that we collect from the web, such as a phone or an email.{{NoteFormat|Successful verification requires a phone number in E164 format.  
  
 
We do not automatically create a new contact from a cookie.
 
We do not automatically create a new contact from a cookie.
Line 33: Line 38:
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
−
|sectionHeading=How web sessions begin and end
+
|sectionHeading=Web session type
−
|anchor=BeginEnd
+
|anchor=WebSessionType
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=Each time a customer arrives on your website, a new web session begins. The web session ends when a user has been inactive for 20 minutes or longer.
+
|structuredtext=We automatically assign each web session the predefined <code>web</code> session type. You cannot change this type.
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
−
|sectionHeading=For later
+
|sectionHeading=Web session events
 +
|anchor=WebSessionEvents
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=As an admin, you can use the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Session_library}} to configure the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Session_card|display text=session card}} for web sessions. This ensure that agents see the correct level of detail in a layout that is easy to use.
+
|structuredtext=For all web sessions, we automatically track the following web events:
−
|Status=Yes
+
 
 +
*form_submitted
 +
*form_abandoned
 +
*page_viewed
 +
*widgets_web_chat_submitted
 +
 
 +
<br />
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=Track additional web events
 +
|anchor=TrackMoreEvents
 +
|alignment=Horizontal
 +
|Media=Image
 +
|image=acrecordexample.png
 +
|structuredtext=You can use the {{Link-SomewhereInThisVersion|manual=SDK|topic=Record|display text=ac('record') method}} in the Journey JavaScript SDK to track additional web events. For these additional web events, you can track {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|anchor=customAttributes|display text=custom attributes}}. For example, suppose we track the following web event using <code>ac('record')</code>.<syntaxhighlight lang="javascript">
 +
ac('record', 'form_submitted', { 'formName': 'Loan Application', 'type': 'First Time Buyer' }, () => {});
 +
</syntaxhighlight>When an agent hovers over the event's icon on the customer journey map, the custom attributes and their corresponding values appear in the tooltip.
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=Web session cards
 +
|anchor=WebSessionCards
 +
|alignment=Horizontal
 +
|structuredtext=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
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=Configure web session cards
 +
|anchor=CustomizeWebEvent
 +
|alignment=Horizontal
 +
|Media=Image
 +
|image=WebSessionCard.png
 +
|structuredtext=You can configure the appearance of the web session cards:
 +
 
 +
*The name that appears as the title on all web session cards (Ex: "Web Visit")
 +
*The appearance of attributes that appear in the tooltip
 +
 
 +
For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Event_types|anchor=MakeItMeaningful|display text=Make event information meaningful to agents}}.
 +
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 10:21, July 28, 2020

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

Feature coming soon!Understand 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 their web interactions. This history includes all of the times and ways in which 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 user has been 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 by using their cookie. If no cookie is available, we attempt to verify their identity with identifiers that we collect from the web, such as a phone or an email.
Important
Successful verification requires a phone number in E164 format.

We do not automatically create a new contact from a cookie.

We do add cookies to existing Genesys Cloud external contacts .

Additionally, we may be able to identify a customer if you use the Journey JavaScript SDK to capture a customer's personal data while they are on your website. For example, you may use ac 'identify' and map traits to link customer records.

If 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 automatically assign each web session the predefined web session type. You cannot change this type.

Web session events

For all web sessions, we automatically track the following web events:

  • form_submitted
  • form_abandoned
  • page_viewed
  • widgets_web_chat_submitted


Track additional web events

You can use the ac('record') method in the Journey JavaScript SDK to track additional web events. For these additional web events, you can track custom attributes. For example, suppose we track the following web event using ac('record').
ac('record', 'form_submitted', { 'formName': 'Loan Application', 'type': 'First Time Buyer' }, () => {});
When an agent hovers over 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

Configure web session cards

You can configure the appearance of the web session cards:

  • The name that appears as the title on all web session cards (Ex: "Web Visit")
  • The appearance of attributes that appear in the tooltip
For more information, see Make event information meaningful to agents.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Web_sessions (2025-06-19 06:16:21)"
Comments or questions about this documentation? Contact us for support!