Customer.io aims to help you send the right messages at the right time to your users. A critical part of this is sending messages in a given person’s time zone, and localizing time in emails! Here, we’ll explain how to do both.
IMPORTANT NOTE: Time Zone Match cannot be used for newsletter scheduling. It can only be used with the Time Window workflow items you add to your triggered campaign workflows.
We ask that you use an attribute named
timezone in your users’ profiles. You can store time zone data in their profiles with a different attribute name, but you need to use the specific
timezone attribute (in the correct format) in order to make use of this feature.
This restriction help us ensure that time zone matching works correctly and lets us validate that the data is entering Customer.io in the right format.
Head over to the Email & Actions area of Customer.io, and find the Time Zone Match feature:
There you can test that you’ve sent us the
timezone attribute in the right format. We support the Regional Format shown here, so something like
Canada/Pacific will work, but
(GMT-08:00) Pacific Time (US & Canada) will not pass. This is what test looks like, both unsuccessful and successful:
Time zone match is visible by default on the Time Window action items in your workflows:
With this setting, you can tell Customer.io to wait until a given time in a customer’s time zone before taking the next action.
You must also set a fallback here, telling Customer.io which time zone to use if a customer doesn’t have the
If you want the time(s) in your messages to be localized, we can do that, too!
Say you want to send an appointment reminder, and you have an
appointment_time timestamp. If that appointment time is a UNIX timestamp— for example, 2014113600—
'US/Pacific', then the above Liquid code will display:
Friday Oct 28, 2033 at 05:00 PDT
For Customer.io and time zones: