[In Beta] Local Defaults available for personalization tokens in the Rich Text Editor

What is it?
Each personalization token within a rich text module can now have an individual local default.

Why is it important?
With personalization tokens, you can tailor each customer communication so it appears like it was intended just for them. For example, you can use a personalization token to reference a specific customer’s response on a form. If your customer left that form field blank, you can set a default value within Email Content Settings. But what if you’re sending variations of your email in different languages, and want your default values to match the language you’re sending in? Or maybe you’re using a personalization token twice in the same email, but you need the default value to change based on the context of the email. Setting a local default for your personalization tokens lets you do both of these things, making your emails more personalized so you can increase your engagement with your customers.

How does it work?
When inserting a personalization token into a rich text editor, you’ll be given the option to either use the property’s global default value, or set a local default. If you use the personalization token again, you’ll be given the same two options, so you can have different iterations of the same personalization token default set to a different value when your contact does not have a value for that property.

 

Who gets it?
We're progressively rolling this out to users now. It will be available to all Marketing Hub Starter, Basic, Professional, and Enterprise users by the end of May.

What language is it in?
All languages supported by HubSpot

 

 

Topics: All Updates, Marketing - All Updates

Updates by Product

All Products
Featured Updates - All Updates

HubSpot Marketing Platform
Featured Updates - All Updates

HubSpot Sales Platform
Featured Updates - All Updates

Updates by Product
HubSpot Marketing Free

Subscribe to Product Updates