Klaviyo Virtual Try-On Flows for Shopify Fashion Brands

Klaviyo is the lifecycle brain for many Shopify fashion brands. It already knows what shoppers viewed, bought, and abandoned. What it often lacks is a hero image that answers the fit question.

Klaviyo virtual try-on flows are automated email sequences that inject AI-generated preview images or deep links into Klaviyo templates based on shopper try-on sessions, browse events, or segment rules. For fashion merchants, they connect Shopify catalog data, custom profile properties, and mobile templates into simulation commerce automation.

Assume Klaviyo is your ESP. The simulation commerce overview frames strategy; personalization guide covers creative rules.

Shopify operator configuring a Klaviyo flow with dynamic try-on image fields beside a fashion PDP screenshot

Klaviyo flows turn try-on sessions into automated preview emails without rebuilding campaigns each week.

Prerequisites On Shopify And Klaviyo

Before building flows:

Shopify-Klaviyo integration syncing catalog, orders, and viewed product events.
Try-on live on hero SKUs via Antla or chosen vendor from best virtual try-on for Shopify fashion.
Custom profile property plan documented (see below).
One mobile-tested base template with dynamic image slot.

Klaviyo Flows product overview and help center are the canonical references for triggers and splits.

Profile Properties To Standardize

Property	Source	Email use
`last_tryon_image_url`	Try-on app webhook	Dynamic hero
`last_tryon_product_id`	PDP event	Product block
`last_tryon_at`	Timestamp	Suppression if stale
`tryon_count_30d`	Aggregated	VIP segment

Name properties consistently across dev and marketing. Stale URLs are the top production bug: set seven-day expiry fallback to static PDP image.

Antla try-on feed helps marketers manually verify URLs before automating. Antla virtual try-on feature page documents embed and session behavior.

Flow 1: Browse Abandonment With Preview

Trigger: Viewed product, no add to cart, 4-24 hours.

Split: Has last_tryon_image_url for same product vs not.

Yes branch: Email with dynamic try-on hero, CTA to PDP with restore param.

No branch: Email with static hero, CTA opens try-on modal on landing.

Compare to abandoned cart try-on guide when event is cart not browse.

Flow 4: Post-Purchase Cross-Sell Handoff

When a shopper buys hero SKU A, wait seven days after delivery confirmation before suggesting complementary SKU B with try-on preview. Suppress if they returned SKU A or unsubscribed from marketing.

Use Klaviyo Placed Order trigger with product type filters. Dynamic block pulls try-on URL for SKU B if shopper generated preview; otherwise static hero with “See it on you” CTA to PDP modal.

This flow pairs with the post-purchase cross-sell guide. Keep frequency caps: one preview cross-sell per fourteen days per profile.

Flow 5: VIP Try-On Engaged Segment

Build a segment where tryon_count_30d >= 3 and no purchase in fourteen days. These shoppers showed high intent but stalled. Send curated three-SKU preview grid linking to PDP try-on, not a blanket discount.

Track revenue per recipient against your Klaviyo benchmark holdout. Engaged try-on non-buyers often respond to fit reassurance copy: “Still thinking about the wide-leg?” beats “20% off everything.”

Troubleshooting Common Klaviyo Preview Failures

Blank dynamic image: Property empty because webhook lagged. Add two-hour delay on post-try-on flow or fallback branch.

Wrong variant color: Map Shopify variant ID in webhook payload, not product ID alone.

Duplicate sends: Smart sending off between preview browse flow and cart flow. Set global cap of one simulation commerce email per forty-eight hours.

Deliverability dip: Image file over 600KB. Compress WebP heroes; test with Litmus image weight guidance.

Document fixes in a shared runbook so seasonal interns do not rebuild flows from scratch.

Flow 2: Post-Try-On Follow-Up

Trigger: Try-on completed event (custom metric from app).

Wait: 2 hours (let shopper decide without nagging).

Email: “Your preview is saved” with same image, size selector reminder, shipping cutoff if applicable.

Bridges to post-purchase cross-sell when purchase follows within 48 hours; suppress flow.

Flow 3: Win-Back 90-Day With Preview

Trigger: No purchase 90 days, historical try-on or high page views.

Creative: Pull archived preview or category fallback.

Detail in email re-engagement with virtual try-on.

Dynamic Template Markup Pattern

In Klaviyo HTML block:

{% if person.last_tryon_image_url %}
  <img src="{{ person.last_tryon_image_url }}" alt="Your preview" width="600" />
{% else %}
  <img src="{{ event.ImageURL }}" alt="Product" width="600" />
{% endif %}

Always include alt text describing garment fit, not “dynamic image.” Test with Litmus across Gmail and Apple Mail.

Metrics Klaviyo Dashboards Should Track

Flow revenue per recipient vs holdout
Click rate by branch (preview vs static)
Unsubscribe spike after preview intro
Placed order within 72 hours of preview email

Klaviyo benchmarks give industry CTR context; your holdout is the truth.

Antla merchants often see 35% higher conversion among try-on users site-wide. Flow attribution should tag orders with UTM utm_campaign=tryon-browse-abandon.

Integration Paths Without Custom Dev

Low code: Weekly CSV of try-on URLs from Antla feed, upload to segment manual properties.

Mid code: Shopify Flow plus Klaviyo API update on try-on webhook.

Full code: App embed posts event to Klaviyo Metrics API with image URL payload.

AI email marketing and AI tools directory help sequence Klaviyo with other stack pieces.

QA Checklist Before Turning Flow Live

Test profile with and without last_tryon_image_url.
Confirm product variant in email matches preview color.
Verify unsubscribe and physical address compliance.
Set smart sending limits so preview flows do not stack same day as promo blast.
Document fallback image per SKU in shared drive.

Frequently Asked Questions

Can Klaviyo send different try-on images per subscriber?

Yes, when custom profile properties store per-user preview URLs and templates use dynamic image tags. Klaviyo cannot generate try-on itself; a Shopify try-on app must write properties via webhook, API, or integrated connector.

What trigger should I build first in Klaviyo?

Browse abandonment with a split on try-on completion is the highest-learning first flow. It captures intent before cart friction and tests preview vs static with clear attribution.

How does Antla connect to Klaviyo?

Antla provides try-on on PDP, try-on feed for marketers, and email list collection as a foundation for lifecycle integration. Custom properties typically use webhooks or middleware to pass image URLs into Klaviyo profiles.

Will dynamic images slow Klaviyo sends?

Send time is dominated by recipient volume and Klaviyo processing, not image hosting. Host preview images on CDN with reliable HTTPS. Large files hurt mobile load after click, not ESP throughput.

Where do privacy rules apply in Klaviyo flows?

Photo-based previews should follow your existing privacy policy and Antla terms settings on the PDP. Store consent timestamps on Klaviyo profiles when your legal team requires it before automating try-on heroes.

About the author: Aaron is the founder of Antla. After years of frustrating returns, never looking like the supermodels on product pages, he set out to make fashion personal by helping shoppers see themselves in the outfits they want to buy. He maps Klaviyo flows like product funnels: one trigger, one preview job, one measurable outcome.

Clone your browse abandonment flow and swap the hero for a try-on dynamic field on one SKU category. Antla feeds the try-on feed and profile-ready preview paths on Shopify PDPs.