You spend months building Klaviyo segments. VIPs. Lapsed buyers. Subscribers and non-subscribers. The cohort that clicked your Fall collection email three times but never bought.

Each segment gets its own email cadence. Its own SMS flow. Offer timing mapped to their habits.

Then every one of those people clicks through to the same homepage. Same hero, same headline, same promo strip above the fold.

Klaviyo's own analysis of 2.5 billion emails found that highly segmented campaigns return more than 3x the revenue per recipient of unsegmented ones. You've already done the work of dividing your audience. The question is whether the rest of your store reflects it.

This piece covers how to use Klaviyo segments as targeting rules inside Relevant Bits, and the two-way data loop that makes both tools sharper over time.

Klaviyo + Shopify personalization: turning segments into on-site experiences

Relevant Bits and Klaviyo connect through three mechanics. Each one covers a gap the other one has.

Klaviyo segments become targeting rules on your storefront

Every customer segment you build in Klaviyo shows up inside Relevant Bits as a Customer segments rule. Drop it into a recipe and it controls which content variation a visitor sees. Variations are built using your native Shopify theme sections, inside the Shopify theme editor. No custom code, no injected overlays, no parallel page builder.

The integration recognizes visitors even when they aren't logged in

This is the piece most guides skip. Relevant Bits uses the Klaviyo beacon, which sets a cookie when a known Klaviyo profile clicks through from an email or SMS. On every future visit, Relevant Bits reads that cookie and applies the right segment rule, even if the visitor never signs in.

Most storefront traffic is anonymous. The Klaviyo beacon is how segment-based personalization works at real traffic volumes.

"The Klaviyo beacon is how segment-based personalization works at real traffic volumes."

On-site behavior flows back into Klaviyo profiles

When a recipe runs for a visitor Klaviyo already knows, Relevant Bits pushes three events back onto that profile:

• Context session: Customer ID, URL, Recipe ID, Recipe name
• Context view: Section ID, Variation ID, Variation Name, Variation type, URL, Recipe ID, Recipe name
• Context click: Section ID, Variation ID, Variation Name, Variation type, URL, Recipe ID, Recipe name

What a customer saw on your storefront, and what they clicked, becomes part of their Klaviyo profile. That data is available for further segmentation and for flow triggers.

One prerequisite to flag: the Klaviyo integration needs to be enabled inside Relevant Bits settings, and your Klaviyo account needs at least one customer segment created. An empty dropdown usually means no segments exist yet in Klaviyo.

Setting it up

Roughly fifteen minutes from install to first live recipe.

1. Open Relevant Bits settings and turn on the Klaviyo integration. Paste in your Klaviyo API key.
2. Confirm your segments appear in the dropdown.
3. Open an existing recipe or create a new one.
4. Add a rule. Choose the Customer segments rule type.
5. Pick one or more Klaviyo segments from the list.
6. Build your content variation in the Shopify theme editor and save.

One note on ordering: Relevant Bits evaluates recipes from top to bottom, so more specific recipes need to sit above broader ones. A "VIPs arriving from the holiday campaign" recipe belongs above a general "all email traffic" recipe. Otherwise the broader recipe fires first and the specific one never runs.

The full walkthrough, including screenshots of the Klaviyo key paste, lives in the Relevant Bits Klaviyo docs.

Five recipes you can ship this week

Each one uses a Klaviyo segment as the targeting rule. You can build all five in an afternoon.

1. VIP customers see a VIP experience

Segment: Klaviyo VIP, however you define it. Most brands use top 10% by lifetime value or a trailing-twelve-month spend threshold.

What changes: the hero swaps to a recognition message. A VIP-only collection or early-access banner appears. The first-purchase discount modules hide.

Why it works: you stop offering new-customer promos to your best customers. You protect margin. And you treat the relationship with the weight it's earned.

2. Lapsed buyers land on a comeback hero

Segment: Klaviyo lapsed purchasers. Ninety days without an order is a common threshold.

What changes: the homepage hero highlights arrivals since their last order. A small "welcome back" banner appears. If the segment has an active win-back code, surface it.

Why it works: the email did the hard part. The homepage picks up where the email left off instead of dropping the thread.

3. Non-subscribers see the subscribe module, subscribers see something better

Segment: Klaviyo non-subscribed.

What changes: non-subs see an embedded subscribe form in a prominent section. Subscribers see a different section in that same slot, for example new drops, a referral module, or a members-only teaser.

Why it works: you stop asking your current subscribers to subscribe again. That real estate does more useful work.

"You stop asking your current subscribers to subscribe again. That real estate does more useful work."

4. Flow recipients land on what the email promised

Segment: recipients of a specific Klaviyo flow, such as abandoned browse, welcome series, or back-in-stock.

What changes: the homepage hero or first featured collection matches the flow content. If the welcome flow tells your founding story, the hero leads with it. If back-in-stock just told a customer their size is available, the hero shows it.

Why it works: every paid-ads playbook calls this "ad-to-landing-page match." The logic is identical for the owned channel most brands forget about. See our guide on matching landing pages to ad campaigns for the mechanics.

5. Product-interest segments see a rearranged homepage

Segment: customers who've viewed or purchased in a specific category.

What changes: homepage sections reorder so the relevant category leads. Related collections move up. Unrelated categories drop down or hide.

Why it works: the first screen becomes the one most likely to convert this specific visitor.

Stack Klaviyo segments with other rules for sharper targeting

Segment rules combine with every other Relevant Bits rule type. That combination is where storefront personalization pulls ahead of email personalization. Email has the identity. On-site, you get the identity and the real-time context.

A few pairings worth testing:

• Klaviyo segment + UTM parameters: a VIP arriving via a specific email campaign sees a variation matched to that email's offer and creative.
• Klaviyo segment + geographic location: a VIP experience with US shipping language reads differently from a VIP experience with EU shipping language.
• Klaviyo segment + date range: a seasonal recipe for repeat buyers that turns on and off on scheduled dates without anyone touching the site.
• Klaviyo segment + cart value: high-LTV customers see a free-shipping-threshold nudge, while lower-LTV customers see a first-order discount.
• Klaviyo segment + weather: relevant for outerwear, hydration, sunscreen, and anything else the forecast genuinely affects.

Klaviyo carries who the visitor is. Rules add what's happening right now.

"Klaviyo carries who the visitor is. Rules add what's happening right now."

The feedback loop worth building for

This is the section that changes how you think about your customer data.

When Relevant Bits runs a recipe for a known Klaviyo profile, it pushes the three events listed earlier (Context session, Context view, Context click) back onto that profile. Each event carries the recipe name, the variation name, and the URL. Inside Klaviyo, those events are available to build new segments and trigger new flows.

A few things that become possible:

1. Build a segment of customers who saw the "VIP early access" variation in the last fourteen days but didn't purchase. Route them into a follow-up flow that references what they saw.
2. Build a segment of customers who clicked on a specific variation. Those are your most engaged segment members for that message. Email them first on the next related launch.
3. Cohort by recipe name, so you can measure exposure and response by personalization type, not only by email open.

Klaviyo and your storefront stop being two separate surfaces with two separate data stores. What a customer sees on-site joins what's already in their profile. What's in their profile shapes what they see on-site. Each loop makes both sides a bit smarter.

Measure what's working

Assumptions about your best customers are usually wrong in small, measurable ways. Test them.

• Every Relevant Bits recipe supports A/B testing out of the box. Run two variations against the same Klaviyo segment to see what actually converts for that group.
• Built-in analytics report engagement, conversion rate, average order value, and units per transaction by recipe and by variation.
• GA4 events fire automatically if that's where you do cross-channel analysis.

One habit worth building: every segment-based recipe gets at least one A/B test before a team calls it done.

Getting started with Klaviyo segment personalization

What you need:

• A Shopify store
• A Klaviyo account with at least one customer segment defined
• Relevant Bits installed. 14-day free trial. Klaviyo integration is included on the Starter plan at $99/month.

From install to first live Klaviyo-powered recipe: paste your Klaviyo API key, open a recipe, add a Customer segments rule, build the variation in the theme editor, publish.

Your segmentation work is already done. Now let the rest of the store catch up.

Start your free trial →