nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Dynamic variables with Liquid

I am looking for a solution for storing terms and conditions that have the following features

place hodlers for dynamic dates and other dynamic variables.
each T&C item is related to a content_id within the email it's used in

I have tried both catalogs and json nested profile attributes but both have the same problem where I cannot process the T&C with liquid and also populate a dynamic variable with liquid.

What other options are available in Braze for solving this problem or do I need to consider an external solution and pull in at runtime using connected content ?

Find more posts tagged with

Catalogs

Liquid

Connected Content

Accepted answers

Nirnay

Hey @sm, I have actually tested it with a dynamic item_id and it works well. Can you make sure item_id is in curly braces when calling the catalog? I feel there's some issue with your Liquid, you haven't provided the full code.
Can you try the below:

{% assign first_name = {{${first_name}} %}
{% assign item_id = "20067276" %}
{% catalog_items Terms-and-Conditions {{item_id}} :rerender %}

{{ items[0].terms }}

If the above works, then it should work regardless of a for loop. Let me know how it goes!

All comments

Nirnay

Hi @sm
It would be really helpful if you could share more details about your exact setup and what you've tried - for example, what your catalog structure looks like and the Liquid you're using to call it. That would help narrow down where things are going wrong!

That said, have you tried using :rerender combined with pre-declaring your personalisation variables? This is what I have tested and it works:

Create a catalog with a field called tc_text. For the item with id welcome_email, store the following value in tc_text:

Welcome {{${first_name}}}, by signing up on {{'now' | date: '%d %B %Y'}} you agree to our terms.

Then in your message Liquid:

{% assign first_name = {{${first_name}}} %}{% assign your_custom_attribute = {{custom_attribute.${your_custom_attribute}}} %}{% catalog_items your_catalog welcome_email :rerender %}{{ items[0].tc_text }}

There are two things working together here:

:rerender - tells Braze to do a second Liquid rendering pass on the catalog field value, so any Liquid tags stored inside it actually get evaluated at send time rather than outputting as a raw string.
Pre-declaring your personalization tags - as per Braze docs, any profile fields or custom attributes referenced inside the catalog field must be referenced earlier in the message before the catalog lookup. Assigning them at the top registers them in scope for the rerender pass.

Without both of these together, either the Liquid in the catalog won't evaluate, or the personalisation tags inside it will render blank.

Share your exact use case if you're still stuck, can also look at combining catalogs and content blocks to make it work more dynamically if your setup expects it. Hope this helps!

Thanks Nirnay,

this advice has me closer to a solution but still one outstanding issue.

My catalog is an item an terms, I have used your catalog content above as the test but have the ID as an offer ID rather than the string you used.

Each catalog ID matches to an offer that is used within the email so there is a loop that populates terms for each offer.

{% for offer in offers %} {% assign item_id = offer.offer_id %}

{% assign first_name = {{${first_name}}} %}{% catalog_items Terms-and-Conditions 20067276 :rerender %}{{ items[0].terms }}<BR>

{% assign first_name = {{${first_name}}} %}{% catalog_items Terms-and-Conditions item_id :rerender %}{{ items[0].terms }}

The above code produces

Welcome Steve, by signing up on 20 April 2026 you agree to our terms.

Welcome {{${first_name}}, by signing up on {{'now' | date: '%d %B %Y'}} you agree to our terms.

The dynamic item_id works fine for retrieving the terms but not for the extra parse of the liquid placeholders.

Nirnay

{% assign first_name = {{${first_name}} %}
{% assign item_id = "20067276" %}
{% catalog_items Terms-and-Conditions {{item_id}} :rerender %}

{{ items[0].terms }}

If the above works, then it should work regardless of a for loop. Let me know how it goes!

Hi @Nirnay I have re-created T&C json and run the API to refresh catalog items. Must have been something strange in there as is now working as expected.

Thanks for your help it's solved a huge problem for us and removed a lot of manual T&C creation in our emails.