We currently POST a Klaviyo event with a property that we later embed into an email template as a URL on a button. However, it appears that this is no longer being persisted with case sensitivity, and the property is populating as all lowercase.
For a simple example, say we POST a Klaviyo event with a body like:
{
data: {
type: 'event',
attributes: {
...{{some attributes}},
properties: {
myUrl: 'http://test.com/CaseSensitiveNeeded'
}
},
},
}
We then create a button in our email template whose url is
{{ event.myUrl }}
When we actually click the button from the email, the URL we are taken to is
'http://test.com/casesensitiveneeded'
It’s worth noting that when I GET the Event, the property appears to maintain case sensitivity.
This hasn’t always been this way, as it was working when first implemented. Has something changed? How can we persist case sensitivity in our flow?