Personalization with Liquid using purchase events on order level

Question

Hello, I am trying to personalize an email based on purchase event on order level.
Here it says that event properties schema could not be generated for purchase events, but that the nested data is supported by purchase events. Is nested objects even supported for purchase events on order level?
This is the event that I am using:
&nbsp;
&nbsp;
{
    "purchases": [
        {
            "external_id": "2023_new",
            "product_id": "Completed Order",
            "currency": "USD",
            "price": 219.98,
            "properties": {
                "products": [
                    {
                        "name": "Monitor",
                        "category": "Gaming",
                        "product_amount": 19.99
                    },
                    {
                        "name": "Gaming Keyboard",
                        "category": "Gaming ",
                        "product_amount": 199.99
                    }
                ]
            },
            "time": "2024-06-20T13:59:30+01:00"
        }
    ]
}
&nbsp;
&nbsp;
So can you please clarify how can we add liquid tag in order to display the name of the first product - "Monitor"?
Looking forward for your reply!
Many thanks

elena14 · Accepted Answer

Hi&nbsp;inespais&nbsp;, it finally worked with this piece of code in the email template.{{event_properties.${products}[0].name}}
{{canvas_entry_properties.${products}[0].name}}

inespais · Answer

HI&nbsp;elena14&nbsp;- if your JSON event data structure is like the one shown above, you will need to use&nbsp;dot notation to access the nested data. Please try the following and see if it works:To&nbsp;display the name of the first product:{{purchases[0].properties.products[0].name}}To display the name of the second product:{{purchases[0].properties.products[1].name}}&nbsp;and so on...

elena14 · Answer

Hello&nbsp;inespais&nbsp;,&nbsp;I tried your suggestion and unfortunately it is not working.&nbsp;😐Do you know what can be the issue here?

inespais · Answer

Hey&nbsp;elena14&nbsp;- are you able to share an example of your JSON event structure? I believe the one above might be taken from Braze's documentation. Even if your's is really similar, a small difference (structure, naming, etc) might be the key here.

elena14 · Answer

Hello&nbsp;inespais&nbsp;, Please see the JSON payload here:&nbsp;{
    "purchases": [
        {
            "external_id": "2023_new",
            "product_id": "Order Level",
            "currency": "MKD",
            "price": 230.98,
            "properties": {
                "products": [
                    {
                        "name": "Sunscreen",
                        "category": "Health",
                        "product_amount": 20.09
                    },
                    {
                        "name": "Lipstick",
                        "category": "Cosmetics",
                        "product_amount": 25.99
                    }
                ]
            },
            "time": "2024-06-24T11:35:30+01:00"
        }
    ]
}&nbsp;And this is how the campaign is being set up.Can it be related to the fact that&nbsp;Event property schemas cannot be generated for purchase events.&nbsp;As it is stated in the documentation hereMany thanks,Elena

inespais · Answer

Hi elena14&nbsp;apologies if I misread, but my understanding of your original post (I probably just assumed!) was that you wanted to capture the product name for liquid personalization, for which you'd use the schema I suggested:&nbsp;&nbsp;{{purchases[0].properties.products[0].name}}&nbsp;If this is for trigger criteria, then I think you could simply try:&nbsp;properties.name(also try "is" vs "equals" vs "matches regex" if you have different logic options available)To be honest I haven't worked with order level purchase events, and this might require some trial and error.To your point that event property schemas cannot be generated for purchase events - this is definitely confusing in the documentation, but you&nbsp;can definitely trigger campaigns off purchase properties.&nbsp;When Braze mentions that "Event property schemas cannot be generated for purchase events," it means that the specific structure of data for purchase events is fixed and cannot be dynamically generated or altered based on past data, unlike custom events where schemas can adapt based on the data received over the past 24 hours. Essentially, the schema for purchase events is predetermined and not subject to change based on incoming data.Hope that finally works!&nbsp;

Forum Discussion

Personalization with Liquid using purchase events on order level

6 Replies

Related Content

Liquid Countdown App Push

[Remote] Manager - CRM and Personalization @ The Wendy's Company

FAQ: Can I Use Purchase Events in Liquid?

Question about Personalized Variant?

PLEASE BRING IT/BRING IT BACK: Color Coding in JSON and Liquid

Recent Discussions

Ignore hour of timestamp custom attribute in segment filters

Estimated Audience V Reachable Audience V sent

Unsubscribed clicks

Catalog Selections personalization based on array data type

Best Practices for Crafting Effective Push Notifications