Using Dynamic Values in Automation Rules

When creating Automation Rules you can make use of the data available on the visitor. The Session parameters are always available but the Contact parameters are only available when Triggerbee has a visit from a known contact, so these should only be used when executing a Automation Rule for sessions that have a conversion / contact.

Here is a list of available parameters:


  • contact.detailsUrl
  • contact.firstname
  • contact.lastname
  • contact.telephone
  • contact.organization
  • contact.interest1
  • contact.interest2
  • contact.campaigns
  • contact.goals
  • contact.labels
  • contact.lastVisit
  • contact.firstSeen
  • contact.conversionDate
  • contact.visitCount
  • contact.engagementScore


  • session.goals
  • session.campaign
  • session.landingpage
  • session.activityCount
  • session.totalTime
  • session.interest1
  • session.interest2
  • session.referrer
  • session.utm_medium
  • session.utm_source
  • session.utm_campaign
  • session.detailsUrl

Custom form values

If you script content to the session using the custom.session JSON object you can also access these like this:

  • session.custom.propertyName
  • session.custom.companySize
  • session.custom.foodAllergies

Note: These properties are not automatically accessible on in the custom.session object. They must be scriptet by the developer, like this:

var mtr_custom = mtr_custom || {};
mtr_custom.session = { foodAllergies: "Lactose" };


How to use

Use the parameters by surrounding them with double brackets like this: {{contact.firstname}}

The dynamic parameters are automatically added to connected email apps. In Mandrill and Mailchimp you access the parameters in this syntax (and notice that the dot is replaced with an underscore): *|contact_firstname|*