Hi everyone,
I've run into a recurring issue with the Wufoo/Klaviyo integration that I believe is a fundamental flaw: custom properties created in Klaviyo via Wufoo form submissions are not scoped to the specific form. This means that if you have multiple Wufoo forms live, and they each contain a field with the same question—e.g., "attending event?"—Klaviyo treats those properties as the same across all forms.
For example:
-
A subscriber fills out Form A, answering "Yes" to "attending event?"
-
Later, they fill out Form B, answering "No" to the same question
In Klaviyo, only the most recent answer is retained—without any indication of which event/form the response was tied to.
This introduces two major challenges:
-
Segmentation becomes unreliable, since we can’t attribute responses to specific forms/events.
-
Flows triggered by form submissions can't use conditional splits based on those answers, especially if there's a delay—because the data may have already been overwritten by another form submission.
One suggested workaround is to make each field/question unique (e.g., “attending spring gala?” vs. “attending fall mixer?”), but this approach assumes every question across all forms has never been reused, which isn’t always practical—especially at scale or over time.
If I were designing the integration, I'd prepend each custom property with the form's unique hash or ID—something like:abc123xyz_attending event?
To maintain backward compatibility, both the scoped and unscoped versions could be sent to Klaviyo.
Curious, has anyone figured out a good workaround for this? I'd love to hear how others are managing this limitation.
Thanks!
