Dynamic Content with CSV

• Use a CSV to personalize at scale – One message, custom experiences for everyone
• Dynamic personalization – Content adapts to user properties (language, region, campaign ID)
• HTML injection (email) – Include HTML markup in CSV cells to dynamically build rich email content
• Team collaboration – Non-technical users edit content in CSV files
• Cross-channel compatibility – Reuse CSV logic across channels
• Multi-language support – Automatic language switching per user

• Multi-language onboarding or marketing
• Region-specific promotions
• Event announcements per location
• Campaign-based personalization

​

Dynamic Content with CSV setup steps

1. Create a CSV file with your content variations.
2. Create a template
3. Map the CSV data to the message using the dynamic_content property in liquid syntax.
4. Select the Dynamic Content or Personalization button.
5. Upload the CSV file and send the message.

​

CSV requirements & setup

• File size: Under 200 KB
• Column headers:
  • Reserve the first column header for the tag key or leave blank to reference sections
  • Alphanumeric characters and underscores only
  • Use underscores (_) instead of spaces
• Encoding: UTF-8

• Multi-language – Localize content by language
• Content personalization – Customize content by Tags

​

Example CSVs

• Multi-language Template Example
• Content Personalization Template Example

• Map the column headers to your supported language codes.
• Add your translations to each row for each language code.
• If you have multiple sections (like in an email), designate the first column as the section name.

This example includes:

• 3 languages: English, Spanish, and French.
• 2 sections: “section_1” and “section_2”.

• Map the first column header to the tag key and underlying rows to the values you want to reference. See Tags for more information on adding tags to users.
• Map the remaining column headers to the sections or components you want to personalize.

In this example:

• The tag key is campaign_id with possible values of A and B.
• There are 3 components: “title”, “message”, and “url”.

Important: Remove spaces and non-alphanumeric characters from CSV headers or use hash notation in Liquid.

​

Map CSV data to message content

<!-- Option 1: access by component first -->
{{dynamic_content.file_name.message_component[user_property]}}

<!-- Option 2: access by user property first -->
{{dynamic_content.file_name[user_property].message_component}}

• dynamic_content – The property name used to reference the CSV data
• file_name – CSV file name (without .csv extension)
• message_component – The specific message component you want to personalize. This is the static text in the CSV column header or first row.
• user_property – The user property you want to reference.

{{ dynamic_content.my_template.header[user.language] | default: "Welcome to our latest update" }}

• Dynamic Content is used when available
• A hard-coded message appears if Dynamic Content fails
• Users never receive blank content

• Multi-language Message Example
• Content Personalization Message Example

translations.csv

,en,es,fr
section_1,Hello,Hola,Bonjour
section_2,Thanks for shopping with us...,Gracias por comprar con nosotros...,Merci pour votre achat avec nous...

• The file_name is translations.csv.
• The message_component is in the rows of the first column section_1 and section_2.
• The user_property is the column header matching language code. We can reference this on the user with the user.language property.

Basic Liquid syntax for the multi-language message

{{dynamic_content.translations.section_1[user.language]}}
{{dynamic_content.translations.section_2[user.language]}}

(Recommended) Liquid syntax with default fallback for the multi-language message

{% assign supported_langs = "en,es,fr,de" | split: "," %}
{% assign lang = user.language | default: "en" %}

{% unless supported_langs contains lang %}
  {% assign lang = "en" %}
{% endunless %}

{{ dynamic_content.translations.section_1[lang] | default: "Hello" }}
{{ dynamic_content.translations.section_2[lang] | default: "Thanks for shopping with us..." }}

content_personalization_template.csv

campaign_id,title,message,url
campaign_123,Flash deal for you,Tap to claim,https://example.com/flash
campaign_456,Weekend picks are here,See what's trending,https://example.com/weekend
default,Our latest offers,See what's new,https://example.com

• The file_name is content_personalization_template.csv.
• The user_property maps to the tag key: campaign_id.
• The message_component is the column header mapped to the section of the message you want to personalize (title, message, or url).

Liquid syntax for the content personalization message

{{ dynamic_content.content_personalization_template[campaign_id].title }}
{{ dynamic_content.content_personalization_template[campaign_id].message }}
{{ dynamic_content.content_personalization_template[campaign_id].url }}

(Recommended) Liquid syntax with default fallback for the content personalization message

{% assign cid = campaign_id | default: "default" %}

{% unless dynamic_content.content_personalization_template[cid] %}
  {% assign cid = "default" %}
{% endunless %}

{{ dynamic_content.content_personalization_template[cid].title | default: "Our latest offers" }}
{{ dynamic_content.content_personalization_template[cid].message | default: "See what's new" }}
{{ dynamic_content.content_personalization_template[cid].url | default: "https://example.com" }}

​

Using HTML in CSV cells (email only)

campaign_id,banner_html
spring_sale,<div style="background:#4CAF50;padding:16px;text-align:center;"><a href="https://example.com/spring" style="color:#fff;font-size:18px;">Shop the Spring Sale</a></div>
default,<div style="background:#333;padding:16px;text-align:center;"><a href="https://example.com" style="color:#fff;font-size:18px;">See What's New</a></div>

{{ dynamic_content.promo_banners[campaign_id].banner_html | default: "<p>Check out our latest offers</p>" }}

​

Reference

​

Updating templates

​

Special characters in keys

{{ dynamic_content.file_name["!the_row!"]["&the_column&"] }}

{{ dynamic_content.file_name.the_row.the_column }}

​

FAQ

​

How can I test Dynamic Content with CSV?

• Use + addressing in emails to test multiple variations: username+test@example.com.
• Set tags following the multi-language and content personalization examples above.
• See Import for more on uploading multiple users and tags.

​

When should I use Dynamic Content with CSV vs. other personalization options?

​

Related pages