Adding Fallbacks to Dynamic Variables in Campaign Builder
Anyone know how to add a fallback to a dynamic variable in the new campaign builder?
Anyone know how to add a fallback to a dynamic variable in the new campaign builder?
To add a fallback to a dynamic variable in the campaign builder, use conditional snippets:
1. Type / in your message body to open the conditional snippet panel
2. Set conditions in the Where fields (e.g., check if First Name exists)
3. Define the "If" output with your dynamic variable (e.g., Hey {{First Name}})
4. Set the "Else" output as your fallback content (e.g., Hey there)
This creates if/else logic that displays your fallback when the dynamic variable is empty or missing.
Make sure you're typing the forward slash / directly in the message body where you want to add the conditional snippet. The conditional snippet panel should appear when you type / in your message composition area.
If you're still not seeing it, try clicking in the message body first to ensure your cursor is active in the text field, then type /.
Hi Jared, thanks for reaching out! Right now, in our email campaigns we don't have conditional runs, but we have conditional runs for our other column enrichments outside of the campaign. Let me know if you have further questions or need additional help! 😊
Where can I find the conditional runs editor? Is it considered a formula? Don't see it as an option under "add column" in a standard table
Hey Jared, The conditional snippets aren't available in the email campaign builder itself. I flagged it as a bug but for the time been, here's how to set them up: 1. In your table, click "Add Column" → "Use AI" → "Generate Message" 2. Build your message with conditional logic there using formulas 3. Reference any table values with forward slash (like /Company Name) 4. Once generated, link this message column in your campaign builder This way you're creating the conditional logic at the table level, then pulling the complete message into your campaign with the / Let me know if you have more questions
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
