Messaging
  • Templates
  • Campaigns
    Campaigns Overview Regular Campaigns Recurring Campaigns SMS Messaging AB Split Campaigns AB Winner Campaigns AB Auto Winner Campaigns View and Organize Campaigns GreenArrow Monitoring
  • Triggered Messages
    Triggered Messages Overview Transactional Messages Overview Set Up a Triggered Message Create Template Triggers for Messages Abandoned Shopping Carts AB Split Testing Triggered Messages Force Send Purchase Emails Smart Strategies
  • Promotions
    Promotion Codes
  • Ad Targeter
    Ad Targeter Overview Create an Ad Plan Create an Ad Plan Schedule Target Users with Ad Targeter
  • Data Feeds
    Data Feeds Overview Set Up a Data Feed Create a Content Feed from Your Content Library Content Search in Recommendations Use Feeds and Other Content Data in Templates Build a Campaign from an Edited Feed using Recommendations Call an External Data Feed Example Feeds The Sailthru RSS Extension
  • Deliverability
    Configure DNS Records

    • Implement LiveIntent Tags

    LiveIntent tags require unique variables (macros) to function properly. The values are called into LiveIntent tags at the time the email is sent.

    The variables include:

    • An email
    • A unique placement id
    • A list id (optional, but used for reporting)

    To set these up in Sailthru, you’ll need to swap these LiveIntent values with Sailthru template variables using Zephyr.

    LiveIntent Tag Description Sailthru Template Variable
    Email Maps to an email or an MD5 hash of an email in Sailthru.
    Variable
    e={Email}
    m={MD5 hash} (recommended)

    Note: As a privacy best practice, hash email addresses.

    		Email
    {email}

    MD5 hash of an email
    {md5(email)}

    Placement ID This must be a unique number specific to the individual user and the campaign. To get this kind of value, we recommend combining the “emailnum” variable with a date value or the blast id.

    Emailnum represents the order of the message in the total send, i.e. 20 would be the 20th message sent in the campaign
    Variable
    p={Placement ID}

    		Date and emailnum
    {date(‘MMddyyyy’)+emailnum}

    Blast ID and emailnum
    {blast.id+emailnum}

    List ID
    optional, but needed for reporting     		Sailthru does not have a template variable called list_id. You can use other Sailthru values to identify the campaign in their reporting. We recommend:

    • The numerical campaign ID
    • The campaign list name
    • The campaign name

    Variable
    li={List ID}

    		Numerical campaign ID {blast.id}

    Campaign list name
    {blast.list}

    Campaign Name
    {blast.name}

    Key/Value Pairs Set custom key/value pairs for demographic data or list segments.
    Variable
    {key}={variable}     		Reference Sailthru’s template or profile custom fields as needed.

    Using LiveIntent Values in Templates

    • In the Template Editor, add LiveIntent tags to your template as you build it.
    • In Email Composer, add an HTML block and add LiveIntent tags to your template there.
      • To add an HTML block to your template in Email Composer:
        1. Decide on your template formatting. If you’re using the available row structures, drag them into place on your template.
        2. Drag an HTML block from the Content Pane to your desired location in your template.
        3. Click the HTML block. The Content Properties pane opens for your HTML block.
        4. Add your LiveIntent tags in the HTML composer in the Content Properties pane.
          HTML editor from Email Composer
        5. Finish editing your template.
    Top