Skip to main content

Integrate Genlook with Omnisend

Learn how to connect Genlook with Omnisend

Written by Armintas Griežė

Genlook is a virtual try-on app for Shopify stores. Shoppers upload a photo and see how a product looks on them directly on the product page.

The Omnisend integration sends try-on activity from Genlook to Omnisend as custom events, so you can build segments and automation workflows around the products your shoppers try on.


Key Benefits

  • Record every completed try-on in Omnisend as the Genlook - Tried On Product custom event.

  • Receive a summary of all the products a shopper tried on in one browsing session as the Genlook - Completed Try-On Session custom event.

  • Create or update contacts by email for shoppers who share their email in the Genlook widget.

  • Use try-on events to trigger automation workflows and build segments.

How It Works

Genlook sends signed webhook requests to the unique Omnisend webhook URL whenever a shopper interacts with the try-on widget. Omnisend then records a custom event on the matching contact.

Genlook sends the try_on_session event 30 minutes after the shopper's last try-on. If a delivery fails, Genlook retries it up to 3 times with exponential backoff and then drops it, so webhook delivery is best-effort.

Before You Begin

  • Install Genlook on your Shopify store and make sure the try-on widget is active on your product pages.

  • Subscribe to the Genlook Pro plan. The webhook integration requires the Pro plan in Genlook.

Setup Process

Step 1. In Omnisend, go to Apps → search for Genlook → click Connect now → enable Genlook Try On & On Session integration feature → copy the webhook URL.

Step 2. In your Shopify admin, open the Genlook app and go to Customers.

Step 3. In the Integrations section, find Webhook → click Connect.

Step 4. Paste the Omnisend webhook URL into the Webhook URL field and click Connect.

What Data Is Passed

Custom Events

Genlook sends the following custom events to Omnisend: 

Custom Event Name

When it fires

Genlook - Tried On Product

Triggered when a shopper completes a try-on for a product.

Genlook - Completed Try-On Session

Triggered 30 minutes after a shopper's last try-on, with everything the shopper tried on in that browsing session.

Event Properties

Each custom event also stores the complete Genlook payload, including event, storeId, externalStoreId, occurredAt, customer, and data.

Event: Genlook - Tried On Product

Property

Description

Example

product_id

Shopify product ID of the product the shopper tried on.

gid://shopify/Product/10748412428593

variant_id

Shopify variant ID of the product.

gid://shopify/ProductVariant/55579770388785

product_title

Product title.

The Collection Snowboard: Liquid

variant_title

Variant title. Included when Genlook sends it.

-

brand

Product vendor.

Hydrogen Vendor

sku

Product SKU. Included when Genlook sends it.

-

price

Product price.

749.95

currency

Currency code in uppercase.

USD

product_url

Link to the product page.

https://omnisend-tsi-dev.myshopify.com/products/the-collection-snowboard-liquid

image_url

Product image URL.

-

categories

Product categories, separated by commas.

snowboard

store_customer_id

Shopify customer ID of the shopper.

gid://shopify/Customer/10832245686577

Event: Genlook - Completed Try-On Session

Field

Description

session_id

Genlook ID of the try-on session. Omnisend uses it to avoid recording the same session twice.

try_on_count

Number of try-ons in the session.

product_count

Number of products tried on in the session.

product_ids

IDs of the products tried on, separated by commas.

product_titles

Titles of the products tried on, separated by commas.

product_urls

Links to the products tried on, separated by commas.

image_urls

Image URLs of the products tried on, separated by commas.

top_product_title

Title of the first product in the session.

top_product_url

Link to the first product in the session.

top_product_image_url

Image URL of the first product in the session.

started_at

Time the session started.

ended_at

Time the session ended.

Create Automation Workflows with Genlook Events

You can use the custom events sent to create Automation Workflows in Omnisend. Go to Automation → Create workflow → Create from scratch. In the trigger area, select your custom event.

Note: The custom event must be synced to Omnisend at least once before you can select it as an automation trigger.

Here are example workflows you can build:

  • Try-on follow-up. Use the Genlook - Completed Try-On Session custom event as the trigger and send an email that reminds the shopper of the products they tried on.

  • Interested-shopper segment. Create a segment of contacts who triggered Genlook - Tried On Product in the last 30 days and use it for a targeted campaign.

FAQ

Which Genlook plan do I need?

You need the Genlook Pro plan to use the webhook integration.

Does the integration work for shoppers who haven't shared their email?

No. Omnisend records events only for shoppers Genlook identifies by email. Try-ons by anonymous shoppers aren't sent to Omnisend.

Does the integration subscribe contacts to my marketing emails?

No. The integration doesn't change a contact's subscription status. Omnisend sends marketing emails only to subscribed contacts.

What happens if Genlook can't deliver an event?

Genlook retries failed deliveries up to 3 times with exponential backoff and then drops them. Webhook delivery is best-effort.

What should I check if events don't appear in Omnisend?

Check that:

  1. Your Genlook plan is Pro.

  2. The webhook URL in the Genlook Webhook URL field is the one you copied from Omnisend.

  3. The shopper shared an email in the Genlook widget.

  4. At least 30 minutes have passed since the shopper's last try-on, if you're looking for the Genlook - Completed Try-On Session event.

  5. If the issue persists, uninstall and reinstall the app.


Didn't find the answer to your question? Reach out to our Support team through the in-app chat or at [email protected] – our team is available 24/7.

Did this answer your question?