Skip to content
Gapstow

Platform guide — Email, CRM & Retention

Klaviyo is a customer database that happens to send email.

Most brands buy Klaviyo as an email tool and then discover the expensive part is the data model underneath it: profiles, events, segments and the logic that decides who gets what.

That is also where the value is. Treated as a sending tool, it produces a newsletter. Treated as a customer data layer, it changes what the rest of the stack can do.

Explore Klaviyo

Partner disclosure: Gapstow may receive referral compensation if you sign up or purchase through links on this page. This does not change what you pay or how we evaluate the platform.

What it does

Klaviyo in one paragraph

Klaviyo ingests storefront and order behavior — views, carts, purchases, subscription events — and builds a profile per customer. Campaigns and automated flows then act on those profiles across email, SMS and push, and reporting attributes revenue back to individual messages and segments.

Around that core sit reviews, forms, predictive metrics and a CDP tier. The breadth is real, and it is also why Klaviyo shows up in stack conversations as a consolidation candidate rather than a point solution.

Notable capabilities

  • Behavioral segmentation

    Segments are computed continuously from event history rather than maintained as static lists, which is what makes lifecycle messaging maintainable at scale.

  • Flows

    Welcome, browse and cart abandonment, post-purchase, winback and replenishment automations carry the majority of retention revenue in most accounts — and receive a minority of most teams' attention.

  • Email plus SMS in one profile

    Consent, suppression and frequency can be reasoned about per person rather than per channel, which is the main argument for consolidating channels here.

  • Predictive and benchmark metrics

    Estimated CLV, churn risk and next order date are useful for prioritization. They are estimates, and they behave poorly on thin data.

Where it fits

Every platform decision is a decision about who owns a stage.

Where Klaviyo sits across the eCommerce stack
  1. Storefront
  2. CustomerKlaviyo
  3. CRM & RetentionKlaviyo
  4. Operations
  5. Fulfillment
  6. ReportingKlaviyo

Klaviyo usually becomes the de facto customer profile store, which makes it the thing everything else wants to sync into. Decide deliberately whether that is the role you want it to have.

Commonly touches

  • Shopify
  • SMS and push
  • Reviews
  • Subscriptions
  • Consent management
  • Reporting

Judgment

Two lists, and the second one matters more.

When we’d look at it

  • Retention revenue is material but flows were set up once and never revisited.
  • Email and SMS live in separate systems with separate consent states and no shared frequency logic.
  • Segmentation currently means exporting a CSV.
  • Reviews, loyalty or subscription events exist but never influence messaging.
  • You need attribution that ties messages to orders without a spreadsheet reconciliation every month.

When we’d question it

  • The list is small and largely inactive. A better platform sends the same weak offer to the same unengaged people, faster.
  • The real constraint is content and offer strategy, not tooling. Migrating platforms will not produce something to say.
  • Nobody owns the channel. Klaviyo rewards continuous operation; unowned accounts decay in a quarter.
  • Deliverability problems came from list acquisition practices. Those move with you.
  • You are migrating primarily to escape a contract. That's a real reason, but budget the flow rebuild honestly — it is the bulk of the work.

Before you implement

Questions to answer first

  1. 01

    Which system is the source of truth for customer identity — the store, the ERP, or Klaviyo?

  2. 02

    What events must be sent for the flows we actually plan to run, and are they instrumented today?

  3. 03

    Who owns consent, and how is it captured, stored and revoked across email and SMS?

  4. 04

    What are we retiring when this goes in — a separate SMS tool, a forms app, a reviews app?

  5. 05

    How will success be measured, and against what baseline?

  6. 06

    If the sync fails for a day, what breaks and who notices?

Implementation

What tends to go wrong

  • Historical data rarely migrates cleanly. Decide in advance which history genuinely needs to move and which is being carried out of anxiety.
  • Flow rebuilds, not the platform connection, are the real timeline. Budget for content, not just configuration.
  • Overlapping apps that also write profiles or send messages need a decision at go-live, or you'll double-message people.
  • Attribution windows should be agreed before launch. Otherwise the first monthly report becomes a debate about the numbers instead of the results.

Before adding another retention tool, make sure the real problem is a technology problem. The brands that get the most out of Klaviyo aren't the ones with the most flows — they're the ones who decided what the customer relationship is supposed to look like before they automated it.

Vendor material

The software company publishes its own customer stories. We include one here because it’s a useful data point, clearly attributed and summarized rather than reproduced. It is not Gapstow work and we make no claim about the engagement.

Partner / vendor case study — published by Klaviyo, not Gapstow work

Harney & Sons' consolidation onto Klaviyo

Klaviyo's own customer story describes tea brand Harney & Sons consolidating a fragmented retention stack into Klaviyo, reporting a 114x return in their first full quarter using four integrated Klaviyo products. Gapstow was not involved in this engagement.

  • Reported 114x ROI in Q4 2024
  • 13% year-over-year increase in revenue per email recipient
  • 34% year-over-year increase in flow email click rate
Read the original on Klaviyo's site

Related Gapstow capabilities

← All platform guides

Adding a platform is the easy part.

If Klaviyo is on the table, the useful conversation is about the process and architecture around it — not the software itself.

Talk through the stackSystems & Integrations