Iterable Dynamic Sender: An Alternate Implementation
The ability to manage communications effectively across brands is essential. Leveraging innovative solutions like Iterable’s Dynamic Sender feature can free up staff time to focus on strategic goals.
Out-of-the-Box Capability: Dynamic Sender Setup
Organizations striving for efficiency across multiple brands may find managing email templates challenging. Iterable’s Dynamic Sender feature offers a solution to minimize template creation and still address customers across multiple brands.
This capability provides a way to create a generic email template that can be used to send to multiple subdomains, and this is especially useful when supporting multiple brands within a project.
To use the Dynamic Sender feature, the “Use dynamic sender emails” option must be enabled in your project settings.
- Navigate to Settings > Project Settings
- Switch to Use dynamic sender emails toggle to Yes
- Click Save Project Settings
Dynamic Sender Limitations
While this implementation provides substantial benefits, we have found that there are some limitations.
- The user profile schema must be altered, so any existing data integrations would need to be modified to populate the data in the new attribute(s)
- If a single user profile has multiple brand affiliations, the sender's name associated with each would need to be recorded on the profile, likely in a nested field
Alternative Approach with Snippets
To implement Iterable's Dynamic Sender capability effectively, we have found that utilizing a snippet-based approach allows you to seamlessly define brand-specific email addresses. This method uses Handlebars code within snippets to customize the "From email" field, aligning it with each brand's identity.
Here's how to set it up:
{{#ifEq brand "BRAND A"}}
mktg@brand-a.example.com
{{/ifEq}}
{{#ifEq brand "BRAND B"}}
mktg@brand-b.example.com
{{/ifEq}}
{{#ifEq brand "BRAND C"}}
mktg@brand-c.example.com
{{/ifEq}}
... [Continue for all brands] ...
Then, in the “Details” section, simply reference the snippet in your email configuration and set the “From email” field to reference the snippet you created:
{{{ snippet "setSenderFromEmail" }}}
Expand this setup to include snippets for "From name" and "Reply to email" as required and enjoy a streamlined management process across various subdomains.
By adopting this streamlined snippet-based approach, brand-specific email communications are efficiently managed without the need to alter the user profile schema.