Skip to main content

How are agencies catching event property changes in Klaviyo flows?

  • July 28, 2026
  • 1 reply
  • 25 views

Hi everyone,

I’m working through a Klaviyo issue and wanted to see how other teams handle it.

For example, a flow relies on checkout_url or expects cart_total to be a number. Later, an integration starts sending checkout_URL, renames the field, or sends cart_total as a string. The flow is still there, but the template or filter may no longer behave as expected.

I built a small read-only check for this and tested it against a live flow. Now I’m trying to understand whether agencies actually see this across client accounts, or whether it’s mostly an edge case.

How do you catch changes like this today—manual QA, periodic audits, support tickets, or something else?

And if you do run into it, would an alert showing the exact property and where the flow uses it be useful?

I’d really appreciate any real-world examples.

1 reply

KeviSunshine
Expert Problem Solver III
Forum|alt.badge.img+9
  • Expert Problem Solver III
  • August 1, 2026

Hi ​@TigranMargaryan,

To ensure that critical email variables are as expected, I (1) setup conditional splits and use internal alert emails, and (2) make sure to use conditionals and fallbacks within my templates.

For example, I have a simple flow that sends an email to all new sign ups. As part of my “Sign Up” event, I push a “User ID” to the user’s profile. I then have a conditional split for “if user ID on this profile” and I send myself an internal alert for any profile that goes through the “Sign Up” event without a user ID.

For your purposes, you could check something like “checkout_URL” is set and send yourself (or your QA team, or whoever) an internal alert if a checkout email is sent without a URL. Likewise, for checking string/integer values, you could do something like “cart_total” is greater than 0

It’s not the most robust method as you have to manually setup conditionals for the critical variables, but that’s the best way I’ve figured out.

 

I am curious if anyone else has figured out other QA/safety methods for ensuring their emails aren’t going out malformed!

 

All the best,

Kevin.