Visitor Page View
This rule fires when the customer arrives on a specified page.
This rule is not used with Guide. It is provided for existing digital chat customers who may have implemented this ruloe. It is unavailable for new customers.
Create This Rule
- Click the app selector and select ACD.
-
Go to GUIDE > Engagement Rules.
-
Click Add engagement rules.
- Enter a Name for the rule. Since you can assign multiple actions to the same rule, use a name based on the event or conditions rather than an associated action.
-
From the Event drop-down, select Visitor page view.
-
From the Application type drop-down, select Browser or Native. This changes the conditions that are available for this rule. See the sections below for details.
- In the Delayed execution field, enter the number of seconds to wait after the selected event occurs before firing the rule. If you want it to happen immediately, enter 0.
- Click Save.
- From the detail page, click Activate when your rule is completely configured.
Add a Condition
If you entered a value in the Delayed execution field when you created a trigger, make sure your condition configurations do not exceed that time. For example, if you set the Delayed execution time to 86400 seconds, or 24 hours, you cannot add a Contact status update time condition with a time period greater than 1 day.
- From the detail page, click Add Condition.
- Use the drop-down to select the condition you want. Refer to the table below for a list of conditions available for what you just created.
- Click Select.
- Some conditions require additional configuration. Refer to the table below for instructions.
Available Conditions: Browser
Condition Type | Details and Instructions |
---|---|
Chat Is Active |
Execute actions based on whether chat is available. When chat is available, you can further specify required agent skills Used to automate delivery of interactions based on agent skills, abilities, and knowledge.
|
Current page |
This condition checks the page URL to fire the action.
|
Custom condition |
Execute actions based on the response from the specified URL endpoint. The response from the endpoint should return boolean (true or false).
|
Custom variable |
Checks a custom variable that was relayed using JS API.
|
Date and time |
Executes actions during or outside of specified time frames.
|
Device Type |
Executes actions based on the device your visitor is using, such as desktop, mobile, or tablet.
|
Element clicked |
Executes actions if a user clicks on a mapped part of your website. This requires the use of Engagement Mapper.
|
Excluded visitor tags |
Executes actions based on the tags that a visitor does not have. Any visitor that does not have the tags you specify fires the action.
Tags are assigned to visitors through an engagement rule that uses the Add tag to visitor action. |
External Referrer |
Executes actions based on the external source that sent a visitor to your site.
|
Field is edited |
Executes actions if a user changes the value of a mapped field on your website. This requires the use of Engagement Mapper.
|
Fingerprint |
Executes actions based on data provided by the visitor's browser: OS, OS Version, Browser, Browser Version, Language, Country and Location.
|
Included visitor tags |
Executes actions based on the tags that are assigned to visitors. Any visitor that has the tags you specify fires the action.
Tags are assigned to visitors through an engagement rule that uses the Add tag to visitor action. |
Menu item Clicked |
Executes actions if a visitor selects an item from a mapped menu on your website. This requires the use of Engagement Mapper.
|
New and Returning Visitors |
Executes actions based on whether the visitor is new to your website or a returning visitor. To offer the engagement rule for new visitors:
To offer the engagement rule for returning visitors:
If you select both the New Visitors and Returning Visitors boxes, the engagement rule fires if the visitor is new or meets the returning visitor requirements. Note that visitor data is stored in the browser. If a visitor switches browsers, they are considered a new visitor. |
Page Element exists |
Executes actions based on a mapped page element appearing on a website page. This requires the use of Engagement Mapper. To execute the actions based on a mapped element appearing on a website page:
|
Proactive action grace period |
Executes actions based on the last time a proactive action was used. Any actions in this workflow that would be run during this time frame are skipped. The maximum grace period for proactive actions is 30 days.
|
Probability of execution |
Executes actions based on a probability percentage.
|
Rage Clicking |
Executes actions based on continuous clicks on a page. Page URL
|
Scroll Depth |
Executes actions based on how far on the page a visitor scrolls.
Page URL Scroll Depth |
Time in queue |
Executes actions based on the average time contacts waited to talk with an agent over the past hour. The average is taken across all skills listed in the Queue/Skill field. For example, if you set this to Lower than 2 minutes, the engagement appears only if contacts waited, on average, less than 2 minutes to talk with an agent over the past hour.
|
Time spent on current page |
Executes actions based on the amount of time a visitor spends on a page. If the visitor switches pages, the timer is reset to 0. Note the following:
Time spent |
Time spent on page |
Executes actions based on the cumulative time that a visitor spends on selected pages. Note the following:
Page URL Time spent on page |
Time spent on site |
Executes actions based on how much time a visitor spent on your site. This depends on a specified period of time.
Time spent on website Number of passed days |
UTM Parameters |
Executes actions based on information provided by the visitor's browser.
Source Medium Campaign Term Content |
Visited pages |
Executes actions if a visitor has previously been on one or more specified pages.
|
Available Conditions: Native
Condition Type | Details and Instructions |
---|---|
Chat Is Active |
Execute actions based on whether chat is available. When chat is available, you can further specify required agent skills Used to automate delivery of interactions based on agent skills, abilities, and knowledge.
|
Custom condition |
Execute actions based on the response from the specified URL endpoint. The response from the endpoint should return boolean (true or false).
|
Custom variable |
Checks a custom variable that was relayed using JS API.
|
Date and time |
Executes actions during or outside of specified time frames.
|
Device Type |
Executes actions based on the device your visitor is using, such as desktop, mobile, or tablet.
|
Excluded visitor tags |
Executes actions based on the tags that a visitor does not have. Any visitor that does not have the tags you specify fires the action.
Tags are assigned to visitors through an engagement rule that uses the Add tag to visitor action. |
External Referrer |
Executes actions based on the external source that sent a visitor to your site.
|
Fingerprint |
Executes actions based on data provided by the visitor's browser: OS, OS Version, Browser, Browser Version, Language, Country and Location.
|
Included visitor tags |
Executes actions based on the tags that are assigned to visitors. Any visitor that has the tags you specify fires the action.
Tags are assigned to visitors through an engagement rule that uses the Add tag to visitor action. |
New and Returning Visitors |
Executes actions based on whether the visitor is new to your website or a returning visitor. To offer the engagement rule for new visitors:
To offer the engagement rule for returning visitors:
If you select both the New Visitors and Returning Visitors boxes, the engagement rule fires if the visitor is new or meets the returning visitor requirements. Note that visitor data is stored in the browser. If a visitor switches browsers, they are considered a new visitor. |
Proactive action grace period |
Executes actions based on the last time a proactive action was used. Any actions in this workflow that would be run during this time frame are skipped. The maximum grace period for proactive actions is 30 days.
|
Probability of execution |
Executes actions based on a probability percentage.
|
Scroll Depth |
Executes actions based on how far on the page a visitor scrolls.
Page URL Scroll Depth |
Time in queue |
Executes actions based on the average time contacts waited to talk with an agent over the past hour. The average is taken across all skills listed in the Queue/Skill field. For example, if you set this to Lower than 2 minutes, the engagement appears only if contacts waited, on average, less than 2 minutes to talk with an agent over the past hour.
|
UTM Parameters |
Executes actions based on information provided by the visitor's browser.
Source Medium Campaign Term Content |
Visited pages |
Executes actions if a visitor has previously been on one or more specified pages.
|
Add an Action
Watch a short video on adding an action to a Guide engagement rule.
-
From the detail page, click either Add new action or Add existing action, depending on if the action you want already exists.
- If you clicked Add new action, follow the steps to create the action you want.
- If you clicked Add existing action:
- Use the drop-down to select the action you want.
- Click Add.
Best Practices
-
A simple approach to display a Guide template or proactive offer on one or more pages is to the use Current page condition. This condition can specify one page where the template or proactive offer is displayed. It can also be defined more generally. For example, it might display the template or proactive offer on some or all pages of your website. Note the following:
-
Use the Equals operator for a more specific match on the URL. For example, you might use Equals www.classics.com to just display the template or proactive offer on the home page of your website.
-
Use the Contains operator for a more general match on the URL. For example, you might specify Contains classics.com to offer Guide on any page in your website that uses the domain classics.com in the page URL.
-
-
If you have a subdomain, such as www.sales.classics.com, be careful when specifying the matching page URL. For example, if you set the page URL as Contains classics.com, the rule will be a match for pages that use the classics.com or sales.classics.com domains.