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

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 16: Line 16:
 
|anchor=WSOverview
 
|anchor=WSOverview
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=When you {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=track your website}} with {{MintyDocsProduct}}, we capture the history of web interactions. This history includes all the times and ways that customers visited and interacted with your website.  
+
|structuredtext=When you {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_data_tracking|display text=track your website}} with {{MintyDocsProduct}}, 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.
 
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.
Line 39: Line 39:
 
|anchor=WebSessionType
 
|anchor=WebSessionType
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=We assign each web session the predefined <code>web</code> session type. You cannot change this type.
+
|structuredtext=We assign each web session the predefined web session type. You cannot change this type.
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 47: Line 47:
 
|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}}
+
*{{Link-SomewhereInThisVersion|manual=SDK|topic=Pageview|display text=Page views}} (Journey JavaScript SDK users only)
 
*{{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 64: Line 64:
 
|Media=Image
 
|Media=Image
 
|image=acrecordexample.png
 
|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 custom web events.  
+
|structuredtext=You can track custom web events using one of the following:
 +
 
 +
*If you deployed the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=tracking snippet}} to your website, see {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}}
 +
*If you deployed the [https://help.mypurecloud.com/articles/?p=239328 messenger snippet] to your website, see [https://developer.genesys.cloud/api/digital/webmessaging/messengersdk/SDKCommandsEvents#journey-record Journey.record]
  
 
For example:  
 
For example:  
Line 73: Line 76:
 
*In-page messaging (for example, wrong password, form errors)
 
*In-page messaging (for example, wrong password, form errors)
  
−
For these custom 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">
+
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.
−
ac('record', 'form_submitted', { 'formName': 'Loan Application', 'type': 'First Time Buyer' }, () => {});
 
−
</syntaxhighlight>When an agent rests their mouse on the event's icon on the customer journey map, the custom attributes and their corresponding values appear in the tooltip.
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section

Revision as of 18:50, May 4, 2021

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 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

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
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 12:41:36)"
Comments or questions about this documentation? Contact us for support!