Web sessions

From Genesys Documentation
Jump to: navigation, search

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 user 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 a 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 the customer. For example, you can use ac 'identify' and map traits to link customer 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 user navigates your website, Genesys Predictive Engagement collects the following data about the user'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 orchestra future customer journeys:

For more information about tracking limits, see [[ATC/Limits|]].
For more information about web event tracking for billing purposes, see Billing and usage.

Custom web events

1

You can use the ac('record') method in the Journey JavaScript SDK to track custom web events.

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. 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 rests their mouse on 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

1

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.