Pre-Populating Data Asks & Data Elements for Chat Experiences

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 a number of different variables.

image2.png

If you set multiple pre-population options, UTMs will take precedence, followed by the Data Provider, and then the Initial Value.


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.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.