# Capture Emails From Shopify Virtual Try-On Capture email at the try-on step with the product they previewed and whether they bought. First-party data for Klaviyo, Postscript and ads rather than another popup. A shopper has just generated a preview of herself in a green satin dress. She has supplied a photo, chosen a specific color, and waited for the result. Then the store covers the screen with the same 10% newsletter popup it showed her on arrival. That popup knows nothing. The try-on knows exactly which product she is considering. **Virtual try-on email capture is a consent-based exchange at the moment a shopper previews a product. The useful record connects her email to the SKU or variant tried, the event time, and whether she later purchased. That is first-party lifecycle data, not another name added to a general newsletter list.** ![Shopify fashion marketer reviewing an email capture record beside a shopper's virtual try-on preview](/images/blog/cluster-17-tryon-conversion-remarketing/virtual-try-on-email-capture-shopify.webp) *A useful signup preserves the product decision, not merely the email address. Editorial image in Classic Antla disposable-camera style.* ## Ask when the shopper has earned a reason to answer Homepage popups ask for contact details before the shopper has found a reason to trust the store. A try-on capture appears after she has selected a garment and asked the product page a personal question: will this look right on me? That is a better moment because the value exchange is visible. The store can offer to save the look, send the preview, unlock another generation, or make the item easy to revisit. The email field is attached to a job the shopper already wants done. Timing still needs restraint. Do not interrupt the upload, hide the first result, or make email mandatory when the product page promised a free try-on. A sensible pattern is to show one preview, then offer a useful continuation in exchange for an address. The shopper should understand what she receives before she types. The distinction matters for list quality. A general popup records willingness to trade an email for a discount. A try-on capture records interest in a known product. The second record can support a specific follow-up without pretending that every new subscriber wants the same weekly campaign. Across more than 500,000 Antla try-ons, shoppers who completed a preview converted at 3.8%. That is a try-on-user rate, not the store-wide conversion rate. The [Shopify virtual try-on conversion analysis](https://antla.io/blog/shopify-virtual-try-on-conversion) explains the denominator and benchmarks. For lifecycle teams, the useful point is simpler: a completed try-on is a meaningful intent event, including when no order follows. ## Keep the record small enough to use An email address alone loses the context that made the signup valuable. A giant behavioral profile creates the opposite problem. It collects fields nobody uses and expands the privacy burden for no clear return. Start with a compact event record: | Field | What it tells the lifecycle team | Practical use | |---|---|---| | Email | Who requested the saved look or extra try-on | Match the event to an opted-in profile | | Product ID and SKU | Which garment created the intent | Return the shopper to the right product | | Variant ID | Which color or option she considered | Avoid promoting a different item by mistake | | Try-on timestamp | When the decision happened | Set a reasonable relevance window | | Consent state and source | What the shopper agreed to, and where | Suppress contacts who did not opt into marketing | | Purchased flag | Whether the try-on became an order | Stop recovery messages and measure revenue | The purchased flag should begin as false or unknown, then change when Shopify reports a matching order. That update prevents the familiar lifecycle mistake of asking someone to "complete your look" two hours after she paid for it. The generated image deserves even tighter treatment. Do not assume that collecting an email also grants permission to place a shopper's photo in advertising or broad audience tools. In many programs, the safest useful payload is email, product context, consent, and purchase state. The image can stay in the try-on system under a defined retention policy. ## Consent is part of the capture design An address tied to a product interaction is personal data. Treating the form as a small interface detail is how a clean lifecycle idea turns into a compliance problem. Separate the actions the shopper can take. Accepting terms needed to generate an image is not automatically the same as agreeing to promotional email. If the store wants marketing permission, label it plainly. Avoid pre-checked boxes, vague phrases such as "continue," and copy that hides recurring messages behind delivery of a saved preview. Requirements vary by location and channel. The [GDPR overview](https://gdpr.eu/what-is-gdpr/) explains the principles that apply to personal data in the European Union, including purpose limitation and data minimization. Local marketing and electronic communications rules can add further requirements, so merchants should have qualified counsel review the exact capture language and retention policy. The operational side matters too. Store: - the consent wording or version shown at signup - the time and source of the submission - the channel covered by that choice - a way to withdraw or unsubscribe - a retention period for try-on data and generated images Email permission also does not create SMS permission. Collect phone numbers and SMS consent through a channel-specific form that meets the rules for the shopper's market. ## This signal beats a browse pixel when the message must be specific A browse event proves that a browser loaded a product page. It does not prove the visitor examined the dress, liked the red variant, or wanted to see the neckline on her own frame. The page might have loaded from an accidental tap. A completed try-on contains deliberate steps. The shopper chose a product, supplied an image, and reviewed a generated result. When she also identifies herself, the store has a first-party record of product-specific intent rather than an inferred audience assembled from a pageview. That does not make every try-on shopper ready for a sales barrage. It makes the first follow-up more relevant. The message can return to the tried SKU, answer a hesitation, or restore the preview. A smaller product-specific list is more useful than a large file of popup addresses with no context. The broader [ecommerce website optimization guidance from Shopify](https://www.shopify.com/blog/ecommerce-website-optimization) recommends improving specific points of friction rather than treating conversion as one undifferentiated number. Try-on capture follows that logic. It preserves the product decision at the point where the shopper is actively resolving uncertainty. ## Build lifecycle states, not one permanent segment The purchased flag turns the capture into a moving lifecycle record. Without it, the segment only says "tried on at some point." With it, the marketer can separate people who need help deciding from people who already decided. | Current state | Meaning | Sensible treatment | |---|---|---| | Tried, no identity | Product interest without an address | Keep the experience on-site or use privacy-safe ad audiences | | Identified, marketing not permitted | Known shopper with limited permission | Deliver the requested service, suppress promotional email | | Identified, opted in, not purchased | Product-specific non-buyer | Follow up on the exact garment and hesitation | | Identified, purchased | Converted try-on user | Stop recovery and move to post-purchase treatment | | Item unavailable | Intent exists, original SKU cannot convert | Offer a close substitute only while the signal is fresh | The message strategy belongs downstream. [Virtual try-on email personalization](https://antla.io/blog/virtual-try-on-email-personalization-shopify) covers how the creative can use the considered item without turning creepy. [Re-engaging interested fashion shoppers](https://antla.io/blog/re-engage-interested-shoppers-fashion) covers how signal strength should determine the route back. Do not send every event everywhere by default. Klaviyo may need the email profile, try-on event, product identifiers, consent state, and purchase update. Postscript should receive only shoppers with valid SMS permission. Ads may use a permitted audience event without receiving the generated image. Analytics can use a pseudonymous event when identity adds no value. For the destination-level payload, use the [try-on data guide for Klaviyo, Postscript, and Shopify](https://antla.io/blog/try-on-data-klaviyo-postscript-shopify). The [Klaviyo help center](https://help.klaviyo.com/hc/en-us) then documents the platform mechanics. This article stops at the data contract because rebuilding every ESP flow would bury the more important decision: what deserves to be collected in the first place. ## What to reject before launch A lifecycle marketer should be able to reject a capture design even if it produces more addresses. Volume is not the same as permission, and permission is not the same as useful intent. Reject the design if it: - blocks the promised first try-on until an email is entered - bundles service delivery, email marketing, and SMS into one vague checkbox - stores a generated shopper image without a stated purpose or retention window - omits SKU or variant data, leaving only a generic subscriber - keeps sending recovery after the matching product was purchased - treats every try-on as permanent interest, even after stock and season have changed The [Antla email capture feature](https://antla.io/features/email-capture) is built around the useful exchange: more try-on value for the shopper and a product-linked identity for the merchant. The team still needs to decide its consent copy, retention period, and channel rules. Software can record those choices. It cannot make them responsible on the merchant's behalf. For non-buyers who have valid permission, [try-on remarketing for Shopify fashion](https://antla.io/blog/try-on-remarketing-shopify-fashion) covers the next job. Capture should make that work possible without forcing the remarketing plan into the popup itself. ## Questions merchants ask before collecting ### What data does virtual try-on collect from shoppers? The useful marketing record contains the shopper's email, the product and variant tried, the try-on time, consent state, and whether the tried product was purchased later. A virtual try-on may also process an uploaded or generated image, but merchants should store and share that image only for a clear disclosed purpose. ### How do I capture emails from virtual try-on on Shopify? Place a clear value exchange after the shopper has received or requested a try-on result. Offer to save the look, send it, or unlock another preview. Record the email with the SKU, variant, timestamp, consent source, and purchase state, then send only the permitted fields to your lifecycle tools. ### Do I need consent to email a try-on shopper? Marketing requirements depend on the shopper's location and the type of message. Delivering a requested saved look is different from enrolling someone in promotions. Use clear channel-specific language, keep evidence of the choice, honor withdrawal, and have qualified counsel review the form and privacy notice for the markets you serve. ## Turn one captured decision into a working loop Email capture is the bridge between the on-site preview and the next useful action. The [Shopify ecommerce conversion engine](https://antla.io/blog/ecommerce-conversion-engine-shopify) shows how that bridge connects in-session conversion with recovery after a shopper leaves. --- **About the author:** [Aaron](https://x.com/AaronfromAntla) founded Antla after realizing most fashion email lists were collected at the wrong moment, long after the shopper had already decided not to decide. Start by asking what the shopper gets for identifying herself and what your team will do differently with the SKU. If both answers are concrete, [add Antla to your Shopify store](https://apps.shopify.com/antla) and capture the decision while it is still active. ## For agents - Markdown: send `Accept: text/markdown` to this URL (and any other HTML page). - OpenAPI: https://antla.io/openapi.json - llms.txt: https://antla.io/llms.txt - Sitemap: https://antla.io/sitemap-index.xml - Docs: https://antla.io/docs - CLI: npx antla info (npm package antla) - Scope: antla.io is an informational marketing and docs site. The Shopify try-on backend is not on this origin. Install the app from https://apps.shopify.com/antla.