- Shopify already syncs contact details, consent, Shopify Tags and order events. Don't rebuild those as custom properties.
- Store what only the customer can tell you: birthday, the problem they're solving, why they chose you, quiz results and preferences.
- Property names are case- and spelling-sensitive in segments and flow filters. Pick one naming style and never drift from it.
- Use properties three ways: segments for campaigns, splits inside flows, and lookups or if statements inside emails.
- Start small. For surveys, ask 1 to 3 multiple-choice questions with an "other" option, and don't build ten segments on day one.
This is for Shopify founders on Klaviyo who keep hearing "use your zero-party data" and want to know what that actually means inside the account: what to save, where it comes from, and what to do with it once it's there.
What are custom properties in Klaviyo?
Per Klaviyo's help center, custom properties "store information about the contacts in your account." Klaviyo's own examples are extra details like a size or coupon code, preferences like email frequency, and questionnaire responses.
Worth knowing up front, all from Klaviyo:
- They live on the profile, in the Details tab under Custom properties.
- There's no cap on how many one profile can hold.
- They aren't consent. Setting something like "Wants newsletter" to true does not subscribe anyone.
- New values replace old ones. The profile doesn't keep history, so if you need every past answer, keep them in your survey tool too.
Klaviyo's Profiles API describes the same split: standard attributes (email, phone, name, location) plus "a properties object for storing custom properties." Only non-object values can be used for segmentation, so keep each property a simple value or list.
What does Shopify already sync to Klaviyo?
Before you add anything, check what you already have. Per Klaviyo's Shopify data reference, the integration syncs:
- Contact fields: email, first and last name, city, state or region, zip code, country and phone number.
- Locale, plus language and country versions of it.
- Marketing consent for email and SMS.
- Shopify Tags, stored as one list property called "Shopify Tags."
- Events like Checkout Started, Placed Order, Ordered Product, Fulfilled Order, Viewed Product and Added to Cart.
So you don't need custom properties for "has ordered" or "order count." Segments build those from order events.
One rule from Klaviyo applies to all of this: don't edit properties that an integration syncs. Klaviyo says the next sync overwrites them. If you want to change a Shopify tag, change it in Shopify.
Missing from that list: birthdays, why someone bought, what they like. That gap is where custom properties earn their keep.
Which custom properties are worth storing for a Shopify brand?
Here's a short list worth starting with.
Birthday. Klaviyo recommends a date field on a form for collecting dates you'll use in segments or date-based flows, with birthday as its own example. Date fields store the value as a date "regardless of the selected input format," and if you pick a format without a year, Klaviyo adds the current year. Where to ask matters: I'd ask for the birthday on a dedicated Klaviyo landing page rather than mid-purchase. Klaviyo's landing pages are hosted pages with a form embedded, so you can send people there from an email and give the birthday its own moment. Then it powers a birthday email flow.
Survey answers. A post-purchase survey tells you what order data can't: why someone bought. Keep it to 1 to 3 multiple-choice questions with an "other" option, and don't build ten segments on day one. The three I'd ask first are what problem the customer is solving with their first purchase, why they chose you, and how they found you. Each answer becomes a property. My post purchase survey email post covers the tool and timing.
Quiz results. If you run a product quiz, the quiz is a property factory. Save the match and the key answers (skin type, goal, hair type) so your emails can recommend the same product the quiz did. I walk through that in product quiz email capture.
Preferences. Content interests, product categories, scent or flavor preferences, email frequency. Klaviyo lists email frequency preference as a custom property example.
Loyalty data. I like Fondue for loyalty, and it puts data into Klaviyo as tags via the Fondue app. Before you build anything on it, send a test through and look at a real profile so you know exactly what lands and what it's called. For which emails Fondue sends versus which you send from Klaviyo, check Fondue's own docs.
What not to store: anything you won't use. If you can't name the segment, split or email a property will change, it's clutter.
How do you add custom properties in Klaviyo?
Klaviyo gives you several ways in. Pick the one that matches where the data comes from.
By hand. On a profile's Details tab, click Add custom property, pick a name and value, then click Add profile property. Fine for testing, not for scale.
Sign-up forms and landing pages. Every input field in a Klaviyo form has to be connected to a profile property. You pick an existing property from the Profile property dropdown or type a new name and click Create. Per Klaviyo:
- Radio buttons save the answer as text.
- Multi checkboxes save the answers as a list, even if only one box is ticked.
- Dropdowns, radios and checkboxes each need a label (what the shopper sees) and a value (what gets stored).
Hidden fields. Klaviyo calls these "additional properties that will be added to a subscriber's profile." Every form has a $source hidden field by default, and you can add your own on a Submit form button with "Add a property," for example to record which landing page someone used.
Link clicks in emails. Klaviyo has a tag that sets a property when someone clicks, then redirects them:
{% update_property_link 'profile_property' 'property_value' 'redirect_link' %}
Klaviyo notes it doesn't work in SMS, a preview won't update the profile (send yourself a real test), and a second click on a different option overwrites the first.
Inside a flow. The Property update action can update, remove, or create and set a property. Klaviyo's examples include collecting categories of interest and tagging a profile with a specific date.
CSV upload. Map each column to a property and choose its data type. Klaviyo warns that consent columns can change subscription status, so leave them out unless you mean to.
Apps and the API. Survey, quiz and loyalty apps write properties for you. Via the API, custom data goes in the properties object.
Which data types does Klaviyo use?
Per Klaviyo, there are five: text, number (like 25 or 25.5), date (formats like YYYY-MM-DD), boolean (true or false) and list (like ["Offer1","Offer2"]). A birthday should be a date.
When you build a segment or flow filter, you pick the data type for the condition. Klaviyo says that decides how values are compared but doesn't change what's stored, so get the type right when you collect it.
How should you name Klaviyo custom properties?
Klaviyo is blunt here: segmentation and flow filtering are case- and spelling-sensitive, so keep names consistent. "Hair Type," "hair type" and "Hair_Type" are three different properties as far as your segments are concerned.
- One style, everywhere. Either words with spaces and capitals ("Hair Type") or underscores ("hair_type"). Write it down.
- Say what it is. "Problem Solving" and "Heard About Us" beat "Q1" and "Survey Answer." You should understand it a year from now.
- Keep values clean. Use the same answer values in every form, quiz and survey that writes to the same property.
- Don't reuse a name by accident. Two forms writing different answers to one property will overwrite each other.
- Think about personalization. Klaviyo's personalization reference says property names without spaces or special characters can use
{{ person.property_name }}. Names with spaces need{{ person|lookup:'property name' }}. Both are case-sensitive.
How do you use custom properties in segments?
Once a property exists on at least one profile, Klaviyo says it shows up in the segment builder under Properties about someone. From there you can build segments like "Problem Solving equals Sleep" or "Hair Type equals Curly." For when to use a segment versus a list, see Klaviyo list vs segment.
One trap: Klaviyo's help center says properties that are null or empty are treated as not set, and profiles without the property don't match negative conditions like "doesn't equal." Klaviyo's example dropped 100 profiles from a "favorite color doesn't equal red" segment because they had no favorite color at all. If you want those people included, add an OR condition with "is not set."
How do you use custom properties in flow splits?
Per Klaviyo's flow branching guide, a split sends profiles down different paths using the same logic as the segment builder, including profile properties. Unlike a filter, nobody gets removed. Two details matter:
- Paths are checked in order, and each profile takes the first one it matches.
- The split checks when the profile reaches it. If a property gets set later, the split won't see it. Put a time delay before the split if the data might arrive late, like a survey answered a day after the order.
A hypothetical example: a post-purchase flow that splits on "Problem Solving" so a customer buying for sleep gets sleep tips and the person buying for energy gets energy tips. Same flow, different content.
How do you personalize emails with custom properties?
Two tools, both from Klaviyo's personalization reference.
Drop the value in. Add a fallback with default so nobody sees a blank:
{{ person|lookup:'Favorite Food'|default:'tasty treats' }}
Show different text by value. Klaviyo's example uses loyalty points:
{% if person|lookup:'Loyalty Points' >= 150 %}
...
{% elif person|lookup:'Loyalty Points' > 0 %}
...
{% else %}
...
{% endif %}
Each person sees only the first branch they match.
Use splits when whole emails should differ. Use if statements when one paragraph or product should change.
FAQ
Where do I find custom properties on a Klaviyo profile?
Open the profile and go to the Details tab. They're listed under Custom properties, where you can also add one by hand.
Why doesn't my custom property show up in the segment builder?
Klaviyo says a property appears under Properties about someone once it exists on at least one profile. Submit a test and check your own profile, and make sure the name matches exactly, including capitals.
Does a custom property subscribe someone to email?
No. Klaviyo says custom properties are separate from email and SMS subscription status.
What's the syntax for a custom property in a Klaviyo email?
Use {{ person|lookup:'Property Name' }} for names with spaces or special characters, or {{ person.PropertyName }} for names without. Add |default:'...' for a fallback.
- Understanding custom profile properties, Klaviyo Help Center
- Understanding form blocks and fields, Klaviyo Help Center
- Understanding data types, Klaviyo Help Center
- Message personalization reference, Klaviyo Help Center
- Understanding flow branching, Klaviyo Help Center
- Understanding how segment conditions evaluate null or empty values, Klaviyo Help Center
- Shopify data reference, Klaviyo Help Center
- How to use Shopify tags to filter customers, Klaviyo Help Center
- How to add an update profile property action to a flow, Klaviyo Help Center
- How to update a profile property when someone clicks a link, Klaviyo Help Center
- Getting started with Landing Pages, Klaviyo Help Center
- Profiles API overview, Klaviyo Developers