Hi @BernieMBL,
Thanks for sharing those screenshots. That was helpful to put everything into context.
Ok - what this tells us is that these custom properties are being logged through other source(s) that aren’t exclusively these two Klaviyo forms.
Some further possibilities include a .csv upload. If at some point yourself or another member who had access to the Klaviyo account actioned a .csv upload with these custom properties to update the profiles that would explain this outcome. Perhaps this was done in the context of migrating ESPs? Alternatively or additionally, these custom property fields could be passed to Klaviyo through another 3rd party sign-up form like Typeform, a Klaviyo manage preferences page or adding these custom properties via a button or a link within email campaigns or flows within your account. If you are using any other 3rd party integration or the Identify API to pass custom properties that is another possibility. It could be an update flow action adding these properties as well.
All and any of these scenarios would update the profile’s custom properties, but not log any submitted form metric since they’re being updated independent of the form fill. So there are quite a few ways in which this can occur. I’d recommend consulting with anybody else working within the Klaviyo account to see if any of these aforementioned items were acted on, since the updates must have come from somewhere :)