Klaviyo

Connect Genlook to your Klaviyo account in a few clicks. Once connected, Genlook sends two metrics: a Tried On Product event for each try-on, and a Completed Try-On Session event summarizing everything a shopper tried on in one visit. Both are ready to power segments and flows.

Genlook does not send order events. If you use Shopify, Klaviyo’s native Shopify integration already tracks purchases.

Before you connect

Genlook is installed and the try-on widget is live on your store.
Shoppers can be identified: they’re logged in, or you’ve enabled Email Collection in Genlook Settings (we recommend asking after the 2nd try-on).

Anonymous visitors who never share an email won’t appear in Klaviyo.

Connect Klaviyo

Open Integrations

Shopify: In the Genlook app, go to Integrations.WooCommerce, PrestaShop, and other platforms: Sign in at app.genlook.app, open your site, then go to Integrations.

Click Connect

Find Klaviyo and click Connect. A Klaviyo authorization window opens in a new tab.

Authorize Genlook

Sign in to Klaviyo if needed, then approve the connection. When you see the success message, close that tab and return to Genlook.

Confirm Connected

Back in Genlook, the Klaviyo row should show a Connected badge. You’re done; try-on events will sync automatically.

Choose a list (WooCommerce and other non-Shopify platforms)

At app.genlook.app, open your site’s Integrations and pick the Klaviyo list that consented shoppers should be subscribed to.Only emails captured with the marketing opt-in checkbox shown and ticked are subscribed, and sync is ongoing: emails captured before you choose a list are not backfilled.On Shopify you don’t pick a list (see Profiles and list building).

Which metric should you build on?

	Tried On Product	Completed Try-On Session
Fires	Once per try-on, within seconds	Once per browsing session, 30 minutes after the last try-on
Contains	One product	Every product of the session, with counts and totals
Best for	”You tried on X, here’s 10% off X"	"You tried on 5 things, here’s your fitting room”

They are sent side by side: adding the session metric changes nothing about the per-product one, so existing flows keep working.

A session covers one device and closes after 30 minutes of inactivity. If a shopper tries on three products anonymously, gives their email, then tries on two more, all five land in a single session event, and the three earlier ones are attributed to their profile.

Build flows in Klaviyo

In Klaviyo, create a Flow triggered by the metric Tried On Product or Completed Try-On Session. A few ideas:

Send a follow-up email 24 hours after a try-on if the shopper hasn’t purchased.
Target shoppers who tried on a specific product with reviews or a size guide.
Trigger on Completed Try-On Session where ProductCount is at least 3 to recap a whole fitting-room visit in one email.
Segment on RepeatProductCount at least 1: a shopper who went back to the same product twice is close to buying.

Event properties

Tried On Product

Mirrors Klaviyo’s native “Viewed Product” shape, so you can segment and filter flows on flat properties. Any field Genlook can’t resolve is omitted (never sent as empty).

Property	Example	Notes
`ProductName`	`Linen Shirt`	Product title
`ProductID`	`123456789`	Bare numeric id; matches the catalog synced by Klaviyo’s native integration, so it works with the `{% catalog %}` tag
`VariantID`	`987654`	Numeric variant id, when a variant was tried on
`VariantTitle`	`M / Blue`	Variant label; omitted for single-variant products
`Vendor`	`Example Brand`	Product vendor (brand)
`SKU`	`LIN-SHIRT-M`
`Price`	`49.99`
`PriceCurrency`	`EUR`
`ProductURL`	`https://shop.example.com/products/linen-shirt`
`ImageURL`	`https://cdn.example.com/linen-shirt.jpg`
`Categories`	`["Tops", "Shirts"]`	When known
`ItemNames`	`["Linen Shirt"]`
`Items`	`[{ ProductID, Name, VariantTitle, Vendor, SKU, ItemPrice, ProductURL, ImageURL }]`	One item per event for product blocks

Use {% catalog event.ProductID %} in a flow email to render the tried-on product from your synced catalog.

Completed Try-On Session

One event per browsing session, sent 30 minutes after the shopper’s last try-on.

Property	Example	Notes
`SessionID`	`abc123_1748772000000`	Stable id of the session
`StartedAt` / `EndedAt`	`2026-05-01T10:00:00.000Z`	First and last try-on of the session
`DurationMinutes`	`12`	Also `DurationSeconds`
`TryOnCount`	`6`	Total try-ons, repeats included
`ProductCount`	`4`	Distinct products
`RepeatProductCount`	`1`	Products tried on more than once
`Items`	`[{ ProductID, VariantID, Name, VariantTitle, Vendor, SKU, ItemPrice, ProductURL, ImageURL, Categories, TryOnCount, FirstTriedAt, LastTriedAt }]`	Most-tried product first; capped at 50
`extra`	`{ line_items: [...], presentment_currency: "EUR" }`	Checkout-shaped copy of the session’s products, for reusing checkout email templates (see below)
`ItemNames`	`["Linen Shirt", "Wool Coat"]`
`ProductIDs`	`["123456789", "987654321"]`	Bare numeric ids, for `{% catalog %}`
`Categories`	`["Tops", "Coats"]`	Deduplicated across the session
`TotalValue`	`170.49`	Combined price of the distinct products tried on
`PriceCurrency`	`EUR`
`TopProductID`, `TopProductName`, `TopProductURL`, `TopProductImageURL`, `TopProductTryOnCount`	`Linen Shirt`, `3`	The product they came back to most, flattened so a flow email can render it without looping

Rendering the whole fitting room in an email is a loop over Items; rendering just the hero product is {{ event.TopProductName }} and {% catalog event.TopProductID %}.

Reuse your checkout templates with `extra.line_items`

The session event also carries an extra.line_items array shaped and named like the one Klaviyo’s native Shopify integration puts on Checkout Started and Placed Order events. If you already have a template block that loops over event.extra.line_items, pointing it at Completed Try-On Session renders the fitting room without any changes.

"extra": {
  "line_items": [
    {
      "product_id": "123456789",
      "variant_id": "987654",
      "title": "Linen Shirt",
      "variant_title": "M",
      "vendor": "Example Brand",
      "sku": "LIN-SHIRT-M",
      "price": 49.99,
      "quantity": 1,
      "product_url": "https://shop.example.com/products/linen-shirt",
      "image_url": "https://cdn.example.com/linen-shirt.jpg"
    }
  ],
  "presentment_currency": "EUR"
}

Fields that can’t be resolved are omitted. quantity is always 1: a try-on has no basket quantity, and how many times the shopper tried a product on lives in Items[].TryOnCount.

Profiles and list building

How consented emails reach Klaviyo depends on your platform.

Shopify
WooCommerce and other platforms

Genlook does not create Klaviyo profiles directly. When a shopper opts in through the widget, Genlook records the consent on their Shopify customer record (emailMarketingConsent: SUBSCRIBED). Klaviyo’s native Shopify integration, which you run alongside Genlook, then syncs that profile and consent.This keeps Shopify the single source of truth for consent and avoids duplicate or conflicting profiles. Genlook’s job on Shopify is the Tried On Product event; profiles come from the native sync.

There’s no native Klaviyo integration for these platforms, so Genlook subscribes consented shoppers directly. Pick a list in your site’s Integrations (see the connect steps above); consented emails are added to it with SUBSCRIBED marketing consent and a Genlook Try-On Widget source.

Only emails captured with the marketing checkbox shown and ticked are subscribed.
Sync is ongoing: there’s no backfill of emails captured before you pick a list.
Profiles are deduplicated by email, so re-subscribing is safe.

Verify it’s working

Complete a test try-on as a logged-in customer, or after submitting an email through the widget.
In Klaviyo, open Analytics → Metrics and look for Tried On Product.
Open a customer profile and confirm the event appears.
Wait 30 minutes without trying anything else on, then check the same profile for Completed Try-On Session.

Disconnect

In Genlook Integrations, click Disconnect on the Klaviyo row. Events stop syncing immediately; existing Klaviyo data is not deleted.

Getting Started

WooCommerce / WordPress

Virtual Try-On for Retail

Integrations

Custom Integrations (Developers)

Widget API Reference

Help

Before you connect

Connect Klaviyo

Which metric should you build on?

Build flows in Klaviyo

Event properties

Tried On Product

Completed Try-On Session

Reuse your checkout templates with `extra.line_items`

Profiles and list building

Verify it’s working

Disconnect

​Before you connect

​Connect Klaviyo

​Which metric should you build on?

​Build flows in Klaviyo

​Event properties

​Tried On Product

​Completed Try-On Session

​Reuse your checkout templates with extra.line_items

​Profiles and list building

​Verify it’s working

​Disconnect

Before you connect

Connect Klaviyo

Which metric should you build on?

Build flows in Klaviyo

Event properties

Tried On Product

Completed Try-On Session

Reuse your checkout templates with `extra.line_items`

Profiles and list building

Verify it’s working

Disconnect