Variable tag library

Qualified visitor fields have special syntax that lets them be used as variables in messenger messages, referenced in the Qualified client-side API, or prefilled with URL variables.  See below for the syntax and variable names for these fields.

In all applications, variable names should be all lowercase. 

Qualified visitor field variables

Standard visitor fields

These visitor fields exist and are recognized by default in Qualified.

• visitor.first_name
• visitor.last_name
• visitor.full_name
• visitor.city
• visitor.state
• visitor.state_iso_code
• visitor.country
• visitor.country_iso_code
• visitor.region
• visitor.playback_url
• visitor.initial_referrer
• visitor.initial_landing_page_url
• visitor.conversion_page_url

Date and time fields

• system.current_time
• system.current_date

Note that system.current_time is provided in ISO 8601 format in the UTC time zone. Conversion may be required

Custom visitor fields

• visitor.fields.[field api name]

URL parameters

• visitor.params.[parameter name]

Use this option when a URL parameter is not mapped to an existing Qualified visitor field . If the parameter is mapped to a Qualified visitor field, the value will be prefilled to that field and can be used in that way.

UTM parameters

• visitor.utm_source
• visitor.utm_campaign
• visitor.utm_medium
• visitor.utm_content
• visitor.utm_term

Qualified owner values

• visitor.owner.full_name
• visitor.owner.first_name
• visitor.owner.last_name
• visitor.owner.email
• visitor.owner.salesforce_user_id

A Qualified owner is the rep who has most recently (a) had a conversation with the visitor or (b) booked a meeting with the visitor.  Qualified owner may or may not match the visitor’s Salesforce Lead or Contact owner.

Meeting booked values

• calendar_event.duration OR =calendar_event.duration_in_minutes
• calendar_event.meeting_type_name
• calendar_event.starts_at OR =calendar_event.starts_at_iso
• calendar_event.ends_at OR =calendar_event.ends_at_iso
• calendar_event.conference_details
• calendar_event.meeting_channel
• calendar_event.attendee_names
• calendar_event.attendee_salesforce_ids
• calendar_event.rep.name
• calendar_event.rep.email
• calendar_event.rep.phone_number
• calendar_event.rep.salesforce_id
• calendar_event.rep_who_offered.name
• calendar_event.rep_who_offered.email
• calendar_event.rep_who_offered.phone_number
• calendar_event.rep_who_offered.salesforce_id

External data source values

Salesforce Lead/Contact/Account record values

Refer to any field on the Lead, Contact, or Account record:

• visitor.external_fields.salesforce_lead.[field_name]
• visitor.external_fields.salesforce_contact.[field_name]
• visitor.external_field.salesforce_account.[field_name]

MAP record values

Refer to fields on the Marketo, Hubspot, Pardot, or Eloqua person records:

• visitor.external_fields.marketo_contact.[field_name]
• visitor.external_fields.hubspot_contact.[field_name]
• visitor.external_fields.pardot_prospect.[field_name]
• visitor.external_fields.eloqua_contact.[field_name]

Enrichment values

Refer to fields from Clearbit Enrichment, Clearbit Reveal, and 6Sense data

• visitor.external_fields.clearbit_enrichment.person.[field_name]
• visitor.external_fields.clearbit_enrichment.company.[field_name]
• visitor.external_fields.clearbit_reveal.company[field_name]
• visitor.external_fields.6sense.[field_name]

Variable syntax

Messenger markdown

To use a visitor field in messages sent by the Qualified messenger in rules-based experiences, in the text editor click the blue visitor icon to access a menu of all visitor fields.

Search or browse for the relevant variable, enter fallback text (which will be used if the variable is blank), and then click done.

Visitor fields can also be entered direclty by surrounding the full variable name in double curly brackets.

Client-side API

When referencing a visitor field using the Qualified Client-Side API, simply use the API name listed in Settings → Visitor Fields. In most cases, this will be the name of the visitor field, in all lower case and with the spaced replaced with underscores.  Do not use prefix attributes like visitor or system when writing API names.

If you don’t see the API Name column, click the blue Show API Names option near the top of the page.

URL variable prefill

To prefill a variable as part of a URL, after the end of the url, place a question mark followed by the API name, an equals sign, and the value to fill. For spaces in the value, use %20. 

Qualified will detect the visitor field and populate the value into the appropriate visitor field.

The question mark is only required before the first URL parameter if multiple variable names are used.