Skip to main content
Solved

Profile Property Update Through Zapier - Creating New Property Instead of Adding Existing


Jessica eCommerce Badassery
Partner
Forum|alt.badge.img+19

I’m trying to update a profile property in Klaviyo using Zapier. In this use case, their birthdate. 

I already have a birthday property in my account, but when I add it through the zap, it creates a new version of that property even though the name is the same, case sensitive. It is properly adding it as a date property, so it’s not as if it thinks it should be a text field.

I haven’t used zapier to update a profile in awhile, but I don’t remember ever having this issue

Best answer by Jessica eCommerce Badassery

Just an update on this. 

 

I tested this out with other profile properties and could not replicate the issue. It only happened with the Birthday field the first time I tried it.  As expected, as long as the title is the same, case sensitive there is no reason why it shouldn’t update the existing property. 

View original
Did this topic or the replies in the thread help you find an answer to your question?

4 replies

Christiannoerbjerg
Expert Problem Solver II
Forum|alt.badge.img+12

Hi ​@Jessica eCommerce Badassery 

Thank you for posting in the Community!

Just to clarify - Have you tried with the update profile zap in zapier? You should be able to choose the porperty, that you would like to update, without the need to create a new one.

Where do you get the birthday data from? It could be, that i knew of a workaround in Klaviyo :-)

Christian Nørbjerg Enger
Partner & CPO
Web: Segmento.dk
LinkedIn: @christianfromsegmento
Voldbjergvej 22b, 8240 Risskov


Amos Peace
Problem Solver III
Forum|alt.badge.img+5
  • Problem Solver III
  • 56 replies
  • January 18, 2025

Hello ​@Jessica eCommerce Badassery,

It sounds like you're running into an issue with Zapier not updating the existing profile property correctly, even though it's the same property name. This can sometimes happen if the profile update isn't being recognized as an update to an existing field.

Here are a few things I think you can try to resolve the issue:

  1. Profile Identifier: Ensure you're using a unique identifier (e.g., email) to correctly target the profile to update.

  2. Check Date Format: Ensure the birthday is passed as a correctly formatted date.

  3. Use "Update Profile" Action: In Zapier, select "Update Profile" instead of "Add Profile Property" to update the existing birthday field.

  4. Check Property Type: Ensure the property is consistently set as a date field in both Klaviyo and Zapier.

  5. Verify No Duplicates: Make sure there aren’t any conflicting properties.

Test the update manually in Klaviyo to confirm it works, and check Zapier’s task history for data issues.

 

Best Regards,

 


MANSIR2094
Problem Solver IV
Forum|alt.badge.img+13
  • Problem Solver IV
  • 184 replies
  • January 18, 2025

Hello ​@Jessica eCommerce Badassery ,  Could this issue be happening because Zapier is formatting the property differently than Klaviyo expects? Even if the names match, subtle differences in how data is passed (e.g., hidden spaces or formatting) can cause Klaviyo to treat it as a new property.

Double-check Zapier's field mapping to ensure the property name and format match exactly, including spaces and capitalization. If the issue persists, use a test zap to pass only the date to confirm it updates the correct property. For complex setups, reach out to Klaviyo or Zapier support for assistance.


Jessica eCommerce Badassery
Partner
Forum|alt.badge.img+19

Just an update on this. 

 

I tested this out with other profile properties and could not replicate the issue. It only happened with the Birthday field the first time I tried it.  As expected, as long as the title is the same, case sensitive there is no reason why it shouldn’t update the existing property.