What was the scope of the Klaviyo engagement?

Full lifecycle flows built and iterated against live revenue — welcome, browse abandon, abandoned cart, post-purchase, win-back, sunset, VIP, and review request — plus deliverability infrastructure across dedicated IP warm-up, list hygiene, sender reputation monitoring, and BIMI plus DMARC, SPF, and DKIM configuration. Not a template stack. Real flows iterated against real conversion data.

Why Klaviyo on Magento 2 instead of Magento native email?

Magento 2 native email tooling does not handle behavior-based segmentation off live commerce data the way Klaviyo does. The integration via API plus webhooks gives real-time event flow into Klaviyo, which then drives behavior-based segmentation and flow triggers off live Magento data. The native Magento path would have left meaningful revenue on the table.

What kinds of deliverability work were involved?

Dedicated IP warm-up over the launch window, list hygiene cohorts segmenting by engagement recency, sender reputation monitoring with corrective sending pattern adjustments, BIMI logo registration once domain authentication was clean, and ongoing DMARC/SPF/DKIM tuning. Inbox placement testing was part of the cadence, not a one-time setup. Deliverability is a maintenance discipline, not a checkbox.

Was this work scoped as project or retainer?

Retainer. A lifecycle engagement of this depth does not finish — it iterates. Build the flow, ship it, measure it, adjust it, hygiene the list, re-warm if needed, test new content, sunset stale segments. The retainer shape matches the operational shape of email lifecycle work. Project-shaped engagements end up under-delivering on the maintenance discipline that determines outcomes.

What is in this case study and what is deliberately left out?

This page covers scope, platform integration shape, deliverability discipline, and engagement model. It deliberately omits subscriber counts, segment-level breakdowns, replenishment cycle days, and any revenue figures — those are confidential commercial details of the client. The case study is here to show the engagement shape and discipline, not to leak operational numbers.

Core delivery work·AVOS sits on top →

CASE · KLAVIYO · MAGENTO 2 · 3-YR RETAINER

Three years of lifecycle.
Owned end-to-end.

Q: How did the lifecycle flows evolve over three years?

The flows themselves stayed roughly the same shape — welcome, abandon, post-purchase, win-back, sunset, VIP. What evolved was the segmentation feeding them, the behavioral triggers, the send time logic, and the content variants tested into each step. The three-year arc is not 'more flows.' It is 'the same flows getting smarter on the data.'

Kidsplaza.vn is one of Vietnam's largest mom-and-baby ecommerce brands, operating on Magento 2. The engagement: a Klaviyo-owned lifecycle program — flows built end-to-end against live revenue, integrated with the Magento 2 catalog and event stream via API plus webhooks, with full ownership of deliverability infrastructure. Three years and counting. Retainer, not project — because lifecycle email is a maintenance discipline, not a launch task.

Client

Kidsplaza.vn (Vietnam)

Sector

Mom & baby DTC

Engagement

Klaviyo lifecycle · 3-yr retainer

Status

● Ongoing

01 · The brief

Lifecycle email, owned end-to-end.

Kidsplaza needed a Klaviyo-owned lifecycle program integrated with Magento 2 — flows iterated against live revenue, not a template stack. Significant repeat-purchase patterns tied to baby-age progression and replenishment cycles made the lifecycle layer high-leverage.

02 · What we did

Flows, deliverability, integration.

Eight lifecycle flows built and iterated. Deliverability infrastructure owned across warm-up, list hygiene, reputation monitoring, and authentication. Magento 2 to Klaviyo integration via API plus webhooks, real-time.

Welcome, browse abandon, abandoned cart, post-purchase
Win-back, sunset, VIP, review request
Dedicated IP warm-up + list hygiene + sender reputation monitoring
BIMI registration after DMARC/SPF/DKIM clean
Behavior-based segmentation off live commerce data

03 · What evolved over three years

Same flows, smarter on the data.

The eight flows stayed roughly the same shape. What evolved was the segmentation feeding them, the behavioral triggers, the send-time logic, and the content variants tested into each step. That is what a three-year lifecycle engagement actually looks like — not 'more flows,' but the same flows getting smarter on the data.

04 · Why this case is here

Engagement shape over leaked numbers.

This page deliberately omits subscriber counts, segment-level breakdowns, replenishment cycle days, and revenue figures — those are confidential commercial details of the client. What is portable is the engagement shape: owned end-to-end, retainer-shaped, deliverability as a maintenance discipline. That is what we recommend to brands considering serious lifecycle work.

3-yr

Retainer

Ongoing engagement, iterating against live data.

Flows owned

Welcome through VIP, built end-to-end on live revenue.

Full

Deliverability

IP warm-up, hygiene, reputation, BIMI, DMARC/SPF/DKIM.

SERIOUS ABOUT LIFECYCLE EMAIL?

Run lifecycle the way Kidsplaza —
owned, iterated, retainer.

Same engagement shape, available for ecommerce brands at scale.

Book 30-min call See all work

Three years of lifecycle.Owned end-to-end.