Using Dynamic Tags (MergeVars) in Triggers

When creating Automations you can make use of the data available on the visitor. You do this using MergeVars in your automation. 

There are two objects that you can access different properties on: Session and Contact. The Session parameters are always available but the Contact parameters are only available when the visitor is know. So using the Contact data can only be used when executing an Automation for sessions that have a conversion/contact (like Widget Form Conversion).

Here is a list of available parameters:

Contact

  • {{contact.detailsUrl}}
  • {{contact.firstname}}
  • {{contact.lastname}}
  • {{contact.email}}
  • {{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

  • {{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}}
  • {{session.country}}

Custom Fields

If you are using custom fields in your contact form widget, you can use this parameter to fetch the data in the field. 

  • {{session.custom.Customfield}}

Consent Values

When your form has recorded a Consent event you can access these values using the below parameters. Consent is recorded in all widget forms when the Triggerbee Consent-module is activated and the form in the Widget is connected with Triggerbee Consent-module. A Consent event can also be scripted from your own custom forms

  • {{session.custom.pp_url}}   ex:  "https://privacypolicy.trgr.be/gpp/7216632833/188/2018-02-18-sv.html"
  • {{session.custom.pp_version_date}}        ex: "02/18/2018 09:26:23"
  • {{session.custom.pp_revision_number}} .    ex: "188",
  • {{session.custom.pp_accepted_title}}    ex: "Marketing Automation för B2B, B2C och E-handelsföretag - Triggerbee",
  • {{session.custom.pp_accepted_url}}      ex: "https://triggerbee.com/sv/#conversion-154549876"
  • {{session.custom.pp_current_url}}   ex: "https://triggerbee.com/sv/boka-demo"
  • {{session.custom.pp_title}}   ex: "Discover Business Opportunities Already Hiding in Your Traffic"
  • {{session.custom.pp_text}}   ex: "Boka kostnadsfritt demo av Triggerbee idag!"

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 scripted 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|*  

Still need help? Contact Us Contact Us