Two Shopify Stores, One Klaviyo Account: How to Actually Handle List Segmentation

You’ve got two brands, two Shopify stores, and one login. You want your email lists to reflect that. Simple enough, right?

Not quite. If you’ve spent any time trying to connect two Shopify stores to a single Klaviyo account, you’ve probably hit the same wall: it barely works, and Klaviyo itself tells you not to do it.

Here’s an honest breakdown of why the native integration fights you, what your real options are, and how to get to a workable setup — even before your backend consolidation is done.

Why You Can’t Just Plug Two Stores Into One Klaviyo Account

This is the core frustration, and it’s not a bug — it’s by design.

Klaviyo’s architecture operates on a strict one-to-one relationship between stores and accounts, particularly for Shopify. When you connect a Shopify store, Klaviyo’s native integration only allows you to select one list for checkout opt-ins. There’s no dropdown to say “Brand A subscribers go here, Brand B subscribers go there.”

But it goes deeper than just the list selector. When multiple stores feed data into a single Klaviyo account, the system can’t effectively distinguish which purchases, browsing events, or behaviors came from which storefront. Customer profiles become muddled with mixed purchase histories, making accurate segmentation nearly impossible. Automated flows designed for one brand can inadvertently trigger for customers from a completely different storefront — potentially damaging the experience for both.

Warning: Klaviyo’s own community guidance is clear — there is no supported way to separate Shopify store data within a single Klaviyo account. Attempting to force it creates reporting chaos, flow misfires, and segmentation that can’t be trusted.

The Recommended Path: Two Accounts, One Login

The cleanest solution — and the one Klaviyo consistently recommends — is one Klaviyo account per Shopify store. Before you groan, this doesn’t mean juggling two separate logins.

Klaviyo supports multi-account access, meaning you can log in once with a single email and password and switch between multiple accounts without logging out. This is specifically built for brands that have multiple websites or several brands under a single parent company. Your whole team can be added to both accounts with appropriate permissions, and everyone switches between them from the same session.

If you’re on a paid plan, you can also set up a Klaviyo Portfolio — a unified dashboard that lets you compare billing details, performance metrics, and account data across all your accounts in one view without constantly switching contexts.

What You Don’t Lose With Two Accounts

The biggest fear with splitting into two accounts is the duplication of work. That concern is legitimate, but less painful than it used to be:

• Flows and email templates can be cloned between accounts. In the Flows section, click the three dots next to any flow, select Clone, and choose the destination account. You need admin access on both accounts for this to work.
• Campaigns can be saved as templates and copied across accounts the same way.
• Segments with standard conditions can also be cloned, though segments using advanced operators may not transfer cleanly and will need to be rebuilt.

Pro tip: Set up both Klaviyo accounts using the same email address and password from the start. This links them together and enables seamless switching. If you’ve already created them with different credentials, you can add your primary email as a user on the second account to gain switching access.

The one area that doesn’t clone across accounts yet: signup forms. Those will need to be recreated manually in each account.

If You’re Stuck With One Account for Now: The Custom Property Workaround

Maybe your backend consolidation is months away, your loyalty program launch can’t wait, and you need something working now. There’s a pragmatic middle path — it’s not perfect, but it gets you to a functional state.

The approach: use Klaviyo custom profile properties to tag subscribers with their source brand, then build segments around those properties.

Custom properties are fully customizable data fields that live on each subscriber’s profile. You define the field name and values yourself, and once they exist on at least one profile, they become available for segmentation and flow filtering.

Here’s how to implement a basic brand-source property:

Property name: brand_source
Values: brand_a | brand_b

How to Set the Property on Incoming Subscribers

Since checkout opt-ins from Shopify all land in one list, you need another mechanism to tag them. A few options:

1. Klaviyo embed forms per site — Instead of relying on the native Shopify checkout opt-in for segmentation, deploy separate Klaviyo-hosted signup forms on each store’s site. Configure each form to set brand_source = brand_a or brand_source = brand_b as a hidden field on submission. This won’t capture checkout opt-ins but works well for any active signup form placements.

2. CSV import with custom properties — For existing subscribers you’re migrating or importing, you can include a brand_source column in your CSV. Any column after the email column in a Klaviyo import is treated as a custom property.

3. Post-purchase flow with Update Profile Property action — Set up a simple flow triggered by Placed Order, add a conditional split based on which store’s products appear in the order (e.g., by product tag, collection, or vendor), then use an Update Profile Property action to stamp brand_source on the profile. This retroactively tags purchasers based on what they bought.

Building Your Segments From the Property

Once brand_source is populated on profiles, create two segments in Klaviyo:

These segments become your effective “List A” and “List B” — you can trigger separate welcome flows from each, target campaigns to each independently, and build brand-specific automations using conditional splits inside flows.

Warning: This approach has real limitations. The Shopify native checkout opt-in still lands everyone in the same single list — you can’t split that at the Klaviyo integration level. Behavioral event data (Placed Order, Viewed Product, etc.) is also intermingled. Reporting will be harder to interpret, and flows can misfire if your segmentation conditions aren’t airtight. Treat this as a temporary bridge, not a permanent architecture.

Which Path Is Right for You?

The last row is worth highlighting: if your two brands already share a single Shopify store backend (just different storefronts or experiences), the problem is simpler. In that case, you can have two separate lists in one Klaviyo account, each triggering its own welcome series, and the data stays clean because it’s coming from one Shopify source.

The complexity only kicks in when you have two separate .myshopify.com URLs.

The Bottom Line

Klaviyo isn’t going to let you elegantly run two separate Shopify stores through one account — that’s a structural constraint, not a configuration you’re missing. The right long-term answer is two accounts linked under one login, with flows and templates cloned between them to minimize duplication.

If you need something working today while your backend consolidation is in progress, the custom property + segment approach is a reasonable bridge — just go in knowing its limits, document your setup clearly, and plan the migration to a proper dual-account structure before the workaround starts creating bigger problems than it solves.