Merge Tags and Dynamic Substitution Tags

  • Updated

In order to personalize campaigns and Automations, Engage provides the ability to substitute dynamic information about your guests and those guests' preferences into campaigns. You can add those supported substitution tags to your campaigns to have those automatically included.

Skip To:

Tag Library
You can view the list of supported tags in the Tag Library accessible in our Automations tool.

Note there shouldn't be spaces between the {{ and text

  • Example: {{ guest -> {{guest

User-uploaded Image

Want to copy and paste the values above? Use the text below: 

{{first_name}}

{{last_name}} 

{{email}}

{{phone}}

{{birth_day}}

{{birth_month}}

{{anniversary_day}}

{{anniversary_month}}

{{postal_code}}

{{sparkly_offer_url}}

{{guest _selected_home_location_name}}

{{send_date;plus_x_days}}

Note: the list of available tags will only show up if a substitution tag is detected in the templates. In addition, if tags detected are in the wrong format, the Automations tool will provide a visual indication. See below:
User-uploaded Image
  • These subtags pull ONLY from the Engage database. Custom fields uploaded to SendGrid ARE NOT supported. 
  • Default values
    • If a field does not have a value, by default, Wisely will leave the field blank. If you want to provide your own default value, you can do with in the following format:
      • {{ first_name % default_value }}
      • For example: Hey {{ first_name % there }}

Dynamic Expiration Substitution Tags

These are ideal if you want to send Automations with offers that expire. Given that you have Automations that are sent on a rolling schedule, you can create them with an expiration date that is created dynamically. A new dynamic substitution tag dynamically populates an expiration date relative to the send date.

If any substitution tags are detected in the email template, the available library of tags appears.

Examples of Dynamic Expiration Substitution Tags:

      • 14 days from the send date would be written {{send_date;plus_14_days}}
      • 2 weeks from the send date would be written {{send_date;plus_2_weeks}}
      • 3 months from the send date would be {{send_date;plus_3_months}}
      • 1 year from the send date would be written {{send_date;plus_1_years}}

Note: All of the days/weeks/months/years attributes are in the plural - even if doing 1 week, the correct format is 1_weeks (it will show a broken tag if not formatted in the plural).

The following is an example of an incorrectly configured attribute:

User-uploaded Image


Want to take a look at the Engage Automations Handbook?

Click HERE!

Related articles