Klaviyo, Shopify Flow, and 47 Languages: The DrapX August 2026 Release

Virtual try-on produces the most intentful signal a fashion store can collect: this specific shopper put themselves in this specific garment. Until now, DrapX captured that signal and showed it to you in analytics, but getting it into the tools you actually run your marketing from meant exporting a CSV. This release closes that gap. Try-on data now flows into Klaviyo and into Shopify itself, automatically, on every plan including Free.

There is also a widget that now speaks 47 languages, a new Integrations page in the app, a redesigned Customers page, and a change to the plan lineup. Here is the whole release.

1. Klaviyo, connected in one click

The Klaviyo integration connects through Klaviyo OAuth. There are no API keys to generate, copy, or store, and no private key sitting in a settings field waiting to be rotated. You authorize DrapX from the Integrations page, choose the list captured emails should land in, and you are done.

Once connected, four things sync:

• Captured emails become Klaviyo profiles and join the list you chose, with consent recorded against the profile.
• A "DrapX Virtual Try-On Completed" event, carrying the product the shopper tried and a link to the try-on result image.
• Share events, so you can see and segment on shoppers who sent their look to someone else.
• Orders attributed to a try-on, which is what lets you measure revenue against try-on behaviour inside Klaviyo rather than only inside DrapX.

Every one of those event types has its own on/off switch. If you only want completions to start with, turn the rest off. There is a test-connection button, a pause, and a disconnect, so the integration is reversible at every step.

On compliance: customer deletion requests are forwarded to Klaviyo automatically. If a shopper exercises their right to erasure against your store, you do not end up with an orphaned profile in Klaviyo that you have to remember to clean up by hand.

Why the result image matters more than the event

The detail worth dwelling on is that the completion event carries the try-on image. That changes what your follow-up email can be. A browse-abandonment email shows the shopper a product photo they have already seen and ignored. A try-on-abandonment email can show them a photograph of themselves wearing the thing.

That is a different message, and there is a different level of intent behind it. Someone who uploaded a photo to see themselves in a $180 coat is not casually browsing; they rehearsed owning it. The flows worth building first are covered in more detail in our guide to DrapX and Klaviyo: tried-on-but-did-not-buy within 24 hours, a size-help angle for repeat try-ons of the same item, and a VIP segment for shoppers with three or more try-ons in 30 days.

2. A native Shopify Flow trigger

Not every store runs Klaviyo, and not every automation belongs in an email tool. DrapX now ships a built-in Shopify Flow trigger called "Try-on completed". It carries the customer, the product title, the product ID, and a link to the try-on image.

Because it is a native trigger, it appears in Shopify Flow alongside Shopify's own triggers, with no connector, no webhook plumbing, and no third-party automation service in between. Things you can build with it:

• Tag a customer who completes try-ons on three or more products in a week, then target that tag with a segment.
• Send an internal alert when someone tries on a high-value or limited-run product.
• Start a Shopify-native follow-up sequence for try-ons on a specific collection during a launch.
• Add a note to a customer record so your support team can see what someone was looking at before they wrote in.

3. Try-on leads become Shopify customers

The third integration keeps everything inside Shopify. It is opt-in: when you turn it on, emails captured in the try-on widget become customer records in your own Shopify admin, tagged DrapX Try-On.

The important behaviour here is matching. If the email already belongs to a customer, DrapX tags the existing record rather than creating a second one. Nothing gets duplicated, which is what usually goes wrong when a third-party app starts writing to a customer list. There is an optional switch to mark newly created records as email subscribers, because that is a consent decision that belongs to you rather than to us.

There is also a one-click "DrapX Try-On Shoppers" segment you can create in the Customers area of your Shopify admin, so the audience is available to Shopify Email, discounts, and anything else that reads segments, without further setup.

4. An Integrations hub in the app

All three of the above live on a new Integrations page, which now sits above Billing in the app navigation. It shows a status table for Klaviyo, Shopify Flow, and Shopify Customers, so you can tell at a glance what is connected and what is not, plus three numbers that were previously scattered: leads collected, customers created by DrapX, and leads linked to existing customers.

The Customers page was redesigned in the same release. Shopper identity is now avatar-and-email first rather than an ID column, product images appear as thumbnails instead of titles, the orders columns have been merged, and the stat cards at the top have been cut back to the ones people actually read.

5. The widget now speaks 47 languages

Every shopper-facing string in the try-on widget has been translated into 47 languages. The widget follows your storefront's language automatically and falls back to English when a shopper is browsing in something outside that set.

There is no merchant configuration. You do not pick languages, you do not paste translations, and you do not maintain a locale file. If you sell into multiple markets through Shopify Markets, the try-on flow now matches the rest of the storefront instead of being the one English-only element on an otherwise localized page. That mismatch was a real drop-off point, because a shopper being asked to upload a photo of themselves is exactly the shopper who needs to understand the privacy copy next to the upload button.

6. New pricing

The plan lineup has changed at both ends of the range. Free and Growth are unchanged.

Overage rates are unchanged: $0.14 per extra try-on on Starter, $0.12 on Growth, $0.10 on Pro. Existing subscribers keep their current price until they change plans, so nothing about your bill changes unless you choose to move.

The reasoning is that the old Starter plan was doing two jobs badly. It was expensive as a first paid step for a store that had just outgrown the free plan, and its 150 try-ons were not much headroom for anyone actually growing. At $9.99 for 70 it is a genuine first rung. At the other end, Pro was capped at a level that high-traffic stores were passing every month and paying overage on; the new plan is a lower cost per try-on than the old one at $0.067 against $0.08.

As before, none of this is feature-gating. Every feature in this release, the Klaviyo integration, the Shopify Flow trigger, the Shopify customer sync, and all 47 languages, is available on every plan including Free. The only paid-exclusive feature on DrapX remains the option to apply your own brand watermark to results. Model what a plan is worth on your own traffic with the ROI calculator and the conversion simulator.

What this does not change

DrapX is still Shopify only. There is no WooCommerce app, no headless integration, and no public API, and the integrations in this release are Shopify and Klaviyo specifically rather than a general-purpose webhook layer. More platforms remain on the roadmap. Generation speed is still around 8.5 seconds, image retention is still capped at 10 days, and no plan carries a DrapX watermark. If you are still comparing options, the full comparison of every Shopify virtual try-on app is the honest version, including where competitors beat us.

The outcome figures we quote are unchanged too, and they are still merchant-reported ranges rather than measured results: brands report conversion lifts of 10 to 30% and merchants report up to 20% fewer returns. What this release changes is your ability to act on try-on data rather than only look at it.

Frequently asked questions