Klaviyo Account Structure Best Practices: Lists, Segments, and Properties

The way you structure your Klaviyo account in the first few weeks determines how much of its capability you can actually use at scale. Brands that set it up thoughtlessly early on spend months later untangling conflicting lists, redundant properties, and data that doesn’t map to the segments they now need to build.

This post covers the structural decisions that matter most — and the mistakes that create the kind of technical debt that costs far more to fix than it would have cost to avoid.

Understanding Klaviyo’s Data Model

Before making any structural decisions, it helps to understand what Klaviyo actually is: a customer data platform built around profiles, not just an email sender. Every subscriber is a profile. Every action they take becomes data attached to that profile. The richness of that data — and the quality of the structure you build around it — determines what you can do with it.

Profiles

A profile represents a single person. Each profile has:

Identity data: email address, name, phone number
Custom profile properties: any data you define (LTV, quiz results, product preferences, subscription status)
A timeline of events: every action that person has taken (placed order, opened email, clicked link, viewed product, submitted form)

The profile is the atomic unit. Everything else in Klaviyo — lists, segments, flows, campaigns — is ultimately a way of working with groups of profiles.

Events

Events are timestamped actions attached to a profile. Some come from your integration automatically (Placed Order, Checkout Started, Viewed Product). Others you send via Klaviyo’s API or through connected tools.

Events are more powerful than properties for segmentation because they carry context: not just “this person bought” but “this person bought [product] on [date] for [amount].” This context is what makes behavioural segmentation possible.

Lists vs Segments

This is where most brands go wrong early.

A list is a static collection. Someone is either on it or they’re not. They get added through an opt-in form, an API call, or a manual import. Lists are for opt-in management and compliance — they represent a deliberate subscription relationship.

A segment is a dynamic query. Klaviyo evaluates every profile against the segment definition in real time and includes profiles that match. Segments are for targeting — they represent a group of people who currently share a characteristic or behaviour.

The mistake brands make is trying to use lists as a targeting tool. Creating a list for “customers who bought in the last 30 days” or “VIP customers” means someone has to manually maintain those lists, and they’re never fully accurate. The same thing built as a segment maintains itself automatically.

Why You Should Have as Few Lists as Possible

The correct approach to Klaviyo lists is minimalist: start with one list (your master marketing list) and resist the urge to create more unless there’s a compliance or opt-in reason to do so.

Brands with many lists encounter predictable problems:

Profile fragmentation. The same person might exist across multiple lists with different consent records, causing confusion about which communications they’ve opted in to.

Segment complexity. When you want to target “people on list A but not list B who have also done X,” you’re fighting your own architecture.

Suppression inconsistency. If someone unsubscribes from one list, they may not be unsubscribed from others. This creates compliance risk and annoyed customers.

Reporting confusion. List-level metrics become meaningless when the same people appear across multiple lists.

The exception cases for multiple lists: a transactional list (non-marketing, for order confirmations), a wholesale or B2B list with different opt-in terms, or compliance-specific lists for regulated markets.

Segment-First Thinking

Once you’ve committed to minimal lists, everything you want to “target” should be built as a segment.

Start by mapping the groups you currently want to target (or will want to target in the next 6 months):

Subscribers who have never purchased
One-time buyers
Repeat buyers (2+ orders)
High-value customers (LTV above £X)
Recently lapsed (no purchase in 90–120 days)
VIP (top 10% by LTV or order count)
Engaged subscribers (opened or clicked in last 90 days)
Unengaged (no open or click in 180+ days)
Category-specific buyers (e.g., bought from skincare category)
Subscribers who have viewed a specific product type

Each of these is a Klaviyo segment definition. Once built, they update themselves in real time.

When building campaigns, you target the relevant segment — not a list. When building flows, you can add split conditions based on segment membership. When doing reporting, you pull data by segment.

Building a Custom Property Taxonomy

Custom profile properties let you store data about a person that isn’t automatically tracked by the Klaviyo-Shopify integration. Common examples include:

Quiz answers or product recommendations from an on-site quiz
Subscription tier or plan name (for subscription businesses)
Referral source (first-touch attribution data)
Loyalty points balance (synced from a loyalty platform)
Custom tags from your CRM or customer service tool

The mistake brands make with custom properties is creating them ad hoc — whoever sets up a new integration or flow adds their own properties without a naming convention or documentation. Over time, you end up with “ltv”, “LTV”, “customer_ltv”, and “lifetime_value” all attempting to store the same thing.

Before adding custom properties, establish a naming convention:

Use lowercase with underscores: subscription_status, quiz_hair_type, loyalty_tier
Document every property in a shared reference: what it stores, where it comes from, when it updates
Review the property list quarterly and clean up unused properties

A well-maintained property taxonomy is what makes personalisation and advanced segmentation reliable.

Event Tracking Planning

Events come from your e-commerce integration automatically for standard purchase and browse actions. But there’s a broader set of events worth tracking deliberately:

High-value customer actions that signal intent:

Clicked on a “Learn More” for a subscription product
Watched a product video to completion
Added to wishlist
Used a size or shade finder tool

Lifecycle milestones:

Completed onboarding steps
Reached loyalty tier threshold
Referred a friend

Feedback events:

Submitted a review
Responded to a survey
Contacted customer support

Each of these events, tracked via Klaviyo’s Track API or through connected tools, becomes available as a flow trigger, a segment condition, and a data point in profiles.

The planning exercise is to map your customer journey and identify the 5–10 events that most meaningfully signal intent, loyalty, or churn risk. These are the events worth instrumenting beyond the standard integration.

Account Structure Mistakes That Create Technical Debt

Using flow filters to work around messy list structure. If your list architecture is creating problems, the answer is to fix the list architecture — not to add increasingly complex filters to every flow to compensate.

Ignoring property naming conventions. Once you have 30 custom properties with inconsistent naming, fixing it requires touching every flow and segment that references them. Do it right from the start.

Not documenting your event schema. Events are powerful but invisible — there’s no in-app documentation of what events you’re tracking or what properties they carry. Maintain a separate reference document.

Storing data in lists that belongs in segments. The tell-tale sign: you have more than 5 lists and you’re managing who belongs in each one manually.

Not reviewing the account structure after 6 months. What made sense when you had 5,000 subscribers and 3 products may not make sense at 50,000 subscribers and 30 products. Schedule a structural review when your scale changes meaningfully.

The Payoff of Getting Structure Right

A well-structured Klaviyo account isn’t just tidy — it’s more powerful. Clean segments enable accurate targeting. Consistent properties enable reliable personalisation. A deliberate event schema enables flow logic that responds to real customer behaviour rather than guessed rules.

The brands that get the most out of Klaviyo are the ones who treated the setup as a strategic exercise, not just a technical checklist.

If you’re setting up Klaviyo for the first time, or you’ve inherited an account that needs restructuring, Excelohunt builds Klaviyo account architecture that scales correctly from day one.

Looking to implement these strategies with expert support?

Klaviyo Setup — learn how we implement this for clients Book a free strategy call with Excelohunt →

Klaviyo Account Structure Best Practices: Lists, Segments, and Properties