Segment Shoppers by Try-On Behavior for Email Marketing
Email segmentation by try-on behavior for fashion: Klaviyo properties, RFM plus preview signals, campaign rules, and privacy-aware targeting on Shopify.
Demographic segments guess. Behavioral segments remember that a shopper tried on three dresses last Tuesday, abandoned the satin midi, and never opened your last two promos.
Email segmentation by try-on behavior groups subscribers using virtual try-on events, frequency, recency, and product affinity so campaigns send preview creative to high-intent shoppers and education to browsers who have not generated yet. For Shopify fashion brands, it is the targeting layer simulation commerce needs to beat batch-and-blast CTR ceilings.
Segments, Klaviyo properties, campaign mapping, and governance below. Read the overview and Klaviyo flows for automation wiring.
Try-on behavior segments send preview creative to shoppers who already proved fit interest.
Core Behavioral Signals
| Signal | Definition | Email use |
|---|---|---|
| Try-on recency | Last generation timestamp | Urgency, restore preview |
| Try-on frequency | Count 30/90 days | Power users vs curious |
| SKU affinity | Most tried category | Hero pick |
| Try without purchase | Session, no order | Abandonment preview |
| Purchase after try | Converted | Suppress discount, ask review |
Antla try-on feed surfaces last 72 hours of generations for manual QA before segments scale. Antla virtual try-on documents feed and embed behavior.
Segment Recipes Ready For Klaviyo
High-intent previewers: Try-on in last 7 days, no purchase, viewed product 2+ times. Flow: abandoned cart try-on.
Preview power users: 3+ try-ons in 30 days. VIP early access with new arrivals try-on.
Stale preview: Try-on 30-60 days ago, no return visit. Win-back per re-engagement guide.
Never tried: Purchased or browsed, zero try-on events. Education email with click-to-generate CTA, not fake personalized hero.
Converted believers: Purchased after try-on. Post-purchase cross-sell per lifecycle guide.
Combining RFM With Try-On
Classic RFM (recency, frequency, monetary) plus try-on layer prevents overspending on dormant VIPs who stopped engaging preview.
Example: High monetary, low try-on recency, get win-back preview of last tried SKU. Low monetary, high try-on frequency, get first-purchase offer only after preview email two.
Shopify conversion benchmarks remind you revenue matters; try-on behavior is a leading indicator, not the ledger.
Property Hygiene And Decay
Set TTL on last_tryon_image_url (seven days typical). Expired URLs should fall back to static event image in templates.
Document property definitions in shared wiki so agency partners do not rename fields.
Campaign Calendar Mapping
| Week | Segment | Message |
|---|---|---|
| 1 | High-intent previewers | Preview reminder |
| 2 | Never tried browsers | How try-on works |
| 3 | Power users | New collection preview |
| 4 | Stale preview | Re-engagement |
Align with 30-day rollout plan.
Data Hygiene For Preview Segments
Do not export raw photos to your ESP. Store preview URLs and product IDs only. Enable Antla’s terms toggle on the PDP and link to your store privacy policy before scaling behavioral preview segments.
Performance Expectations
Segmented preview campaigns typically beat batch CTR reported in Klaviyo benchmarks because relevance rises. Measure revenue per profile, not only clicks.
Downstream, try-on users on site show 35% higher conversion on average across Antla merchants. Segmentation ensures email reaches shoppers likely to engage that PDP behavior.
Engagement duration 2-3x longer on try-on PDPs supports sending fewer, sharper emails to high-intent segments instead of weekly noise.
Returns can fall up to 30% when preview-informed segments buy with clearer expectations.
Export Formats For Weekly Segment QA
When automating is not ready, export try-on feed columns:
email,product_handle,preview_url,generated_at,variant_id
Upload to Klaviyo as CSV segment for one-off campaigns. Validate five random URLs manually before send. This weekly habit catches broken previews before they hit inboxes at scale.
Naming convention: Prefix segment names with TON- (try-on) so future team members know which flows require preview URLs at send time.
Suppression rules: Exclude profiles with active support tickets on sizing disputes from preview promos until resolved. Fit frustration plus personalized creative can read as tone-deaf.
Seasonal refresh: Rebuild “never tried” segment copy each quarter with current hero SKU photography so education emails do not reference sold-out styles.
Klaviyo Segment Export Template
When documenting segments for handoff, include:
| Segment name | Filter logic | Primary flow | Fallback if no preview URL |
|---|---|---|---|
| TON-high-intent-7d | try-on ≤7d, no order | Browse abandon preview | Static last viewed |
| TON-never-tried | orders >0, try-on =0 | Education | Click-to-generate CTA |
| TON-stale-30d | try-on 30-60d ago | Win-back | Category hero |
This table prevents “what does TON-high-intent mean?” six months later.
Anti-Patterns
- Emailing every profile a “personalized” hero without URL = broken trust
- Segment overlap causing three preview emails same day
- Using try-on count as vanity metric without purchase follow-up
Operational Playbook For CRM And Data Teams
Weekly segment review (30 minutes): Export try-on feed, spot-check five random preview URLs, confirm variant color matches Klaviyo property, archive broken SKUs.
Monthly overlap audit: List flows that can send preview email same day. Set Klaviyo smart sending and custom global cap property preview_email_sent_at.
Quarterly policy check: Confirm Antla terms toggle and privacy policy link on try-on modal still match your legal team’s current language.
Handoff to finance: Report revenue per try-on segment vs holdout so leadership funds automation instead of one-off campaigns.
When CRM and analytics share one segment dictionary, simulation commerce scales without weekly fire drills. Document segment names in plain language merchants understand: “Preview power users” not “SEG_TON_30D_V3.”
AI tools Shopify fashion places segmentation in stack context. best virtual try-on confirms PDP coverage before segment promises preview.
Frequently Asked Questions
What is email segmentation by try-on behavior?
It groups email subscribers using virtual try-on events such as recency, frequency, SKU affinity, and try-without-purchase patterns so campaigns send preview-led creative to high-intent shoppers and educational messages to those who have not tried on yet.
Which try-on data should sync to Klaviyo first?
Start with last try-on timestamp, last try-on product ID, and last preview image URL. Add thirty-day try-on count once basics are stable. Avoid syncing raw photos; use URLs and product references.
How is this different from browse abandonment?
Browse abandonment uses page views. Try-on segmentation uses fit evaluation intent, a stronger signal for apparel. Many flows combine both with splits prioritizing try-on when available.
Can I segment without automated sync?
Yes. Weekly exports from Antla try-on feed or manual CSV uploads work for pilots. Automate once segments prove revenue.
What privacy rules apply?
Use preview URLs and product references in Klaviyo, not raw photo files. Follow your store privacy policy and Antla terms settings on the PDP before scaling behavioral preview segments.
Segmentation Sibling Guides
- Email product images vs try-on CTR
- Virtual try-on email personalization
- AI email marketing fashion Shopify
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 segments like a performance marketer with a returns spreadsheet: behavior first, demographics second.
Export thirty days of try-on events and build one high-intent segment this week. Email them a preview-led flow before your next promo blast via Antla try-on feed.