1. Home
  2. Cookbook
  3. Campaigns
  4. Birthday and nameday emails

Birthday and nameday emails


You may want to contact your customers on their birthday and wish them all the best, or perhaps offer them something special (recommendations, discount coupon…). To do this, you have to have a customer attribute in date format with customer birthday. After that, you can create a scenario that will send out emails on a daily basis to people whose birthday is on that day.

  • Create a new scenario, and add a repeat trigger, a condition, and an email

birthday email

  • Set repeat trigger to daily at a desired time

birthday email trigger

  • Create a condition for customers whose birthday matches the current day and month

birthday email condition

  • Select a desired email template

If you don’t have any attribute with emails, you can always import one.


It is also possible to send customers emails on their name day, and it is possible to identify their name day based on their name from an imported catalog.

  • Import a catalog with the following attributes:
    • item_id – this will be a name that a customer can input when registering. Be sure to include multiple combinations of special characters/capital letters, as it needs to be a perfect match, e.g. have different ids for Martin, martin and MARTIN
    • Addressing name – this is an attribute you will use in the email, and will always be in correct form, e.g. martin is associated with Martin
    • gender (optional) – you can directly assign gender to names to have this attribute stored with the customers
    • nameday – a timestamp with the correct date. This can be a date of any year

It would look similar to this



  • Create a scenario where attributes will be assigned to customers daily based on the catalog. This scenario should run before any emailing is attempted.
    • Add a repeat trigger, a condition node, and three set attribute nodes
      nameday assign scenario
    • Set the condition only for customers not having nameday and addressing_name assigned yet, but first_name assigned
      Scenarios nameday condition
    • For each you should set attribute node, pair the attributes with their respective fields in the catalog using also Jinja as below, where
      • nameday in catalogs.nameday.item is catalog name
      • first_name is the attribute you use for storing first name of the customer
      • nameday in item.nameday is attribute you have in your catalog. This will be the only thing replaced when setting attributes for gender and addressing name.
      {% set item = catalogs.nameday.item_by_id(customer.first_name  | trim) %}{{ item.nameday }}

      Scenarios set attribute node

  • Now create a scenario from the birthday part, replacing the birthday attribute with the nameday attribute.
Updated on August 31, 2017

Was this article helpful?

Related Articles