Has a Fallback value always been required? I don’t remember this being the case.
Is there a workaround/setting to disable this?
Hey @JsonRoth_1,
Thanks so much for posting in the Community!
I’m reading through our knowledge base article on setting unique fallback values for personalization tokens, and it emphasizes that users can set these values; but nowhere does it specify that these are required. The only factor I’ll point out, because I can’t see where you took this screenshot, is that “A Content Hub Professional or Enterprise subscription is required to add personalization tokens to website and landing pages.” Additionally, The Marketing SMS Long Code Add-On or Marketing SMS Short Code Add-On is required to add personalization tokens to SMS messages." (see here)
If you’re attempting to add this token in any of these locations, your subscription may be the issue, which may not have been the case before.
Shane, Senior Community Moderator
It may depend on the field type or a recent update/change in the platform. If there’s no setting to disable it, the usual workaround is to use a neutral default value that won’t affect the actual logic.
Hi Shane, the screenshot is from the email build module, when you click “personalize”. It won’t flag you, but the insert button remains gray until you add a character value, a space won’t suffice.
Appreciate the note.
Yes, went with a neutral default value that fit the email. Was hoping there was something more formal.
Hi @JsonRoth_1,
After adding a fallback value, you can remove it in the email source code:
In the source code, change the personalization syntax to {{ contact.lastname }} and you should be able to publish the email.
And yes, this has been required for some time, it hasn’t changed recently.
Best regards!
This is brilliant. Exactly the solve I was looking for.
Thank you Karsten!