Web Engagement Cluster:pacing:interactionMinProcessingTime
(Rpfeiffer used the OptionPublish action.) |
|||
Line 1: | Line 1: | ||
− | {{PubOption | + | {{PubOption |
− | |||
|hidden=false | |hidden=false | ||
|default=20 | |default=20 | ||
Line 7: | Line 6: | ||
|shortdesc=Specifies the minimum number of seconds during which an interaction should be alive in order to participate in the calculation of inbound reactive traffic. <br/> | |shortdesc=Specifies the minimum number of seconds during which an interaction should be alive in order to participate in the calculation of inbound reactive traffic. <br/> | ||
This option allows the Web Engagement server to prevent the corruption of results provided by dual pacing algorithms in the presence of low-volume malicious traffic (where visitors continually start chat interactions and then immediately close them without delivering them to an agent). | This option allows the Web Engagement server to prevent the corruption of results provided by dual pacing algorithms in the presence of low-volume malicious traffic (where visitors continually start chat interactions and then immediately close them without delivering them to an agent). | ||
+ | }} | ||
+ | {{DraftOption | ||
}} | }} | ||
{{PubExtended}} | {{PubExtended}} | ||
− | {{DraftExtended}} | + | {{DraftExtended |
+ | }} | ||
{{OptionCreate | {{OptionCreate | ||
|component=Web_Engagement_Cluster | |component=Web_Engagement_Cluster |
Latest revision as of 20:46, March 22, 2018
View in ref guide.
Edit this option Publish this option Clear draft content
Published Option
Draft Option
No draft option
This page was last edited on March 22, 2018, at 20:46.
Comments or questions about this documentation? Contact us for support!