LessLens Virtual Try-On puts a “Try on virtually” button on your eyewear product pages, under Add to cart or under the title and price. Shoppers try your frames on their own face right on the product page, in the browser on computers and phones, with nothing to install.
What your store gets
- A try-on button on the product page, under Add to cart or under the title and price, on the frames you have in 3D. Each frame is matched to its product by the SKU you already use, so nothing changes in your catalogue.
- Every colour. When a shopper picks another colour, the button switches to that colour. If the try-on is open at that moment and the colour has another 3D model, it closes and the button switches to the new colour. Colours that share the product’s SKU can have a 3D model each, or all show the product’s. Colours and products without a 3D model show no button and stay exactly as they are.
- The try-on in place of the product photo. On a computer, it opens right where the product photo was, so the price, the colours and Add to cart stay in view. This includes galleries that fade from one photo to the next.
- A photo with the frame on. Shoppers can take one and share or save it. If the camera isn’t available, they can try frames on a photo instead; the photo stays in the browser.
- Your theme as it is. Classic and block themes: the button goes under Add to cart or under the title and price by itself, or wherever you put the
[lesslens_tryon] shortcode.
- Test mode. Check the try-on on your live store before shoppers see it: only a browser tab opened with
?lltest=1 shows the button, and nothing is loaded from LessLens for anyone else.
- Fast product pages. The try-on itself loads only when a shopper points at or taps the button. Pages other than product pages get nothing.
- Your own analytics. Button views, try-on openings, try-ons and kept try-on photos as events on your page, and in Google Tag Manager’s dataLayer if you switch it on.
- Private by design. The camera image is processed on the shopper’s device. LessLens doesn’t receive or store camera images, and the try-on sets no cookies.
A LessLens store key is required
This plugin connects your store to the LessLens virtual try-on service. The try-on, the 3D models of your frames and your store key come from LessLens with a pilot or a plan: see LessLens for WooCommerce and plans and pricing.
Until a store key is saved (it starts with pk_), the plugin adds nothing to your pages and nothing is loaded from LessLens.
External services
This plugin relies on the LessLens virtual try-on service of LessLens Inc., served from cdn.lesslens.app (hosted on Cloudflare). Nothing is sent from your WordPress server, and nothing is loaded in wp-admin. The requests below are made by the shopper’s browser, after you have saved a store key, on every single product page that gets a try-on placeholder: every product with a SKU and every variable product (a product with colours), whether or not that frame is in your LessLens catalogue. The service answers which of the page’s frames your store can show; the others get no button. To keep LessLens off some products, use the lesslens_tryon_show_button filter (see the FAQ). With test mode on, they are made only in a browser tab opened with ?lltest=1; in every other tab nothing is loaded from LessLens.
What is sent, and when:
- When such a product page loads: the browser loads the LessLens script (
https://cdn.lesslens.app/tryon/v2/tryon-button.js) and asks the service which of the page’s frames your store may show. That request carries your store key, the frame names (made from the product’s and its colours’ SKUs; for a colour without a SKU of its own, or with the product’s SKU, from the product’s SKU and the colour, such as ab-1234-gold) and your store’s address (the page’s origin). Once the service has answered, the request is repeated every 5 minutes while the page is in view and when the shopper comes back to the tab, and it is made again for each newly picked colour. For a colour named from the product’s SKU, if your catalogue doesn’t have that frame, the product’s own frame is asked about next (once per page). A variable product without a SKU of its own loads the script but makes this request only when a colour with a SKU is picked or preselected.
- When the shopper points at, focuses or taps the button: the public try-on files (the face-tracking model and lighting) are downloaded from
cdn.lesslens.app.
- When the shopper opens the try-on: the browser starts a try-on session (sending a short-lived ticket and the frame name) and downloads the try-on and your frame’s 3D model from
cdn.lesslens.app through links that expire within minutes.
- With every request: as on any website, the shopper’s IP address and browser user agent reach the service. LessLens counts button views and try-ons by frame, with the device type (from the user agent), the country (from the IP address) and your store’s domain, to run the service and for your store’s report. IP addresses are used only to stop abuse and are not stored. No cookies and no visitor IDs are used.
- Never sent: the camera turns on only after the shopper starts the try-on and allows it. The camera image is processed on the shopper’s device and is never sent to LessLens or anyone else, and neither are face data or measurements. A photo the shopper takes with the frame on goes only where they send it (their share sheet or downloads). A photo the shopper tries frames on instead of the camera stays in the browser. A pupillary distance the shopper types in stays in the browser tab and is passed only to your page.
The try-on window shows a small “Try-on by LessLens” link to business.lesslens.com. It is shown for every store key, pilots included; only stores on the Scale or Custom plan can ask LessLens to turn it off. The plugin has no setting for it.
The analytics events stay on your page; with the dataLayer option on, they also go to your Google Tag Manager, not to LessLens.
- Terms of use: https://business.lesslens.com/terms
- Privacy policy: https://lesslens.com/privacy
- Data and security: https://business.lesslens.com/security