Klaviyo CRM strategy is often discussed as a matter of choosing the right platform, but Glow25’s customer story points to a more useful conclusion: the real advantage comes from operationalizing customer data across lifecycle stages, countries, and channels. The collagen brand’s reported gains are notable, yet the deeper lesson for DTC marketers is how segmentation, automation, localization, and measurement work together as one retention system.

The Glow25 story in context

Glow25 is a European pro-aging collagen brand built around a message of feeling comfortable in your own skin at every life stage. In Klaviyo’s video case study, Sara Adam, Team Lead CRM, and Sema Durgun, Head of CRM and Retention, describe why the brand selected Klaviyo early: they wanted a platform designed around direct-to-consumer commerce rather than a generic database or a campaign-only email tool.

Their reported results are attention-grabbing. Over the referenced 12-month period, Glow25 said it achieved 17% year-over-year growth in Klaviyo-attributed revenue. The published Klaviyo case-study page also reports 5% year-over-year growth in overall ecommerce revenue and 102% year-over-year growth in email subscribers.

That last detail is worth stating precisely. The supplied video summary refers to 102% growth in subscriptions, while Klaviyo’s accompanying published case study labels the metric as growth in email subscribers. Those are not necessarily identical measures. A subscriber-list metric may include people who have opted in but have not purchased, while a subscription-business metric would normally refer to recurring product orders. For marketers evaluating the case, the official wording matters.

Glow25’s own explanation is not that one campaign transformed the business. Its team describes moving from a static marketing approach to a more individualized lifecycle model, supported by precise segmentation and both email and SMS communication. That is the more transferable story.

What Glow25’s reported growth does and does not prove

The results give useful evidence that Glow25’s CRM program was growing, but they should not be treated as a universal causal guarantee from software adoption alone. Klaviyo published the case study, so the figures are first-party claims rather than an independent experiment. They are still valuable as a practical example, provided readers distinguish between business outcomes, platform-attributed outcomes, and activity metrics.

Three metrics, three different questions

Glow25’s numbers answer different questions:

5% overall ecommerce revenue growth asks whether the entire online business grew.
17% Klaviyo-attributed revenue growth asks whether revenue credited to interactions tracked in Klaviyo increased.
102% email-subscriber growth asks whether the brand expanded its reachable, permissioned audience.

These measures can move independently. A brand can double its list while total revenue barely changes if new leads are low quality or poorly nurtured. It can also grow attributed CRM revenue while total revenue stays flat if more purchases are being measured or credited through the platform than before. Conversely, total revenue can rise faster than CRM-attributed revenue if acquisition channels are doing most of the incremental work.

The right takeaway is not that 17% attributed revenue growth is insignificant. It is that attribution should start a decision-making conversation, not end it. CRM leaders should examine incrementality, repeat-purchase rate, customer lifetime value, gross margin, unsubscribe trends, deliverability, and contribution to total revenue alongside dashboard attribution.

A better way to read a vendor case study

Use a case study as a pattern library rather than a benchmark promise. Ask four questions:

What changed in the operating model? In Glow25’s case, the answer is segmentation, personalization, and coordinated channel usage.
What customer behavior made the strategy possible? For a replenishable collagen product, there is likely recurring demand, education needs, and a meaningful post-purchase journey.
Which metrics are outcome metrics versus proxy metrics? Revenue and repeat purchase are outcomes; list growth and click rate are supporting signals.
What would have happened without the changes? A holdout group, controlled test, historical cohort analysis, or channel-level incrementality test can help answer this.

This interpretation makes Glow25’s story more useful for founders and retention teams. The point is not to mimic its exact percentages. The point is to build a CRM system that can reveal which customer experiences create profitable, durable retention.

The core of a Klaviyo CRM strategy is segmentation

Glow25’s team repeatedly emphasizes precise segmentation. That deserves more attention than the platform name because segmentation is the mechanism that turns a contact database into a customer strategy.

A static approach typically treats a list as a single audience: everyone gets the same promotion, product launch, or brand update. A lifecycle approach recognizes that customers have materially different needs depending on what they have done, what they have bought, where they live, how they engage, and what they are likely to do next.

Klaviyo’s own current product positioning centers on unified customer profiles and real-time behavioral signals across channels. Its segmentation tools can use purchase history, browsing activity, engagement, preferences, geography, and other customer properties. The technology enables the targeting; the brand still has to define segments that correspond to a meaningful commercial decision.

Segments that are useful, not merely available

A good segment meets three tests: it represents a distinct customer situation, it changes what the brand should say or offer, and it is large enough or valuable enough to justify the work. For Glow25 or another wellness and beauty brand, that could include:

First-time purchasers who have not yet reached the expected replenishment window.
Customers who purchased a starter product but have not adopted a recurring order or bundle.
High-value repeat purchasers who should receive early access, education, or a loyalty benefit rather than frequent discounts.
Lapsed customers whose previous purchase cadence suggests they may be ready for a replenishment reminder.
Browsers who viewed collagen products repeatedly but have not checked out.
Customers in one market who need a different language, shipping promise, regulatory statement, currency, or seasonal campaign.
Email subscribers who repeatedly engage with text messages more quickly than emails, and customers who show the opposite preference.

Notice that these are not just demographic groups. The most useful CRM segments are often behavior- and lifecycle-based because they connect directly to the next decision a customer is making.

Avoid segment inflation

The danger is creating dozens of segments that exist only because the software permits them. Fragmented micro-audiences can make reporting hard, slow campaign production, and produce inconsistent customer experiences. Start with a limited set of high-value segments, then expand only when a segment has an identified message, owner, and success metric.

A simple framework is to organize segmentation around five dimensions: market, consent, lifecycle stage, product affinity, and engagement. This creates enough nuance to make messages relevant without turning CRM into an unmanageable maze of rules.

From static campaigns to lifecycle journeys

Glow25 describes its pivotal realization as the ability to build an individualized customer journey. This is a critical distinction. Personalization is not merely inserting a first name in a subject line. It is changing timing, message sequence, channel, and content according to the customer’s context.

Lifecycle automation creates the baseline experience that runs every day whether or not the marketing team is launching a campaign. For a consumable or routine-led product, this foundation can have more long-term value than a single broadcast because it supports the customer across acquisition, consideration, first use, replenishment, and reactivation.

A practical lifecycle map for a replenishable DTC brand

A strong CRM program could include the following journeys:

Welcome and preference capture: Deliver the promised incentive if one exists, introduce the brand’s point of view, capture product goals or interests, and guide subscribers toward the most relevant first purchase.
Browse and cart recovery: Remind high-intent visitors about the product they considered, answer objections, and avoid sending the same message to a person who has already purchased.
First-order education: Confirm the order, set expectations for delivery and product use, and help customers understand how to incorporate the product into a routine.
Post-purchase reassurance: Address common questions, share usage guidance, request reviews at an appropriate time, and provide customer support paths before frustration turns into churn.
Replenishment and subscription consideration: Estimate a likely consumption window from product size and quantity, then use reminders or bundles to make the next purchase convenient.
VIP and loyalty treatment: Give high-value customers recognition that does not always rely on a price cut, such as access, useful content, or a chance to influence future products.
Winback: Identify customers who have passed their normal reorder window and send a message that reflects their previous product and the likely reason they have gone quiet.

The wording “individualized” should not be taken literally to mean every customer receives a fully unique hand-built sequence. At scale, individualization means designing decision rules that are responsive to the data a customer has provided through consent, purchases, behavior, and preferences.

Personalization needs constraints

The best flows have guardrails. A customer should not receive an abandoned-cart text minutes after completing checkout, a replenishment message for an item they returned, or a discount campaign immediately after paying full price. Suppression logic, frequency caps, purchase exclusions, and event timing are just as important as the creative itself.

This is also why a CRM workflow must be reviewed as a whole. Teams often optimize each flow separately, then accidentally create a noisy experience when several automations trigger at the same time. A journey map and a communications calendar can reveal collision points before customers do.

Why email and SMS should be coordinated, not duplicated

Glow25 says it uses both email and SMS in Klaviyo, framing that combination as an omnichannel strategy. The important word is not “both.” It is “coordinated.” Adding SMS to an email calendar without a clear role can increase costs and customer fatigue faster than it increases revenue.

Email is generally better suited to education, visuals, longer-form brand storytelling, detailed product comparisons, receipts, and content a recipient may revisit. SMS is more immediate and compact, making it better for timely alerts, limited-access moments, order-related updates where allowed, and concise high-intent nudges. The same concept can be delivered across both channels, but it should not always be delivered in the same format or at the same moment.

A practical channel decision model

Before adding an SMS touchpoint, ask:

Is there a time-sensitive reason this customer would value an immediate alert?
Has the customer explicitly opted in to SMS for the relevant market?
Does email already communicate this information adequately?
Will this text add a new action or merely repeat an existing message?
Can the team measure whether the text generated incremental behavior rather than taking credit for a purchase that email would have driven?

For example, an email may explain how to use a collagen product and include routine ideas. A later SMS may be appropriate for an opted-in customer approaching a likely replenishment date, especially if it offers a simple one-tap path to reorder. Sending both channels simultaneously with identical copy is usually less thoughtful.

Consent remains non-negotiable. SMS rules vary by jurisdiction, and brands operating internationally need market-specific processes for capturing, storing, and honoring consent. Klaviyo’s developer documentation explicitly distinguishes consent for email and SMS subscriptions, which reinforces an essential operational truth: a profile is not automatically permitted for every channel. Teams should involve qualified legal counsel for their markets rather than treating platform configuration as legal advice.

Cost discipline matters as messaging expands

A multi-channel approach also changes economics. Email, SMS, and newer mobile channels can have different pricing models, regional rates, and deliverability constraints. Klaviyo has continued to evolve its mobile-message pricing, including a 2026 move from credits toward per-message, dollar-based pricing for mobile messaging. That makes channel-level measurement and send discipline more important, not less.

Before scaling mobile messaging, model expected volume by audience size, frequency, market, and message length. Brands comparing platforms or forecasting a retention stack should connect CRM strategy to transactional email pricing and total messaging economics, not evaluate software only by the first monthly plan displayed.

Localization is a revenue operation, not a translation task

The video describes Glow25 serving customers across three countries. A later Klaviyo case study says the company expanded into four countries, illustrating an important point: international growth changes the complexity of CRM over time. It is not enough to translate copy and duplicate a flow.

Localization touches language, local promotions, product availability, delivery expectations, currency, time zone, opt-in rules, seasonal behavior, cultural references, and support options. If any of those elements are wrong, a technically functional automation can still reduce trust.

How to structure multi-market CRM

A scalable setup normally begins with shared global logic plus controlled local variation. The global layer defines universal customer states: subscriber, browser, purchaser, repeat purchaser, inactive customer, and VIP. The local layer determines the appropriate language, templates, product feed, currency, shipping information, consent handling, and send windows.

This approach reduces duplicated maintenance. Instead of creating entirely separate operations for every country, the team uses common lifecycle principles but lets market properties influence content and eligibility. A country attribute is only the starting point; an effective setup also captures language preference when possible because country and preferred language are not always the same thing.

Local teams need governance, too

As teams grow, localization can introduce inconsistencies. One market may introduce a discount habit that trains customers to wait; another may write claims that do not meet local compliance requirements; a third may continue emailing customers who should have been suppressed after a consent change. Establish global standards for data definitions, naming, UTM conventions, consent, frequency limits, and reporting, while giving regional owners flexibility over creative and calendar decisions.

For developers and operations teams, that also means documenting which events and profile properties are required in every market. Clear email API setup guidance is especially useful when product, checkout, subscription, or preference data must arrive reliably enough to power customer journeys.

The data architecture behind effective personalization

Glow25’s case emphasizes what the CRM team can do in the interface, but personalized journeys depend on upstream data quality. No automation tool can reliably tailor experiences if it receives incomplete order events, inconsistent product names, missing country data, or incorrect subscription status.

A durable CRM data model should include a stable customer identifier, consent by channel, location and language preferences where appropriate, purchase events, product attributes, discount use, return or cancellation events, and on-site behavioral data that the business has a legitimate reason to collect and use. It should also distinguish operational events from marketing events. An order confirmation, for example, may be transactional and necessary; a promotional follow-up is a different category with different consent and policy considerations.

Data quality checks to run every month

CRM teams should regularly audit:

Whether all paid orders reach the customer platform with accurate value, currency, item, and quantity details.
Whether refunds, cancellations, and returns update the profile quickly enough to prevent inappropriate messages.
Whether signup forms write consent data and source information correctly.
Whether country, language, and customer-status fields use consistent values.
Whether test profiles and internal team addresses are excluded from performance reporting.
Whether duplicate profiles are inflating reachable audience counts.
Whether unengaged addresses are being suppressed or sunset according to deliverability policy.

List growth without list quality is not growth a brand can bank on. The 102% email-subscriber increase reported in Glow25’s case is meaningful because permissioned audience growth expands the brand’s ability to communicate directly. But its real economic value depends on acquisition source quality, onboarding, engagement, deliverability, and the percentage of those new subscribers who eventually become profitable customers.

For teams importing leads, collecting event registrations, or cleaning legacy databases, an address verification tool can be part of the hygiene process. It does not replace consent management or engagement-based suppression, but validating address quality before a large send may reduce obvious waste and protect sending reputation.

Measurement: attributed revenue is a signal, not the finish line

Glow25’s 17% growth in Klaviyo-attributed revenue is a useful indicator, particularly because it suggests the company was creating more revenue through trackable CRM interactions. Yet attribution has inherent limitations. The platform observes customer actions through its own tracking and applies its attribution settings; it cannot perfectly observe every competing influence on a purchase.

A customer might see a social ad, search for the brand, read an email, receive an SMS, and finally purchase through a direct visit. Different systems may each claim some credit. That does not make attribution useless. It means teams need to use it consistently and pair it with additional evidence.

Build a retention scorecard with layers

A robust CRM scorecard should include:

Business layer: total revenue, gross margin, repeat purchase rate, subscription retention where applicable, and customer lifetime value.
Customer layer: first-to-second-order conversion, time to second purchase, reorder interval, active-customer rate, and churn or lapse rate.
Channel layer: revenue per recipient, conversion rate, unsubscribe rate, SMS opt-out rate, complaint rate, and cost per incremental order.
Flow layer: contribution by automation, trigger volume, conversion by cohort, and collision or frequency issues.
Quality layer: deliverability, engagement decay, invalid-address rate, consent capture rate, and profile duplication.

Attribution windows should be documented so comparisons remain fair. If the team changes an email click window, adds new tracking, or begins sending substantially more messages, reported attributed revenue may rise partly because measurement changed. That is why controlled tests are valuable.

Test for incrementality when stakes are high

For recurring campaigns and important flows, test a small eligible holdout group where commercially and ethically appropriate. Compare conversion, reorder behavior, and revenue over a defined period. Do not rely only on open rates, especially as privacy features make opens less reliable as a behavioral measure.

The goal is not to prove every message has a massive incremental effect. It is to identify the messages that create value, the messages that merely shift timing, and the messages that train customers to wait for discounts. Over time, this process produces a cleaner and more profitable CRM calendar.

The community lesson: channels should not compete for attention

There were no top comments supplied with the original video, so there is no direct audience reaction to analyze from that source. But the broader practitioner discussion around omnichannel CRM is consistent: uncoordinated channels create customer confusion even when each channel’s dashboard looks healthy in isolation.

A recent discussion in Klaviyo’s community captures this issue well. The argument is that email, SMS, and paid media can begin competing rather than reinforcing one another when each uses different audience logic. A customer may receive a winback email, a promotional text, and a retargeting ad all at once, each using a different offer or message. That is not personalization; it is a disconnected operating model.

Glow25’s emphasis on housing email and SMS together is therefore strategically important. A unified system is valuable not simply because it is convenient, but because it can make suppression rules, eligibility, customer context, and reporting more coherent. The platform cannot automatically solve strategic conflict, but it gives teams fewer excuses to run channels as separate silos.

Where AI changes the playbook—and where it does not

Klaviyo’s current product direction extends beyond email and SMS into channels such as RCS, WhatsApp, mobile push, web activity, and AI-assisted workflows. The company now presents itself as a B2C CRM platform with a unified customer profile and AI capabilities designed to help marketers create, analyze, and optimize customer interactions.

For a team inspired by Glow25’s story, that creates opportunity but also a risk of skipping fundamentals. AI can accelerate copy variants, identify possible audiences, summarize performance, suggest flows, and reduce production time. It cannot decide whether the underlying data is trustworthy, whether the segmentation aligns with a real customer need, or whether a promotion is profitable.

Use AI as an analyst and production assistant

Useful applications include:

Generating localized first drafts that a native-speaking reviewer validates.
Proposing subject-line or message variants for structured tests.
Surfacing segments that have unusual changes in purchase frequency or engagement.
Summarizing flow performance for weekly review meetings.
Mapping product catalog attributes to more relevant content blocks.
Flagging missing data fields, inconsistent event names, or likely automation collisions.

The best use case is not “let AI send everything.” It is shortening the path from insight to a well-governed experiment. Brand voice, claims review, consent, frequency policy, and commercial strategy still require accountable humans.

A 90-day implementation plan for DTC teams

Glow25’s results suggest that CRM maturity is built through daily operating discipline, not a one-time platform migration. For a founder, retention lead, or lifecycle marketer starting from a static send calendar, the following 90-day plan is more realistic than trying to launch every advanced feature at once.

Days 1-30: Establish the foundation

Audit integrations, customer events, consent capture, suppression logic, list health, and reporting definitions. Create a customer journey map from first visit through repeat purchase. Identify the top three revenue-critical lifecycle moments, which are often welcome, cart recovery, and post-purchase or replenishment.

Define a simple segmentation taxonomy: prospect, new customer, active repeat customer, VIP, and lapsed customer. Add market and language fields if the business operates internationally. Agree on a baseline scorecard before changing too much.

Days 31-60: Launch high-intent flows and clean coordination

Build or improve the three priority flows. Add conditional splits based on purchase status, product category, country, and engagement where the data supports it. Set flow filters that stop messages after purchase, cancellation, refund, or a conflicting campaign.

Establish a single cross-channel calendar. Decide which messages are email-first, SMS-eligible, or both. Add frequency caps and a clear escalation rule, such as using SMS only when the message is urgent, consented, and adds value beyond email.

Days 61-90: Optimize and prove value

Review flow performance by cohort rather than only aggregate averages. Run one or two meaningful tests, such as an education-first versus discount-first welcome path, or a replenishment reminder based on predicted timing versus a fixed day count. Use a small holdout where feasible to estimate incrementality.

Then expand thoughtfully into localized flows, VIP treatment, winback, preference capture, and product-specific paths. By the end of 90 days, the target is not perfect personalization. It is a reliable system that can learn without creating brand, compliance, or customer-experience debt.

The bigger takeaway from Glow25’s Klaviyo CRM strategy

Glow25’s case is compelling because it describes CRM as core business infrastructure. Its team says the platform is used every day and supports the brand’s ability to scale. That is the right framing: CRM is not the team that sends newsletters after the acquisition work is done. It is the system that turns customer signals into better timing, better relevance, and more repeatable revenue.

The reported 17% growth in Klaviyo-attributed revenue and 102% increase in email subscribers should be read as evidence of a program gaining momentum, not as a formula that every brand can reproduce by installing the same tool. The durable playbook is more demanding and more valuable: collect clean permissioned data, define useful segments, build lifecycle journeys, coordinate channels, localize the experience, measure beyond attribution, and improve through structured testing.

For DTC brands selling replenishable products, the opportunity is especially clear. A customer relationship should not end at checkout. The post-purchase experience, consumption cycle, education, reorder timing, and loyalty treatment are where a CRM strategy becomes a growth engine—or reveals that it is only a sending tool.

FAQ

What is a Klaviyo CRM strategy?

A Klaviyo CRM strategy is a plan for using customer data, segmentation, automations, email, SMS, and reporting to improve the customer lifecycle. It should define who receives which message, on which channel, at what moment, and how the business will measure incremental value.

What results did Glow25 report from Klaviyo?

Klaviyo’s published Glow25 case study reports 5% year-over-year growth in overall ecommerce revenue, 17% year-over-year growth in Klaviyo-attributed revenue, and 102% year-over-year growth in email subscribers over the stated period. These are first-party case-study figures and should not be interpreted as a universal outcome guarantee.

Is email plus SMS always better than email alone?

No. SMS is most valuable when customers have explicitly opted in and the message is timely, concise, and meaningfully different from email. Duplicating every email as a text can raise cost, increase opt-outs, and make the customer experience feel intrusive.

How should brands measure CRM performance beyond attributed revenue?

Track total revenue, gross margin, repeat purchase rate, time to second order, reorder rate, customer lifetime value, deliverability, unsubscribe and opt-out rates, and controlled-test results. Attributed revenue is useful, but it should be interpreted alongside business-level and incremental outcomes.

What is the first CRM automation a DTC brand should improve?

Start with the lifecycle moment that has the largest combination of volume and intent. For many brands, that is a welcome series, cart recovery, or post-purchase flow. Replenishable-product businesses should also prioritize a well-timed reorder or replenishment journey.

Klaviyo CRM Strategy: What Glow25’s Growth Story Really Teaches DTC Brands