Built in Personalization Tokens

Rob Howard Updated by Rob Howard

Below is a list of DailyStory's built-in tokens available for personalization:

Contact field tokens

The following personalization tokens are unique to each individual contact.

Important personalization tokens are case sensitive.
  • {{user.fullname}} - string; full name of the contact. If there is not first or last name, the email is returned.
  • {{user.firstname}} - string; first name of the contact.
  • {{user.lastname}} - string; last name of the contact.
  • {{user.email}} - string; email address of the contact.
  • {{user.country}} - string; country of the contact.
  • {{user.region}} - string; region or state of the contact.
  • {{user.city}} - string; city of the contact.
  • {{user.address}} - string; address of the contact.
  • {{user.postalcode}} - string; postal or zip code of the contact.
  • {{user.title}} - string; title of the contact.
  • {{user.phone}} - string; phone number of the contact.
  • {{user.mobile}} - string; mobile phone number of the contact.
  • {{user.website}} - string; url of the contact.
  • {{user.gender}} - string; gender of the contact.
  • {{user.age}} - number; age of the contact.
  • {{user.lastModified}} - date; when the contact was last modified in the account's timezone.
  • {{user.lastContacted}} - date; when the contact was last contacted in the account's timezone.
  • {{user.company}} - string; name of the company or organization the contact is part of.
  • {{user.industry}} - number; industry code number the contact is part of.
To account for when a user does NOT have a first name but you still want to use their first name when they do, you can use {{@ user.firstname, default="friend"}}. This will insert the word friend if the user does not have a first name.

Account field tokens

The following personalization tokens are global to your account within DailyStory. Many are set in account settings.

  • {{account.name}} - string; name of the account.
  • {{account.address}} - string; physical address of the account.
  • {{account.phone}} - string; phone number of the account.
  • {{account.url_website}} - string; url to the account's website.
  • {{account.url_appstore_google}} - string; url to the account's Android App download.
  • {{account.url_appstore_ios}} - string; url to the account's Apple App download.
  • {{account.url_facebook}} - string; url to the account's Facebook page.
  • {{account.url_instagram}} - string; url to the account's Instagram page.
  • {{account.url_linkedin}} - string; url to the account's LinkedIn page.
  • {{account.url_pintrest}} - string; url to the account's Pintrest page.
  • {{account.url_twitter}} - string; url to the account's Twitter page.
  • {{account.url_tiktok}} - string; url to the account's TikTok page.
  • {{account.url_yelp}} - string; url to the account's Yelp page
  • {{account.url_youtube}} - string; url to the account's YouTube page.

System tokens

The following tokens are tokens that evaluate to common values and are useful for comparisons. These dates are in the account's timezone.

  • {{system.today}} - date; evaluates to today's date localized for your account.
  • {{system.year}} - number; returns the current year.
Specify a custom date / time value using {{formatDate system.today "MMMM d, yyyy"}}.

Common Date & Time formats

String

Result

MMMM d, yyyy

September 3, 2020

MMM d, yyyy

Sept 3, 2020

MMM d, yyy h:mm tt

Sept 3, 2020 8:30 AM

ddd, MMM d, yyyy 'at' h:mm tt

Fri, Sept 3, 2020 at 8:30 AM

Many of the account tokens are built into templates and designers.

For example, the URLs set for App download or Social buttons in the email designer is automatically set using the Account personalization tokens.

The screen shot below shows the email designer with the app store button for Google Play selected. The url is set to the personalization value for Google's App Store in account settings.

Note you can replace the personalization token with a direct URL too.

How Did We Do?

Personalization Guide

Custom Personalization Tokens

Contact