Skip to main content
Solved

Re-importing current profiles


Forum|alt.badge.img

I noticed the data from when I first imported the profiles wasn’t well-organized, which led to multiple custom properties being created for the same definition. For example, there are two categories: one labeled "residential" and another "Residential." The difference in capitalization has caused them to be treated as separate categories.

This makes it tricky to create segments because it's difficult to capture everyone. How can I review all my profiles, ensure they use a consistent format, and standardise the property setup? There are over 24,000 profiles. 

Best answer by retention

Another way to do this, is simply to export the ones that are incorrect.  Assuming you prefer “Residential” instead of “residential”, just create a Segment where the custom property = “residential.”  Then, export this Segment with this one field selected  In Google Sheets, change the field values to “Residential” export the CSV and then import that as a CSV back into Klaviyo.

You can keep this Segment around in case more profiles have “residential” and you can keep an eye on this Segment periodically. 

Separately, you should try to audit your systems to see where the origin of the bad data is coming from.  If it’s coming from an integration, a Signup Form, Flow Action, or from other external tools or imports, make sure to fix it at the root problem to mitigate bad properties from happening in the first place.

If there’s no way to easily resolve the root issue, you can consider using a Segment Triggered Flow with a Update Custom Property Action that updates the value from “Residential” to “residential” to automatically update this value whenever it occurs.  Just note, Segment Triggered Flows can occur only once per Profile.  

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

2 replies

Mich expert
Problem Solver IV
Forum|alt.badge.img+11
  • Problem Solver IV
  • 64 replies
  • January 20, 2025

Hello ​@martha098 thanks for sharing your proble

 

`    To fix the inconsistency in your custom properties like "residential" and "Residential," follow these steps:

1. Export Profiles

  • Go to Klaviyo’s Profiles section.
  • Export all profiles as a CSV file, ensuring the export includes custom properties.

2. Clean the Data

  • Open the CSV in Excel or Google Sheets.
  • Find and standardize inconsistent properties, e.g., convert all "Residential" variations to "residential" (use =LOWER() in Excel for uniform lowercase formatting).

3. Re-Import the Corrected Data

  • Save the cleaned CSV file.
  • Import the updated file back into Klaviyo.
  • Ensure the updated properties overwrite existing ones.

4. Prevent Future Issues

  • Create a Klaviyo Flow or use the API to standardize new property inputs automatically. For example, use a flow to convert "Residential" entries to lowercase before saving.

5. Test Segments

  • Once standardized, test your segments to confirm they now include all profiles correctly.

This will ensure your custom properties are consistent and manageable moving forward.


retention
Partner - Platinum
Forum|alt.badge.img+62
  • 2025 Champion
  • 918 replies
  • Answer
  • January 20, 2025

Another way to do this, is simply to export the ones that are incorrect.  Assuming you prefer “Residential” instead of “residential”, just create a Segment where the custom property = “residential.”  Then, export this Segment with this one field selected  In Google Sheets, change the field values to “Residential” export the CSV and then import that as a CSV back into Klaviyo.

You can keep this Segment around in case more profiles have “residential” and you can keep an eye on this Segment periodically. 

Separately, you should try to audit your systems to see where the origin of the bad data is coming from.  If it’s coming from an integration, a Signup Form, Flow Action, or from other external tools or imports, make sure to fix it at the root problem to mitigate bad properties from happening in the first place.

If there’s no way to easily resolve the root issue, you can consider using a Segment Triggered Flow with a Update Custom Property Action that updates the value from “Residential” to “residential” to automatically update this value whenever it occurs.  Just note, Segment Triggered Flows can occur only once per Profile.