Klaviyo is the single most powerful lever most brands leave unpulled in their creator program. The flow engine knows about the customer's order history, their browsing behavior, their SMS opt-ins, and their lifecycle stage — but it does not know which creator introduced them to the brand. That gap is why a welcome flow for a customer acquired through a skincare creator looks identical to the welcome flow for a customer acquired through a paid Meta campaign, and why both convert the same. The fix is mechanical: write creator identity into a Klaviyo custom property, then fork every flow on it.
This post is the step-by-step for doing that on a Shopify stack where creator identity is already being written to the customer metafield, order tag, and cart attribute at checkout — the architecture we walk through in the Shopify attribution setup guide. If that foundation is not in place yet, fix it first. The Klaviyo work downstream does not help if the data is not being captured upstream.
What Creator-Native Flows Actually Look Like
A creator-native email flow is not a new flow type. It is an existing Klaviyo flow — Welcome, Browse Abandonment, Post-Purchase, Winback — with conditional splits and dynamic content that vary based on which creator the subscriber came from. The shopper who arrived through one creator's storefront sees a different hero image, a different voice-of-customer testimonial, and a different first email subject line than the shopper who arrived through another creator.
The reason this works is not sophistication. It is continuity. The customer built an emotional association with the creator during the discovery moment. The first email they receive from the brand either reinforces that association or silently erases it. Most brands silently erase it. Creator-native flows do not.
Prerequisites: What Has to Be in Place Before You Start
Before you touch Klaviyo, four data surfaces need to be populated on your Shopify checkout. If any are missing, pause and fix them first.
| Data Surface | Purpose | Where It Lives |
|---|---|---|
| Cart attribute | Captures creator at cart creation | note_attributes on order |
| Order tag | Makes order filterable in Shopify | creator:{handle} |
| Customer metafield | Persists creator on the customer | custom.acquired_via_creator |
| Shopify Pixel UTM | Preserves creator across device switches | utm_creator |
CreatorCommerce writes all four automatically as a side effect of the storefront checkout. If you are using a different stack, the help center reference for Shopify order and customer tagging documents the exact field names CC uses — you can either match the schema or adapt the Klaviyo mapping below.
Step 1: Sync the Creator Metafield to Klaviyo as a Profile Property
Klaviyo's Shopify integration syncs standard customer fields automatically, but metafields require explicit mapping. Open your Klaviyo Shopify integration settings, scroll to "Custom Properties from Metafields," and add a new mapping.
Map the Shopify metafield custom.acquired_via_creator to a Klaviyo profile property called $acquired_via_creator. The $ prefix is a Klaviyo convention for properties that Klaviyo should treat as first-class filter targets. After saving, Klaviyo will backfill the property on all existing profiles that have the metafield set, and will keep it in sync going forward.
Sanity check: after the mapping saves, pick one known creator-acquired customer in your Klaviyo profile search and verify the $acquired_via_creator property shows the correct creator handle. If it is empty or shows a different value, the mapping did not hydrate — re-check the metafield namespace.
Step 2: Sync the Cart Attribute to the Checkout Started Event
Profile properties are persistent. Event properties are per-event. You want both, because some Klaviyo flows trigger on events (Checkout Started, Placed Order) before the profile property has hydrated. To cover that window, add an event-level mapping in the same integration settings panel.
Map the Shopify note attribute creator to a Klaviyo event property also named creator on the Checkout Started and Placed Order events. Now when a flow triggers on those events, the flow can read event.creator directly without waiting for the profile property to populate.
Step 3: Build the Creator Segment
Before forking flows, create a canonical segment that captures all creator-acquired customers. In Klaviyo, this is a single definition used everywhere downstream.
Go to Segments, create new, and define: Properties about someone → $acquired_via_creator → is set. Save as "Creator-Acquired Customers." This segment will sit at several hundred to several thousand profiles for most brands, depending on program scale. For reference, Healf's architecture captures this property across 1,700+ storefronts — the segment is not small for a brand operating at that scale.
Clone the segment for each top creator you want to personalize against. The clone uses $acquired_via_creator → equals → {creator_handle}. Name each segment "Creator: {name}." These per-creator segments power the dynamic content in the next step.
Step 4: Fork the Welcome Flow
The Welcome flow is the highest-leverage place to start. The first email a new subscriber receives sets the tone for everything downstream, and the creator-native version materially outperforms the generic version in our customer data.
In your existing Welcome flow, add a Conditional Split immediately after the trigger. The condition reads Profile Property → $acquired_via_creator → is set. The "Yes" branch becomes the creator-native path. The "No" branch keeps your existing welcome sequence for non-creator-acquired subscribers.
Inside the creator-native branch, add a second Conditional Split that forks based on specific creator identity. The simple version uses Profile Property → $acquired_via_creator → equals → {handle} for your top 5 creators, with a default branch for everyone else. The more scalable version uses Klaviyo's Dynamic Content blocks to pull creator-specific hero images, testimonials, and subject lines from a data table keyed on $acquired_via_creator.
What the first email should say: reference the creator by name in the opening line. "You found us through Sarah — here is what she loves about the brand." Include a product callout that matches the creator's curation. End with an invitation to explore the full storefront, not the full catalog. This is a continuity play, not a catalog dump.
Step 5: Fork the Post-Purchase Flow
Post-Purchase is where the 90-day repeat rate is either built or lost. The shopper who bought from a creator's storefront should receive a post-purchase sequence that reinforces the creator relationship — not the brand's generic "thanks for your order" template.
Trigger on the Placed Order event. Add a Conditional Split on event.creator is set. The creator-native branch should thank the customer specifically for discovering the brand through the creator, reference the creator's own review of the product they bought, and invite them back to the same storefront for complementary SKUs. The brand's voice should step back; the creator's voice should carry the sequence.
Pacing matters. Day 1 is order confirmation (brand voice, unchanged). Day 3 is creator-native — creator's take on the product, quote from a review if available, one complementary SKU. Day 14 is a check-in ("how are you liking it?") with the creator's name in the subject line. Day 45 is a second-purchase nudge to the same storefront. Day 75 is the winback trigger if no repeat order has been placed.
Step 6: Fork the Winback Flow
Winback flows are where most brands revert to a one-size-fits-all message because the customer's original acquisition context feels stale. That is exactly backward for creator-acquired cohorts. The original creator relationship is often the only hook strong enough to re-activate a lapsed creator customer.
Set up the winback flow to trigger on the standard "no order in X days" criterion, where X is 90 or 120 depending on your category's natural repurchase rhythm. Immediately split on $acquired_via_creator. The creator-native winback references the original creator by name, shows what the creator is currently recommending, and links back to the creator's storefront — not to a generic "we miss you" landing page.
Step 7: Build a Creator-Launch Flow
This is the one flow that does not exist in most Klaviyo accounts and should. When a new creator joins your program and launches their storefront, the creator's existing customer cohort (if any — through prior campaigns, partnerships, or the gifted program) should receive a dedicated launch sequence.
Trigger on a segment membership event. The segment is defined as $acquired_via_creator equals {new_creator_handle}. The flow fires a three-email sequence: launch announcement from the creator, mid-week nudge with a specific product spotlight, and a weekend-closer with a limited-time offer tied to the new storefront. This sequence takes minutes to configure per creator once the template is built, and consistently outperforms the generic "new storefront" blast that most brands default to.
Step 8: Wire Up Creator Dashboards in Klaviyo Analytics
Klaviyo's Analytics views can break down any flow's performance by any profile property, including $acquired_via_creator. Use this to build a per-creator view of email program health.
Open any flow's analytics view. In the breakdown dropdown, select $acquired_via_creator. You will see open rate, click rate, placed-order rate, and revenue-per-recipient segmented by creator. The creators whose cohorts have disproportionately high email engagement are usually the creators whose audiences have the tightest structural fit with the category — the 90-day-test winners. The flow-level view makes that visible without a dedicated BI tool.
What the Numbers Look Like When This Is Working
Brands that fork the Welcome and Post-Purchase flows on creator identity typically see the creator-native branches outperform the generic branches by 20–40% on revenue-per-recipient within the first 60 days of the split running. The magnitude varies by category and program scale. What does not vary is the direction — creator-native flows outperform generic flows whenever the underlying storefront-native attribution is in place.
The broader impact shows up in the 90-day cohort retention numbers. Cozy Earth's program — 214% relative conversion lift and 67.37% AOV lift across 600+ storefronts — depends on downstream Klaviyo, Meta, and Gorgias inheriting the creator identity that the storefront writes. The email program is one of the three or four places where the inheritance shows up as a visible revenue line.
Common Mistakes to Avoid
The most common mistake we see is teams building elaborate conditional splits without first verifying the underlying data. If the metafield is not hydrated on 70%+ of creator-acquired customers, the splits will route most of the cohort into the default "not a creator customer" branch and the creator-native work will go unseen. Verify the data before building the flows, not after.
The second mistake is over-personalizing the first email. A Welcome email that references five different creator-specific details feels artificial. One or two creator-specific callouts — the opening line, the product spotlight — is enough. The shopper knows they came through a creator; they do not need the email to prove it.
The third mistake is treating the creator branch as a permanent override. If a customer who was acquired through a creator eventually makes a repeat purchase through a brand-owned channel, the creator context should fade into the background. Add a time-based decay to the creator-native branches — 90 or 120 days after last order with the creator attribution present. Beyond that, the customer is the brand's, and the email voice should reflect it.
Where This Fits in the Broader Program
Klaviyo is one of four downstream surfaces that inherit creator identity when storefront-native attribution is in place. The others are Meta CAPI (for custom audiences and lookalikes), Gorgias (for customer-support tickets tagged with creator context), and Yotpo (for review-request flows tied to the creator). We cover the architectural pattern across all four in the storefront analytics layer post.
The Klaviyo work is the easiest of the four to implement and the highest-leverage on revenue in the first 90 days. It is the place to start. The other three surfaces are additive once the email flows are running.
If your program runs through an affiliate platform that has its own Klaviyo integration — for example Simple Affiliate or Superfiliate — the flow architecture above still applies; the only change is that the creator identifier lands in Klaviyo via the affiliate platform's sync rather than the custom metafield mapping in Step 1.
Frequently Asked Questions
Do I need the Shopify metafield to make this work, or can I use a tag?
You can use a customer tag in a pinch, but the metafield is the more durable approach. Metafields are designed to be referenced by external systems, have native Shopify admin UI, and sync cleanly into Klaviyo's custom property system. Customer tags are better suited for ad-hoc segmentation and tend to get cluttered over time. If you are starting fresh, use the metafield.
Will Klaviyo's forever-growing profile properties cause performance issues?
No. Klaviyo handles hundreds of profile properties per profile without performance degradation on flows or segments. The practical limit is operational — humans cannot maintain hundreds of properties coherently — so keep the creator-related property count small: the handle, a normalized category, and a first-seen timestamp is usually enough.
What happens if a customer is acquired through a creator, then later makes a purchase through a brand channel?
The first-touch creator remains on the profile permanently. What should change is which flow voice wins in any given email — that decision is handled by the time-based decay logic mentioned above, not by overwriting the property.
Can I personalize SMS the same way?
Yes. Klaviyo SMS uses the same profile properties and event properties as Email, so the Conditional Split logic works identically. The message length constraints mean the creator reference is usually just the opening clause (e.g., "From Sarah's storefront: ..."), but the personalization still lifts open and click rates.
How granular should the creator-specific branches get?
For the top 3–10 creators by program contribution, full branch personalization is worth building. For everyone else, a single default "creator-acquired" branch with dynamic content pulling the creator name is usually sufficient. Don't build 50 branches you cannot maintain.
What is the fastest way to test whether this is working?
Put the Welcome flow through an A/B test — the existing generic flow versus the new creator-native branch — on creator-acquired customers only. Measure revenue-per-recipient over 30 days. If the creator-native branch is not at least 15% higher, the execution needs rework; if it is 20%+ higher, scale it to the other flows.
Does this break if a creator churns out of the program?
The profile property stays. What you do with it is a policy call. Most brands freeze the creator-native branch for that creator's cohort (flows still trigger but route to the generic branch) for 60–90 days, then fully retire the creator-specific content. The underlying creator reference on the profile stays historical.
Can I power Meta CAPI audiences from the same metafield?
Yes — that is the reason to use the metafield rather than a tag. Meta's Shopify integration can read customer metafields and pass them as custom parameters to CAPI events. Creator cohorts become lookalike seeds inside Meta Ads Manager without any separate integration work.
What if my Klaviyo account is on the free tier?
The free tier supports custom properties, conditional splits, and dynamic content. The limits you will hit first are the profile count (250 profiles) and the email send count (500 per month). For a creator program operating at any real scale, plan on being on a paid tier — Klaviyo's creator-native flows become materially better when the list is large enough to segment meaningfully.
How does this relate to the 90-day test?
The 90-day test measures whether creator-acquired cohorts come back. Creator-native Klaviyo flows are one of the strongest levers for moving that number. The flow reinforces the original creator relationship during the window when the customer is deciding whether to return. Without the flow, the decision defaults to brand-baseline retention; with the flow, the cohort's retention tracks the creator's trust level. We cover the test methodology in the 90-day test post.
Is this compatible with other ESPs — Attentive, Sendlane, Iterable?
Conceptually yes. Every modern ESP supports custom profile properties, event properties, and conditional splits. The specific UI and property naming conventions differ, but the pattern transfers. If you are on Attentive specifically, the equivalent is a subscriber attribute synced from a Shopify metafield, with message template variables reading the creator handle dynamically.
Related Articles
- How to Track Creator Attribution in Shopify Analytics
- Why the Storefront Is Your Analytics Layer
- Why Most Creator Programs Fail the 90-Day Test
- What We Learned From 10,000 Creator Storefronts
- The Complete Guide to Creator Commerce Analytics
- CreatorCommerce x SARAL: Bridging Relationship and Performance in Influencer Marketing
- How to Use GoAffPro Creator Drops to Drive Higher AOV and Conversion
- Introducing CreatorCommerce: Powering the Future of Creator-to-Consumer
- Introducing Custom Forms in CreatorCommerce: Powerful collaboration, now ridiculously simple
- Introducing the new Veeper x CreatorCommerce integraton
- A Mother's Day Affiliate Email Template to Send This Week
- Recruiting Tips: A Creator's Hierarchy of Partnership Needs
- The Age of Performance-based Word-of-Mouth Marketing
- The Future Is Creator-To-Consumer: Why Brands are Rushing To Influencer Marketing
- The relationship that's 🌱 germinating between eComm Managers and Influencer Marketing Managers
- The story of Abercrombie & Fitch, and the brand comeback of the century
- Unlocking the Secrets to Success for Creators and Brands: The Creator Rosetta Stone
- What Uber’s Driver Bonuses Can Teach Influencer Marketers About Incentives
- Why we're building the Creator Primitive for the Internet
%201.png)
%201.png)
