Difference between revisions of "ATC/GPEandWidgets"
From Genesys Documentation
(Published) |
(Published) |
||
Line 7: | Line 7: | ||
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | ||
|Section={{Section | |Section={{Section | ||
− | |||
− | |||
|alignment=Vertical | |alignment=Vertical | ||
− | |structuredtext={{ | + | |structuredtext=<br />{{NoteFormat|This article only applies to customers using {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_chats|display text=web chat}}. If you are a Genesys Cloud customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.|}}<br /> |
|Status=No | |Status=No | ||
}}{{Section | }}{{Section |
Revision as of 11:04, August 10, 2021
Contents
Learn why and how to configure a widget for use with Genesys Predictive Engagement.
Important
This article only applies to customers using web chat. If you are a Genesys Cloud customer, we encourage you to use the new web messaging feature to replace web chat.1. Administrators: Create a Genesys Cloud Version 2 widget
Follow the instructions to configure a Genesys Cloud Version 2 widget.
As you configure the widget, remember:
- Give the widget a meaningful name that indicates its use with Genesys Predictive Engagement.
- The list of allowed domains for the widget should match the list of allowed domains for Genesys Predictive Engagement.
- After you save the widget, copy the deployment key for use as you complete your platform-specific configuration and deployment.
2. Developers: Configure and deploy the widget on your platform
Important
On a tracked website, you must deploy the widgets transport object above the location where you deploy the Genesys Predictive Engagement tracking snippet.- Genesys Cloud:
- Follow these instructions to deploy the Version 2 widget on your website.
- Genesys Engage:
- PureConnect:
Comments or questions about this documentation? Contact us for support!