Klaviyo Customer Retention: What Purdy & Figg Learned From Unified Data

Klaviyo customer retention is often discussed as a flows-and-discounts problem. Purdy & Figg’s experience suggests the more fundamental issue is data: when a brand cannot connect customers, campaigns, and post-purchase behavior, it cannot confidently improve the moments that determine whether someone comes back.

In a Klaviyo customer story and accompanying video, Purdy & Figg CRM and Retention Lead Matt Davis described the brand’s earlier challenge as a lack of data sources capable of linking customers to the campaigns they received. The turning point was having multiple channels and their associated data visible in one platform, which made the customer onboarding journey easier to inspect. According to Davis, that visibility coincided with higher Net Promoter Score (NPS) and retention. Klaviyo’s longer case study also reports 102% year-over-year growth in Klaviyo-attributed revenue for Purdy & Figg—but that figure is vendor-published case-study data, not an independently audited causal result. (klaviyo.com)

That distinction matters. The useful lesson is not “install a platform and retention doubles.” It is that unified customer data can shorten the gap between observing an experience problem, changing a lifecycle journey, and measuring whether the change produced a better customer outcome. For founders, ecommerce operators, and CRM teams, that is a more durable growth advantage than simply sending more email.

The Purdy & Figg case: a data visibility problem before a marketing problem

Purdy & Figg is presented by Klaviyo as a consumer brand that has used the platform for more than five years. Davis’s comments focus less on a single clever campaign and more on operational friction: the business previously struggled to join customer identities to actual marketing campaigns. Without that connection, a team may know an email was sent, know an order happened, and know that a customer later churned—but still lack a reliable picture of how those events relate. (klaviyo.com)

That is a familiar failure mode in lifecycle marketing. Data might be divided among an ecommerce platform, an email service provider, an SMS vendor, support software, survey tools, loyalty software, spreadsheets, and paid-media dashboards. Each system can be useful in isolation. The issue arrives when an operator needs to answer a deceptively simple question: what did this customer experience between their first order and their next decision to buy—or not buy?

A disconnected stack produces several predictable problems:

• A customer receives a welcome offer after already purchasing.
• A recent buyer gets a generic acquisition message rather than setup guidance.
• Support complaints or product issues are invisible to the retention team.
• Teams judge onboarding by open rates rather than by repeat purchase behavior.
• Analysts spend time exporting, matching, and reconciling data instead of testing improvements.
• Attribution becomes a debate about dashboards instead of a tool for decision-making.

Davis’s description of data being “built into the platform” should be interpreted as a workflow advantage. It does not mean data quality happens automatically. It means that once a business has connected and structured its data correctly, the people running retention do not have to rebuild the same customer view manually every time they ask a question.

Why unified data is central to Klaviyo customer retention

Retention is a behavior that unfolds over time. A customer may discover a brand through social media, opt in through a form, buy after an email, need help after delivery, complete a survey, and return months later through SMS or a replenishment reminder. A channel-by-channel view treats those as separate activities. A customer view treats them as one relationship.

Klaviyo’s current data documentation describes its core model around profiles, metrics and events, catalogs, and web feeds. It says data is used primarily for targeting—who should receive a message and when—and personalization—what a recipient sees. Events can trigger flows, while segments and filters determine eligibility and message content. (developers.klaviyo.com)

That framework explains why a unified platform can be valuable even before a brand introduces advanced AI features. If a customer’s purchase, product interest, subscription status, email engagement, and support-relevant custom event can be associated with the same profile, the CRM team can create more relevant rules. The platform is not magically creating empathy; it is making previously fragmented context available when a message decision is made.

The practical difference between a list and a customer record

A conventional email list tells you whom you can contact. A useful customer record tells you what the person has done, what they bought, where they are in the lifecycle, what messages they have received, and which message should be suppressed because it no longer makes sense.

For example, imagine a household-cleaning brand with a new customer who has:

1. Purchased a starter kit three days ago.
2. Clicked a how-to video from an order-confirmation email.
3. Opened a shipping update but not a replenishment promotion.
4. Submitted a low product-rating response mentioning unclear instructions.
5. Not yet ordered refills.

The relevant next communication is probably not a broad “20% off everything” blast. It may be an instructional message, a proactive service recovery path, or a timely refill explanation once the customer has had enough time to use the product. Unified data makes that decision feasible at scale because eligibility can be based on actual behavior rather than an export assembled last month.

Onboarding is where retention strategy becomes real

The strongest point in the Purdy & Figg story is the emphasis on onboarding visibility. Marketers often reduce onboarding to a welcome series: a brand introduction, discount, social proof, and product recommendation. That can be useful for leads. But customer onboarding begins after purchase and should answer a different question: how quickly does a new buyer reach the first meaningful outcome with the product?

For a cleaning-product company, that outcome could be successfully using a product, understanding dilution or refill instructions, enjoying the sensory experience, solving a household problem, or feeling confident that the purchase was worthwhile. For a SaaS product, it may be completing setup and reaching an activation event. For a subscription brand, it could be consuming the first delivery and updating preferences before the second shipment.

If the first experience is unclear or disappointing, discounts rarely solve the underlying problem. The customer may redeem an offer once, but their likelihood of becoming a genuine repeat buyer remains weak. Conversely, a clear, well-timed post-purchase journey can reduce uncertainty, preempt support questions, and build trust before the next purchase decision.

A better onboarding map

A retention team should map onboarding as a sequence of customer states, not as a fixed string of emails. A practical starting structure looks like this:

1. Order confidence: Confirm what was purchased, when it will arrive, and how to get help.
2. First-use readiness: Teach the one or two actions that make success most likely.
3. Value realization: Show use cases, routines, or proof that helps the buyer experience the promised outcome.
4. Friction detection: Identify signals such as low ratings, refunds, delivery issues, unengaged new customers, or support events.
5. Feedback invitation: Ask for a review or NPS response only after an appropriate experience window.
6. Repeat-purchase bridge: Introduce replenishment, complementary products, subscriptions, referrals, or loyalty only when relevant.

The timing should be driven by product reality, not by a generic template. A consumable with a 30-day usage cycle requires different cadences from apparel, skincare, supplements, software, or high-consideration home goods. The purpose is to give people what helps them progress, rather than treating every inbox touch as a revenue extraction opportunity.

NPS and retention: useful signals, but not interchangeable metrics

Davis linked improved onboarding visibility with an increase in NPS and retention. That is plausible: a smoother early experience can produce more satisfied customers, and satisfied customers may be more likely to buy again. But teams should avoid collapsing the two measures into one.

NPS measures stated willingness to recommend, based on a survey response. Retention measures actual purchasing behavior over a defined period. They can move in the same direction, but they can also diverge. A brand might earn high NPS for friendly service but have a low repeat rate because its product is infrequently purchased. Another might produce repeat orders through heavy promotions while sentiment deteriorates.

Klaviyo’s own retention-rate guidance emphasizes that retention must be calculated over a defined period and reflect longer-term purchase behavior, rather than simply identifying customers who bought recently. (help.klaviyo.com)

Build a measurement system, not a vanity dashboard

For an onboarding optimization project, use a small set of linked metrics:

The key word is cohort. Compare customers who started onboarding during the same time frame and had similar time to mature. If a brand changes the welcome journey in April, it should not declare success based on a May email click-through rate alone. It should observe whether April’s customer cohort reaches key behavioral milestones at a better rate than comparable prior cohorts.

Where volume allows, use holdouts or carefully designed A/B tests. A holdout group does not receive a particular intervention, enabling the team to estimate incremental impact rather than merely counting revenue that happened after a message. This discipline is especially important for replenishment and win-back programs, where many customers would have bought anyway.

What a unified data architecture should include

The Purdy & Figg account is a reminder that “single customer view” is not a marketing slogan; it is a data design job. Before creating more flows, define the information that must be reliable at decision time.

At a minimum, an ecommerce retention program should connect:

• Identity and consent: email address, phone number where applicable, preferences, locale, and marketing permission.
• Commerce events: viewed product, added to cart, checkout started, order placed, refunded, canceled, subscription started or paused, and product-level purchase history.
• Product context: category, price, inventory status, replenishment window, margin constraints, and compatible cross-sell products.
• Engagement data: messages received, delivery status, opens and clicks where available, site behavior, and channel preferences.
• Experience signals: support contacts, delivery exceptions, product ratings, survey responses, returns, and qualitative feedback tags.
• Business-specific events: quiz result, store visit, membership tier, referral, usage milestone, or appointment status.

Klaviyo’s developer documentation says profile and event data can be used to create custom customer experiences in flows and message templates. Its segmentation documentation also supports targeting based on event activity, profile properties, location, engagement, expected next order date, lifetime value, and churn-related conditions. (developers.klaviyo.com)

Start with a data contract

A data contract is simply a shared agreement about event names, required properties, identity rules, and owners. For example, an Order Placed event should not mean one thing in the store, another in analytics, and a third in the email platform. Nor should a profile property such as customer_type be overwritten by multiple tools without a source of truth.

Write down for every critical event:

• What causes it to fire?
• Which system is authoritative?
• Which customer identifier is included?
• What properties are mandatory?
• Can it arrive late or be duplicated?
• Which campaigns or flows rely on it?
• Who verifies it after a site, checkout, or integration release?

This is less glamorous than campaign production, but it prevents the automation errors that erode customer trust. An elegant journey built on unreliable events is just a faster way to send irrelevant messages.

From visibility to action: five high-value lifecycle plays

Once customer activity is visible in one place, the next challenge is restraint. Teams do not need 50 automations on day one. They need a small number of journeys that address consequential customer moments and have clean measurement.

1. Post-purchase education based on the product bought

Send different first-use guidance depending on the item, bundle, or category purchased. The message should solve a real question: how to use it, how much to use, what to expect, or how to get the best result. Exclude refunded or canceled orders and stop the path when a customer has already reached the intended outcome.

2. Service-recovery routing

When an order is delayed, a low rating is submitted, or a support event signals dissatisfaction, suppress promotional messages temporarily. Route the customer into a helpful sequence with context, a reply path, and an appropriate follow-up. This can protect both brand experience and deliverability because frustrated customers are less likely to mark messages as spam when they feel heard.

3. Replenishment based on observed purchase timing

Do not default to “buy again in 30 days.” Calculate typical reorder intervals by product or customer cohort, then test reminders before and after the expected window. Klaviyo currently supports segmentation and retention flows based on RFM groups and customer behavior changes, including churn-risk scenarios. (help.klaviyo.com)

4. Cross-sell after demonstrated product value

Cross-selling works better after the customer has had an opportunity to benefit from the first purchase. A helpful how-to sequence can naturally introduce a compatible item. A generic cross-sell sent immediately after checkout may look like buyer’s remorse prevention rather than service.

5. Win-back based on value, not panic

A lapsed customer is not one homogeneous audience. Segment by purchase frequency, historical value, product category, complaint history, and elapsed time since the expected next order. Some people need a reminder. Some need new information. Some should receive a meaningful incentive. Some should be allowed to go quiet rather than pushed toward an unsubscribe.

Attribution should inform the journey, not settle every argument

Purdy & Figg’s stated original issue involved linking customers to campaigns, which makes attribution an important part of the case. But attribution is inherently a model, not an unfiltered record of reality. An email platform can report messages sent, clicks, conversions within an attribution window, and multi-touch interactions; it cannot conclusively prove every message caused every order.

Klaviyo describes ecommerce attribution as the process of identifying the marketing touchpoints that influence a purchase, and promotes a linear multi-touch model for examining touchpoints beyond the first sale. (klaviyo.com)

That is useful when applied with humility. Use attribution to find patterns and prioritize experiments, not to award every dollar to the most visible channel. If email-assisted customers retain better, investigate whether the education sequence, customer segment, product mix, or acquisition source explains the effect. Then test the most likely intervention.

A practical attribution review

At least monthly, ask these questions:

1. Which onboarding messages reach customers who later repurchase at the highest rate?
2. Are those customers already more valuable before they receive the messages?
3. Which segments have the highest complaint, unsubscribe, or low-NPS rates?
4. Are promotional sends cannibalizing orders that would have occurred organically?
5. Did a change improve an entire customer cohort, or merely boost a channel’s reported revenue?

This process shifts the discussion from “Which dashboard wins?” to “Which customer behavior are we trying to change?” That is a healthier operating model for a retention team.

The limits of the Purdy & Figg story—and what teams should learn from them

The original video is brief and no substantive viewer comments were supplied, so there is no useful community debate to analyze from that source. The more valuable response is to scrutinize the case-study format itself. Klaviyo publishes the story, and it naturally emphasizes outcomes that support its platform. The reported 102% year-over-year Klaviyo-attributed revenue growth, as well as Davis’s comments on rising NPS and retention, should be treated as Purdy & Figg and Klaviyo’s account of the result rather than universal benchmarks. (klaviyo.com)

There are also important implementation caveats:

• Unified data can unify bad data. Duplicate profiles, missing consent, poor event naming, and delayed syncs do not disappear inside a single platform.
• More channels can create more fatigue. Omnichannel orchestration must include suppression logic and frequency governance.
• NPS is vulnerable to sampling bias. Survey only highly engaged customers and the score may overstate broad customer sentiment.
• Vendor attribution is not incrementality. Reported revenue attribution should be supplemented with cohort analysis and tests.
• Technology does not replace product-market fit. No flow can permanently compensate for a product that customers do not want to reorder.

The appropriate takeaway is not to copy Purdy & Figg’s stack blindly. It is to adopt the underlying discipline: make the customer journey observable, establish trustworthy event data, build a few useful lifecycle interventions, and judge them using behavioral outcomes.

Email infrastructure still matters when marketing data improves

A connected CRM platform helps decide who should receive a message and why. It does not eliminate the basic responsibilities of email sending: consent management, sender authentication, accurate content, list hygiene, and reliable delivery infrastructure.

In the United States, the Federal Trade Commission says commercial email is subject to CAN-SPAM requirements, including accurate header information, non-deceptive subject lines, a valid postal address, a clear opt-out mechanism, and prompt honoring of opt-out requests. The law applies to commercial messages beyond bulk blasts. (ftc.gov)

For teams that operate both marketing and product email, separate the purposes operationally. Marketing campaigns and lifecycle promotions should be consent-aware and frequency-controlled. Transactional messages—such as password resets, receipts, account alerts, and essential order updates—need dependable sending paths, clean event instrumentation, and clear distinctions from promotional content. Before sending at scale, checking address quality with an email verification workflow can reduce avoidable bounces and keep lifecycle metrics from being distorted by bad contact data.

The broader lesson is that data unification and delivery quality reinforce one another. If messages fail to arrive, engagement data becomes misleading. If consent is mishandled, a technically successful campaign damages the relationship it was meant to grow.

A 90-day plan to apply the lesson without rebuilding everything

A large-scale data-platform project can become a multi-quarter distraction. Most brands can learn from the Purdy & Figg approach through a narrower, outcome-driven plan.

Days 1–30: establish the baseline and repair critical signals

Choose one onboarding outcome: second purchase, activation, subscription continuation, first review, or lower early-life support volume. Document its current baseline by monthly acquisition cohort. Audit the minimum events required to understand the path from purchase to that outcome.

Verify that order, cancellation, refund, product, consent, and key support signals are accurately associated with profiles. Review automated messages that can collide with those events. The goal is not exhaustive data completeness; it is confidence in the data that makes a customer journey relevant.

Days 31–60: redesign one journey around customer progress

Interview support and customer-success teams, review survey verbatims, and inspect behavior from new customer cohorts. Identify the two or three moments where customers appear confused, inactive, or unhappy. Build one conditional flow that teaches, reassures, or routes help at those points.

Use control groups where practical. Set suppression rules for recent purchasers, open support cases, refunds, and users who have already completed the desired action. Write messages as a continuation of the purchase experience rather than as isolated campaigns.

Days 61–90: measure, refine, and expand carefully

Compare the revised cohort with the baseline. Look at the selected behavioral outcome plus NPS or satisfaction, refund and support rates, unsubscribes, and revenue. If the journey helped, identify the specific branch or message responsible before cloning it elsewhere.

Only then add the next play: replenishment, cross-sell, churn prevention, or VIP treatment. This sequencing produces a compounding advantage. Each successful journey adds reliable behavioral data and a clearer view of what customers need next.

The real retention advantage is faster learning

Purdy & Figg’s story is useful because it highlights the unglamorous mechanism behind many retention improvements: visibility. When teams can see campaigns, channels, purchases, and onboarding progression in the same customer context, they can stop guessing about the relationship between messaging and experience.

Klaviyo customer retention should therefore be evaluated less as a feature checklist and more as an operating capability. The most valuable platform is the one that helps a team move from data to an informed action quickly, while preserving consent, relevance, and measurement discipline. Unified data is not the finish line. It is the foundation that makes better onboarding, better experimentation, and more durable customer relationships possible.

FAQ

What is Klaviyo customer retention?

Klaviyo customer retention refers to using customer profiles, behavioral events, segmentation, and automated lifecycle messaging to encourage repeat purchases and reduce churn. The most effective programs connect post-purchase education, service signals, replenishment timing, and customer value rather than relying only on discounts.

How did Purdy & Figg use Klaviyo to improve retention?

According to Klaviyo’s case study and Matt Davis’s video comments, Purdy & Figg used the platform to bring multiple channels and customer data into one view. The team could better see the onboarding journey, which Davis associated with increases in NPS and retention. The case study’s additional revenue figure is vendor-reported and should not be generalized as a guaranteed result. (klaviyo.com)

Which metrics should an onboarding flow track?

Track the first-to-second purchase rate, time to second purchase, cohort retention, satisfaction or NPS, refunds, support contacts, unsubscribes, and incremental lift. Use a time window that matches the real product usage and replenishment cycle.

Is a unified customer data platform enough to improve retention?

No. It can make customer context more accessible, but results depend on data quality, product experience, journey design, deliverability, consent practices, and rigorous measurement. A unified platform can speed up learning; it cannot repair unreliable source data or a weak product experience on its own.

Should brands send more email to increase repeat purchases?

Not necessarily. Send more relevant email at moments when it helps customers succeed, choose, or get support. Increasing volume without good segmentation and suppression often increases fatigue and unsubscribes instead of retention.