Can Liquid be passed in Custom Event Properties?

Currently, Braze does not support importing dynamic Liquid templates from event payloads and then further processing them as Liquid. In Braze, Liquid is processed only when it’s embedded directly within the message or campaign content itself. When you pass the Liquid template as a property (e.g. liquidBody) via the event payload, Braze treats it as a static string and does not evaluate the Liquid logic contained in it.

This means that if you want to leverage dynamic personalization with Liquid in your notifications, the Liquid code must be part of the message configuration (e.g., directly in your Canvas message step) rather than coming in dynamically from an external source. This limitation is a known behavior in Braze since dynamic evaluation of Liquid passed through event payloads is not supported.

As an alternative, you might consider pre-processing the dynamic content on your end (outside of Braze), so that the final content you send as a property is already fully rendered. Then, your message can simply inject that final string without additional Liquid processing. Another approach would be to structure your campaign to use the static Liquid that references other event properties (like body or other custom attributes) rather than a dynamically passed Liquid template.

For further details on Liquid usage in Braze, check out the official documentation on personalization and Liquid templating:
https://www.braze.com/docs/user_guide/message_building_by_channel/customization/liquid/

Hope this helps clarify the current capabilities and limitations!