Customizing your SMS content allows you to connect with your users more friendly and engagingly, often leading to higher returns than non-personalized messages.
Note: {{ ... }} indicates dynamic variables (custom fields) automatically pulled from the system. This is the standard usage pattern.
You should not manually include the curly brackets ({}) in the dynamic attribute’s input field. The system adds them automatically.
Customize date format
You can format your default and custom data attributes, such as {{birthday}}, in different formats. Below is the sample formatting syntax for the SMS design:
{{attribute_name|time-format=DD-MM-YYYY}}
Your title goes here
If you want to customize your values, you can specify and write your preferred format in the fallback field. Moreover, you can either apply a customization or assign a fixed value to the fallback field; both options are available and can be used simultaneously.
You have the flexibility to apply customization and assign a fixed date to the fallback field; these options are not mutually exclusive and can be used together. Below, you can see the date example:
Fixed Date|time-format=MM-DD-YYYY
You can customize your date formatting. Once you insert your attribute representing the date, the date value of this attribute will be displayed in a human-readable format. You can use this for any date-type attribute like birthday, registration date, release date, etc. Below, you can see some examples:
{{custom_field|time-format=DD-MMM-YYYY}}
{{custom_field|time-format=MMMM/DD/YY}}
{{custom_field|time-format=MMMM/D/YY}}
The date parameters in the example above have different formats, such as DD, D, YY, and YYYY. When you use the first example as an attribute in your SMS message, it can be converted to a user as 07-Nov-2024, while the second is November/07/24.
You can customize your attribute values using the following formats:
Formatting | Description | Example |
|---|---|---|
DD | Day as number with zero | 07 |
D | Day as number without zero | 7 |
M | Month as number with zero | 09 |
MM | Month as number without zero | 9 |
MMM | Month as text in short format | Mar |
MMMM | Month as text in full format | March |
YY | Last two digits of the year | 23 |
YYYY | Year as number in full format | 2023 |
You can also use custom time formats with different time parameters. Below, you can see some examples:
{{custom_field|time-format=hh:mm:ss}}
{{custom_field|time-format=hh:mm}}
{{custom_field|time-format=HH:mm:ss}}
The time parameters in the example above have different formats like hh, HH, and mm. You can customize your attribute values using the following formats:
H, HH, h, hh | Hour |
M, MM, m, mm | Minute |
s, ss | Second |
A, a | PM and AM |
Your title goes here
If the time value is exactly 00:00:00, it will always be converted to 12:00:00.
You can use both date and time formats inside the same dynamic content in both your SMS campaigns and Architect SMS campaigns. For example, the {{custom_field|time-format=YYYY-MM-DD hh:mm:ss A}} attribute can be converted as 2024-09-11 11:21:13 PM.
Below, you can see all supported date and time formats. The results are created based on 2024-04-11T15:21:13Z.
Date and Time Formats
Date and time format | Result |
|---|---|
M/DD/YYYY | 4/11/2024 |
MM/DD/YYYY | 04/11/2024 |
MMM/DD/YYYY | Apr/11/2024 |
MMMM/DD/YYYY | April/11/2024 |
M/DD/YY | 4/11/24 |
MM/DD/YY | 04/11/24 |
MMM/DD/YY | Apr/11/24 |
MMMM/DD/YY | April/11/24 |
DD/M/YYYY | 11/4/2024 |
DD/MM/YYYY | 11/04/2024 |
DD/MMM/YYYY | 11/Apr/2024 |
DD/MMMM/YYYY | 11/April/2024 |
DD/M/YY | 11/4/24 |
DD/MM/YY | 11/04/24 |
DD/MMM/YY | 11/Apr/24 |
DD/MMMM/YY | 11/April/24 |
DD-M-YYYY | 11-4-2024 |
DD-MM-YYYY | 11-04-2024 |
DD-MMM-YYYY | 11-Apr-2024 |
DD-MMMM-YYYY | 11-April-2024 |
DD-MM-YY | 11-04-24 |
YYYY-M-DD | 2024-4-11 |
YYYY-MM-DD | 2024-04-11 |
YYYY-MMM-DD | 2024-Apr-11 |
YYYY-MMMM-DD | 2024-April-11 |
M/D/YYYY | 4/11/2024 |
MM/D/YYYY | 04/11/2024 |
MMM/D/YYYY | Apr/11/2024 |
MMMM/D/YYYY | April/11/2024 |
M/D/YY | 4/11/24 |
MM/D/YY | 04/11/24 |
MMM/D/YY | Apr/11/24 |
MMMM/D/YY | April/11/24 |
D/M/YYYY | 11/4/2024 |
D/MM/YYYY | 11/04/2024 |
D/MMM/YYYY | 11/Apr/2024 |
D/MMMM/YYYY | 11/April/2024 |
D/M/YY | 11/4/24 |
D/MM/YY | 11/04/24 |
D/MMM/YY | 11/Apr/24 |
D/MMMM/YY | 11/April/24 |
M-D-YY | 4-11-24 |
MM-D-YY | 04-11-24 |
MMM-D-YY | Apr-11-24 |
MMMM-D-YY | April-11-24 |
D-M-YYYY | 11-4-2024 |
D-MM-YYYY | 11-04-2024 |
D-MMM-YYYY | 11-Apr-2024 |
D-MMMM-YYYY | 11-April-2024 |
D-M-YY | 11-4-24 |
D-MM-YY | 11-04-24 |
D-MMM-YY | 11-Apr-24 |
D-MMMM-YY | 11-April-24 |
MMM D, YYYY | Apr 11, 2024 |
MMMM D, YYYY | April 11, 2024 |
YYYY-MM-DD hh:mm:ss | 11/04/2024 03:21:13 |
hh:mm:ss | 03:21:13 |
YYYY-MM-DD hh:mm:ss A | 2024-04-11 15:21:13 PM |
YYYY-MM-DD hh:mm:ss a | 2024-04-11 15:21:13 pm |
H:m:s | 15:21:13 |
H:m:ss | 15:21:13 |
HH:m:ss | 15:21:13 |
HH:m:ss | 15:21:13 |
h:m:s | 03:21:13 |
h:m:ss | 03:21:13 |
hh:m:s | 03:21:13 |
hh:m:ss | 03:21:13 |
H:mm:s | 15:21:13 |
H:mm:ss | 15:21:13 |
HH:mm:s | 15:21:13 |
HH:mm:ss | 15:21:13 |
h:mm:s | 03:21:13 |
h:mm:ss | 03:21:13 |
hh:mm:s | 03:21:13 |
hh:mm:ss | 03:21:13 |
D MMM | 11 Apr |
D MMMM | 11 April |
Once you complete designing your SMS campaign, make sure to send a test SMS to yourself to make sure your attributes function as you set them.
Customize number format
You can insert separators to number-type default and custom attributes—such as {{price}}, {{amount}}, and {{phone_number}}—so that the dynamic content in your SMS is more readable for recipients.
You can use a comma (,), a dot (.), a space ( ), and an apostrophe (') as thousand and decimal separators.
Syntax example: {{dynamic_attribute|number-format=thousand_separator,decimal_separator}}
thousand_separator: Specifies the character used to separate thousands.
decimal_separator: Specifies the character used to separate decimals.
If you customize the number format for any dynamic attribute, you cannot add a fallback value to that attribute.
Examples
Below are some examples of the usage of the thousand and decimal separators.
Separator | Syntax | Example |
|---|---|---|
Dot as thousand | {{last_purchase_amount|number-format=dot,comma}} | 1.234.567.890,00 |
Comma as thousand | {{last_purchase_amount|number-format=comma,dot}} | 1,234,567,890.00 |
Apostrophe as thousand | {{last_purchase_amount|number-format=apostrophe,comma}} | 1'234'567'890,00 |
Space as thousand | {{last_purchase_amount|number-format=space,dot}} | 1 234 567 890.00 |
Dot as thousand | {{last_purchase_amount|number-format=dot,comma}} | 1.234.567.890,00 |
Dot as thousand | {{last_purchase_amount|number-format=dot,dot}} | 1.234.567.890.00 |
Apostrophe as thousand | {{last_purchase_amount|number-format=apostrophe,dot}} | 1'234'567'890.00 |
Dot as thousand | {{last_purchase_amount|number-format=dot}} | 1.234.567.890.00 |
Comma as thousand | {{last_purchase_amount|number-format=comma}} | 1,234,567,890.00 |
Apostrophe as thousand | {{last_purchase_amount|number-format=apostrophe}} | 1'234'567'890.00 |
Space as thousand | {{last_purchase_amount|number-format=space}} | 1 234 567 890.00 |
Empty thousand | {{last_purchase_amount|number-format=,comma}} | 1234567890,00 |
Empty thousand | {{last_purchase_amount|number-format=,dot}} | 1234567890.00 |
Empty thousand | {{last_purchase_amount|number-format=,apostrophe}} | 1234567890'00 |
Empty thousand | {{last_purchase_amount|number-format=,space}} | 1234567890 00 |
If you want to customize your values, you can specify and write your preferred format in the fallback field. Moreover, you can either apply a customization or assign a fixed value to the fallback field; both options are available and can be used simultaneously.
You have the flexibility to apply customization and assign a fixed value to the fallback field; these options are not mutually exclusive and can be used together. Below, you can see the value example:
Fixed Value| number-format=dot,comma