Lifecycle Optimizer Step Glossary

Entries

Transactional Sent – Begins flow when user is sent transactional email using specified template.

  • A transactional send may have been initiated by Send API, trigger, or LO itself.

Transactional Opened – Begins flow when user opens transactional email sent with specified template.

  • Template A/B variants are identified as such. You may choose to select a specific variant to be used for the entry.

Transactional Clicked – Begins flow when user clicks a link in transactional email sent with specified template.

  • Template A/B variants are identified as such. You may choose to select a specific variant to be used for the entry.

List Joined – Begins flow when user is added to specified natural list via User API call. This also includes other “Add to List” actions within Lifecycle Optimizer.

  • You can use the User API call from your server or use one of Sailthru’s onsite JS functions. Please note this does not currently include list additions from bulk updates or Sailthru Hosted Pages.

Purchase Made – Begins flow when a user makes a purchase, as registered by a Purchase API call or the purchase JS function on site.

  • Purchases made with the bulk import job will start flows
  • Purchase calls with the “incomplete_purchase” parameter will not start a flow
  • Adjustments are reflected in the evaluation of purchase order price
  • Purchases with any order value (including negative) will start flows
  • If any item in an order has a negative purchase quantity, the purchase will not start a flow
  • Optional filter “First Purchase?” evaluates if its the first-ever purchase by the user (as based on the first purchase timestamp on their profile)

Custom Event API – begins flow when an Event API call or event JS function call matching your specified Event Name is received for the user.

  • Optional filter for custom fields (vars) included with each call can include users matching specific event criteria
  • Custom fields names and values are available via Zephyr to templates within the respective flow; the custom field name “class_rating” would be available in Zephyr as {class_rating}

Waits

Wait – Holds the user from proceeding in the flow for a specified period of time.

Actions

Send Email – Sends an email to the user using the specified template.

  • Select a Data Feed if you want to use one that is not already associated with the template.
  • To edit or preview the selected template, click the edit icon. Updates to creative take place immediately for all users who have not yet entered the step.

Add to List – Adds the user to the specified natural list.

  • You cannot directly add users to a smart list. If you would prefer to add the user to a smart list, instead use Add Custom Fields to set a variable that is used in the smart list’s criteria.
  • A list by the entered name will be created if it does not already exist.

Remove from List – Removes user from the specified natural list.

Set Custom Fields – Add or update custom field value on user’s profile.

  • Search and select from field names in use, or enter a new one that will be created.
  • If a value for the selected field already exists for the user, it will be updated.
  • Value type is automatically detected. To preserve leading zeroes in a number (e.g. zip code 01234), put the number in quotes (“01234″) so that it is stored as text, rather than converted to the number 1234.

Increase/Decrease Custom Fields – Updates the existing value of a custom field on the user profile, adding or subtracting your specified number.

  • If the value does not already exist, or is not a number, it will be evaluated as a 0. For example, if the value of field “score” is “none,” and you choose to add 5, the new value will be 5 (0+5).

Remove Custom Fields – Removes specified custom field name and value from user’s profile.

Checks

For each check, you will select whether the user should proceed with the flow (“Yes”) or end the flow (“No”) if they match the selected criteria.

User Visited Site – The last known pageview date for a user, as determined by Sailthru’s on-site JS.

Purchase Made – Purchase made by the user since the time specified.

  • As registered by a Purchase API call or the purchase JS function on site.
  • Optional filter “First Purchase?” evaluates if its the first-ever purchase by the user (as based on the first purchase timestamp on their profile)

Opt-out Status – The user’s opt-out status at time of check.

Email Opened – The user opened a message sent by a selected step in the flow.

  • This check only references template messages sent by the flow. It will not include Send API calls to the template.
  • Includes any message sent by the selected step in the flow. The evaluation will still work if you change the template name and update the flow.
  • Evaluates “beacon” [image load] only, not implied opens. Implied opens are cases where the beacon does not load (e.g. due to the user blocking images) yet a click in the email is registered, indicating that it was opened.
  • Template A/B variants are identified as such. You may choose to select a specific variant to be used for the check.

Email Clicked – The user clicked a link in email that was sent by a selected step in the flow.

  • Only references template messages sent by the flow. Does not include Send API calls to the template.
  • Includes any message sent by the selected step in the flow. The evaluation will still work if you change the template name and update the flow.
  • Is not specific to a given link. If any link in the email is clicked, the user will meet the criteria of the check. You can use a URL parameter to apply a custom field variable to user when they click a specific email link. You can then use a Check step to evaluate against the variable’s presence.
  • Template A/B variants are identified as such. You may choose to select a specific variant to be used for the check.

Custom Profile Field – Evaluates one or more custom profile fields (user vars) based on defined criteria and specified values.

  • Search or select from the list of fields names, which contains all that currently exist across your user profiles, plus any additional field names that may be added per other steps in this flow.
Top