You’re right @_KG, {{ local_dt|datetimeformat('%Y') }} works in an individual email, but HubSpot “freezes” it when you save it inside a section or template, so it turns into a static value like 2025 instead of staying dynamic.
I’d still use that HubL expression directly in the email body (not saved into a reusable section) wherever possible, so it stays dynamic when the email is actually sent.
If your use case really needs it inside a saved section/template, HubSpot doesn’t currently give a clean built-in way to keep local_dt dynamic there, so a common workaround is to store a date or year in a custom property and reference that via a token (but that’s more of a hack than a perfect solution).
For now, I’d suggest using the HubL directly in the specific email rather than inside the saved section, or testing a custom property approach if you really need reuse.
If that still doesn’t solve it in your setup, let me know and I’ll dig into a more tailored workaround for you.
Content Remix doesn’t fully support applying your own branded templates directly. For landing pages, use an active theme with your Brand Kit and “Generate with AI” to align with your branding. For emails, start with your branded template, then use Content Remix to fill in content, and finish by applying your brand colors and any layout adjustments manually.
Hi @_KG Thanks for bringing this question to the Community! This is a really thoughtful use case, and I can see why you’d want that year to update automatically instead of getting “locked in” when saving a section or template.
I’m going to tag in a few folks who work closely with HubL and email templates—they may have run into this before or found a good workaround. Hi @Karushna1@Shubham_Sharma@Christensen - Would you be able to share any insights on this? Your expertise would be greatly appreciated.
Appreciate you raising this—features like this often start with questions just like yours. Victor
Loop Marketing is a new four-stage approach that combines AI efficiency and human authenticity to drive growth. Learn More
You’re right @_KG, {{ local_dt|datetimeformat('%Y') }} works in an individual email, but HubSpot “freezes” it when you save it inside a section or template, so it turns into a static value like 2025 instead of staying dynamic.
I’d still use that HubL expression directly in the email body (not saved into a reusable section) wherever possible, so it stays dynamic when the email is actually sent.
If your use case really needs it inside a saved section/template, HubSpot doesn’t currently give a clean built-in way to keep local_dt dynamic there, so a common workaround is to store a date or year in a custom property and reference that via a token (but that’s more of a hack than a perfect solution).
For now, I’d suggest using the HubL directly in the specific email rather than inside the saved section, or testing a custom property approach if you really need reuse.
If that still doesn’t solve it in your setup, let me know and I’ll dig into a more tailored workaround for you.