Difference between revisions of "ATC/Current/AdminGuide/Action Map Performance"
(Published) |
(Published) |
||
Line 4: | Line 4: | ||
|TocName=Action Map Performance | |TocName=Action Map Performance | ||
|Context=Learn how to see when and how visitors interact with a specific action map. | |Context=Learn how to see when and how visitors interact with a specific action map. | ||
− | |||
|ComingSoon=No | |ComingSoon=No | ||
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud | ||
Line 73: | Line 72: | ||
{{!}}'''Web chats''' | {{!}}'''Web chats''' | ||
{{!}}'''Web messaging''' | {{!}}'''Web messaging''' | ||
− | |||
{{!}}'''Content offers''' | {{!}}'''Content offers''' | ||
{{!}}'''Architect flow actions''' | {{!}}'''Architect flow actions''' | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Qualified''' | {{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Qualified''' | ||
− | |||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
Line 85: | Line 82: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Offered''' | {{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Offered''' | ||
− | |||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
Line 92: | Line 88: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Accepted''' | {{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Accepted''' | ||
− | |||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
Line 101: | Line 96: | ||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
− | |||
{{!}} | {{!}} | ||
{{!}} | {{!}} | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Engaged''' | {{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Engaged''' | ||
− | |||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
Line 113: | Line 106: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Rejected''' | {{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Rejected''' | ||
− | |||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
Line 120: | Line 112: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Errored''' | {{!}} style="width: 245.047px;" data-mce-style="width: 245.047px;"{{!}}'''Web Actions Errored''' | ||
− | |||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
Line 129: | Line 120: | ||
{{!}} | {{!}} | ||
{{!}} | {{!}} | ||
− | |||
{{!}} | {{!}} | ||
{{!}} | {{!}} | ||
Line 136: | Line 126: | ||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
− | |||
{{!}} | {{!}} | ||
{{!}} | {{!}} | ||
Line 143: | Line 132: | ||
{{!}}x | {{!}}x | ||
{{!}}x | {{!}}x | ||
− | |||
{{!}} | {{!}} | ||
{{!}} | {{!}} | ||
Line 151: | Line 139: | ||
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Monitor_web_chat_performance|display text=Web chats}} | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Monitor_web_chat_performance|display text=Web chats}} | ||
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Monitor_web_messaging_performance|display text=Web messaging}} | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Monitor_web_messaging_performance|display text=Web messaging}} | ||
− | |||
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorContentOffers|display text=Content offers}} | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorContentOffers|display text=Content offers}} | ||
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorArchFlows|display text=Architect flows}} | *{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorArchFlows|display text=Architect flows}} |
Revision as of 10:37, May 18, 2021
Contents
Learn how to see when and how visitors interact with a specific action map.
Prerequisites
- Configure the following permissions in Genesys Cloud:
- Journey > Report > View
- Journey > Action Map > View (to see action maps in the report)
About the Action Map Performance reports
The Action Map Performance reports display metrics about the effectiveness of your action maps. For example, you see details such as when the action map triggered and how visitors responded to its engagement offer. For more information about the specific metrics available, see Action Map Performance report metrics.
For more information about the availability of the data in this report, see About analytics data.View Action Map Performance reports
In Admin in Genesys Cloud, open the Action Map Report. A card appears for each action map.
Card details indicate:
- What triggers the action map: a segment or an event
- Whether the action map is active
Configure the Action Map Performance report
- Select the date range for the report.
- Indicate whether you want to see hourly or daily results. For more information, see Granularity.
- To turn on or off a metric, click its name.
Export the Action Map Performance report
You can export the details of the Action Map Performance report to a CSV (comma-separate value) file. Configure the report so that it displays the data that you want and then download the file. The report downloads to your local Downloads folder.
About time values in exported reports
When you export a Visitor Activity report, the name of the exported file includes from- and to- timestamps in the standard ISO-8601 format (mmhhddmmyyyy).
If you import the CSV file into Excel, use the following formula to convert the ISO-8601 time formatted-cell to the Date type:
=DATEVALUE(MID(A1,1,10))+TIMEVALUE(MID(A1,12,8))"
(A1 represents the cell location of the first ISO-8601 time formatted cell in the Excel worksheet.)Action Map Performance report metrics
The Action Map Performance report displays metrics for the time period that you select.
Not all states are applicable to all action map types. For example, content offers, web chat offers, and web messaging offers could share some states. However, content offers and web messaging offers only use a subset of the states.
Metric | Web chats | Web messaging | Content offers | Architect flow actions |
Web Actions Qualified | x | x | x | x |
Web Actions Offered | x | x | x | x |
Web Actions Accepted | x | x | x | |
Web Actions Started | x | x | ||
Web Actions Engaged | x | x | ||
Web Actions Rejected | x | x | x | x |
Web Actions Errored | x | x | x | x |
Web Actions Timed Out | ||||
Web Actions Abandoned | x | x | ||
Web Actions Outside Schedule | x | x |
For more information about the metric definitions:
View report details
Reporting discrepancies
Following are possible reasons for discrepancies between qualified and offered web engagements (web chat, web messaging, content offer):
- URL conditions specified but not met
- Another action map qualified and offered a web engagement
- No agents available
- Cannot answer chats within the service level
- Outside of business hours
- Visitor left your website
- Frequency capping