Visitor Inactivity
Origin: Proactive
This trigger fires when the contact becomes inactive on the page. This is measured by number of clicks over a period of time.
Create This Trigger
- Click the app selector
and select ACD.
-
Go to Digital > Automation Triggers.
-
Click Add trigger.
- Enter a Name for the trigger. Since you can assign multiple jobs to the same trigger, use a name based on the event or conditions rather than an associated job.
-
From the Event drop-down, select Visitor inactivity.
-
From the Application Type drop-down, select Browser or Native. This changes the conditions that are available for this trigger. See the sections below for details.
- In the Delayed execution field, enter the number of seconds that Digital Experience should wait after the selected event occurs before firing the trigger. If you want it to happen immediately, enter 0.
- If you have folders that organize your triggers, you can select which folder to put this trigger in from the Folder drop-down.
- Click Save.
- From the detail page, click Activate when your trigger 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.
If you entered a value in the Delayed execution field when you created a trigger, configure conditions under both the Conditions and Delayed conditions sections or just the regular Conditions section. If you only configure Delayed conditions, the system may duplicate events.
- 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
If the Application Type drop-down is set to Browser, the following triggers are available.
Condition Type | Details and Instructions |
---|---|
Chat Is Active |
Execute jobs if the chat window displays an online status.
|
Current page |
This condition checks the page URL and time spent on that page to trigger the job on specific page.
Time spent on page |
Custom condition |
Execute jobs based on the response from the specified URL endpoint. The response from the endpoint should return boolean (true or false). This condition works for contact center triggers, proactive triggers, and schedulers.
|
Custom script |
Execute jobs based on the script you write in Primi language. This condition works for contact center triggers, proactive triggers, and schedulers. |
Custom variable |
Checks a custom variable that was relayed to Digital Experience using JS API.
|
Date and time |
Executes jobs during or outside of specified time frames.
Jobs can process up to 500 contacts at a time. If you need to process more, have the job run more than once per day at different times. |
Device Type |
Executes jobs based on the device your visitor is using, such as desktop, mobile, or tablet.
|
Element Clicked |
Executes jobs if a user clicks on a mapped part of your website. This requires the use of Web Assistant.
|
External referrer |
Executes jobs based on the external source that sent a visitor to your site.
|
Field is edited |
Executes jobs if a user changes the value of a mapped field on your website. This requires the use of Web Assistant.
|
Fingerprint |
Executes jobs based on data provided by the visitor's browser: OS, OS Version, Browser, Browser Version, Language, IP Address, Country and Location.
|
Included channels condition |
Checks whether the chat window that is on the website belongs to specific channel. This trigger works for both contact center triggers and proactive triggers.
|
Number of clicks |
Executes jobs based on the number of times a visitor clicks on a specific page. This trigger is good for measuring "rage clicks."
Page URL Number of clicks Clicks period |
Probability of Execution |
Executes jobs based on a probability percentage. This condition works for contact center triggers, proactive triggers, and schedulers.
|
Scroll depth |
Executes jobs based on how far on the page a visitor scrolls.
Page URL Scroll Depth |
Time spent on page |
Executes jobs based on how much time a visitor spent on one page of your site. This depends on a specified period of time.
Page URL Time spent on page |
Time spent on site |
Executes jobs based on how much time a visitor spent on your site. This depends on a specified period of time.
Website URL Time spent on website Number of passed days |
UTM Parameters |
Executes jobs based on information provided by the visitor's browser.
Source Medium Campaign Term Content |
Visited pages |
Executes jobs if a visitor goes to one or more specified pages.
|
Visitor is inactive |
Executes jobs based on how long a visitor is inactive on your site. This is measured by number and frequency of clicks.
|
Available Conditions: Native
If the Application Type drop-down is set to Native, the following triggers are available.
Condition Type | Details and Instructions |
---|---|
Chat Is Active |
Execute jobs if the chat window displays an online status.
|
Custom condition |
Execute jobs based on the response from the specified URL endpoint. The response from the endpoint should return boolean (true or false). This condition works for contact center triggers, proactive triggers, and schedulers.
|
Custom script |
Execute jobs based on the script you write in Primi language. This condition works for contact center triggers, proactive triggers, and schedulers. |
Custom variable |
Checks a custom variable that was relayed to Digital Experience using JS API.
|
Date and time |
Executes jobs during or outside of specified time frames.
Jobs can process up to 500 contacts at a time. If you need to process more, have the job run more than once per day at different times. |
Device Type |
Executes jobs based on the device your visitor is using, such as desktop, mobile, or tablet.
|
External referrer |
Executes jobs based on the external source that sent a visitor to your site.
|
Fingerprint |
Executes jobs based on data provided by the visitor's browser: OS, OS Version, Browser, Browser Version, Language, IP Address, Country and Location.
|
Included channels condition |
Checks whether the chat window that is on the website belongs to specific channel. This trigger works for both contact center triggers and proactive triggers.
|
Probability of Execution |
Executes jobs based on a probability percentage. This condition works for contact center triggers, proactive triggers, and schedulers.
|
UTM Parameters |
Executes jobs based on information provided by the visitor's browser.
Source Medium Campaign Term Content |
Visited pages |
Executes jobs if a visitor goes to one or more specified pages.
|
Visitor is inactive |
Executes jobs based on how long a visitor is inactive on your site. This is measured by number and frequency of clicks.
|
Add a Job
-
From the detail page, click either Add new job or Add existing job, depending on if the job you want already exists.
- If you clicked Add new job, follow the steps to create the job you want. These steps can be found on the individual help page for that job, located in the menu on the left of this page.
- If you clicked Add existing job:
- Use the drop-down to select the job you want.
- Click Add.