​@Zintegrations hey, great question!

I’ll list out a few things that I’d try if I was in your place (not saying they are ideal solutions, just that I would take these steps):

Check if the field appears on other profiles, by searching profiles created via the same Zap. If it appears inconsistently in the UI, it’s likely a rendering delay. This is a known inconsistency, particularly when profiles are created or updated in quick succession, or if the property hasn’t been used widely across profiles before.

Try retrieving a few affected profiles using GET /api/profiles/{id} , then confirm if the field is present in the raw response.

Temporarily change the field name to something brand new like “contact_method_v2” and re-test on a few records. This can rule out caching/UI issues tied to the original field key, for example if “Contactmethod” was previously saved as “contactMethod” or “contactmethod”, the UI may not consolidate values properly

Finally, if you consistently confirm presence via API and absence in UI, escalate to Klaviyo with API trace logs + profile IDs as it may be a bug (not likely but still possible).

Let me know if this helped in any way!

Hi ​@Zintegrations,

I agree with what ​@StefanUE mentioned above! It would also be useful to check out the dev logs to see if any other POST or PATCH requests are running after the initial API call that’s overwriting this profile property. They may not come from Zapier, but if another API call is made from somewhere that overwrites or removes this property, that could be the culprit.

Additionally, are there any flows with profile property update actions that could be responsible? Might be worthwhile to take a look at the flows these profiles may have gone through to see if any flow actions could have removed these.

Finally, definitely don’t hesitate to reach out to Klaviyo.com/support, if needed, where a member of our support team can look into the account specifically to determine the reason for the problem.

Hi Stefan and Byrne,

Thank you so much for your advice! Our customer also reached out to Klaviyo support team in tandem and they also recommended we try out Stefan’s recommendations as well.

We did an audit of the Zapier workflows to see if there are other workflows that would contribute to POST or PATCH requests running after the initial API call and we haven’t found any. The screenshots that Klaviyo support team shared from the developer tools also match the number of API calls we’d expect from the initial workflow (and no other ones later).

So we’ll go ahead and try out the recommendations that Stefan outlined and report back.

Thanks again!