Note for Chat Customers
The functionality described in this article will only pertain to Terminus customers who have access to the Chatbots page in their Chat Experiences instance. For Terminus customers using Chat Playbooks, the tokenization feature will replace variable usage.
Types of Chat Personalization
Your web visitors are more likely to engage, and do so at a deeper level, when their experience is personalized. Terminus Chat Experiences allow you to personalize chat interactions in multiple places.
Proactive Messages
Proactive Messages invite your visitors to chat with you.
Engagement Window
Once the chat has been initiated, personalize the messaging within the window.
Pre-Populating Data Asks/Elements
Data Asks (Information you would ask a visitor for) and Data Elements (Information you want to track, but would not ask a visitor for) can be pre-populated with any variable as well.
If you set multiple pre-population options, UTMs will take precedence, followed by the Data Provider and finally the Initial Value.
Variable Usage
After you find the variables you would like to use in the list below, apply them in either the workflow (in the Proactive Message section), or the Terminus Bot Builder.
BIG NEWS, {system.variables.utm}: Ramble was acquired by Terminus! Read the news here
Additionally, if you want to use conditionalization, (for example, you may or may not know if the UTM variable will be present), you can write your message like this:
BIG NEWS{system.variables.utm != null ? ", " : terminus.name != null ? ", " : ""}{system.variables.utm != null ? system.variables.utm : ipDomain.name != null ? ipDomain.name : ""}: Ramble was acquired by Terminus! Read the news here
The following operators are available:
== (equals)
!= (not equals)
~ (contains)
!~ (not contains)
~ /regex/
!~ /regex/
Variable List
UTM Variables
- variables.utm_name
- variables.company
Visitor (Previous chat, visitor-provided)
- visitor.name
- visitor.email
- visitor.phone
- visitor.website
- visitor.company
- visitor.rating
- visitor.note
Chat Info
- system.userAgent
- system.ip
Browser
- system.browser.name
- system.browser.major
- system.browser.version
OS
- system.os.name
- system.os.version
Device
- system.device.name
- system.device.model
- system.device.vendor
Page Context
- system.page.domain
- system.page.page
- system.page.title
- system.page.fullUrl
Referrer
- system.referrer.domain
- system.referrer.page
- system.referrer.fullUrl
Location
- location.continent
- location.country
- location.state
- location.city
Terminus
- terminus.industry
- terminus.name (company name)
- terminus.domain
- terminus.sicCode
- terminus.sicDescription
- terminus.naicsCode
- terminus.naicsDescription
- terminus.employeeRange
- terminus.revenueRange
Feature Note
In most cases, it is better to use visitor.company and visitor.website rather than terminus.name or terminus.domain respectively. The advantage is that the "visitor." prefix will look for existing values and fall back to IP lookup if they don't exist.
Comments
0 comments
Article is closed for comments.