Third-party integrations

​

Overview

• Privacy-compliant: All integrations respect the same consent settings as the Layers Pixel
• Non-intrusive: Integrations only use services already loaded on the page
• Dashboard-managed: Enable or disable integrations with a single toggle
• Extensible: New integrations are added regularly based on merchant needs

​

Configuring integrations

1. Go to the Settings page in the Layers dashboard
2. Select the Integrations tab
3. Toggle integrations on or off as needed
4. Select Save changes

​

Supported integrations

​

Rivo

• Personalize search results based on customer loyalty status
• Surface products relevant to available rewards
• Enhance customer segmentation with loyalty data

​

Smile.io

• Personalize search results by VIP tier and loyalty standing
• Surface rewards-eligible products to engaged shoppers
• Combine loyalty context with other session signals for richer targeting

​

LoyaltyLion

• Personalize search results using points balance and loyalty tier
• Target merchandising at high-tier shoppers or points-eligible customers
• Enrich session context with loyalty signals alongside cart, location, and history

​

Blotout

• Unified customer identity across touchpoints
• Privacy-compliant event tracking
• Enhanced attribution for visual search interactions

​

Microsoft Clarity

• Session recordings of visual search usage
• Heatmaps showing widget interaction patterns
• Behavioral insights for search optimization

​

Abra Promotions

• Accurate price sorting with active promotions
• Correct price filtering during sales
• Consistent pricing across search and collection pages

​

FoxSell Bundles

• Accurate price sorting and filtering for Mix & Match bundles
• Shopify pricing remains unchanged for other bundle types
• Searches for products included in a bundle can also surface that bundle

​

Edgemesh

• Coordinate image prefetching with Layers search and browse responses
• Leverage Edgemesh’s predictive engine alongside Layers’ Link header preload hints
• Unified performance optimization across search, browse, and product pages
• Improved purchase attribution through Edgemesh session tracking. Layers reads _em_session_id from order note attributes to link purchases back to browsing sessions (see Order Attributes)

​

Kairos

• Sessions Kairos blocks never load your storefront, so they never send events to Layers
• Search and browse analytics reflect verified human sessions only
• Conversion rates, click-through rates, and merchandising signals are not inflated by bot noise
• Nothing to configure. Install Kairos and the two work together from there

​

Okendo

• Personalize search and collection results using quiz-derived preferences
• Surface products that match a shopper’s stated needs (e.g., skin type, style preferences, fitness goals)
• Combine quiz context with other signals like cart contents, purchase history, and location for richer personalization
• No theme code changes required. Quiz data flows into Layers automatically once the integration is enabled

1. Enable the Okendo integration in the Layers dashboard under Settings → Integrations
2. Copy the webhook endpoint shown in the setup panel
3. In your Okendo dashboard, register the webhook endpoint and copy the signing secret
4. Paste the signing secret into the Webhook Secret field in Layers and save
5. When a shopper completes a quiz, Okendo sends the response to Layers via webhook
6. Layers normalizes the quiz answers and attaches them to the shopper’s session
7. All subsequent search and browse requests for that session automatically include the quiz profile as part of the contextual information

• quiz_response.create — a shopper submits a new quiz response
• quiz_response.update — a shopper updates an existing quiz response
• quiz_response.delete — a quiz response is removed

​

Yotpo

• Sort collection and search results by average review rating or review count
• Build merchandising rules that boost highly-rated products or products with a minimum number of reviews
• Filter products by star rating without any additional catalog setup
• No storefront code changes required. Yotpo already writes review data to Shopify metafields, and Layers picks them up automatically

1. Adds the Yotpo review metafield namespace to your store’s metafield sync configuration
2. Reads the review metafields that Yotpo writes to each product in Shopify
3. Exposes them as first-class product attributes you can reference in sort orders, merchandising rules, and search filters

​

Judge.me

• Sort collection and search results by review count
• Build merchandising rules that boost products with strong social proof
• Filter products by review count without extra catalog setup
• No storefront code changes required. Judge.me already writes review data to Shopify’s standard reviews.* metafields, and Layers picks them up automatically

​

Fera

• Sort collection and search results by review count
• Build merchandising rules that boost highly-reviewed products
• Filter products by review count without extra catalog setup
• No storefront code changes required. Fera writes review data to Shopify’s standard reviews.* metafields, and Layers picks them up automatically

​

Junip

• Sort collection and search results by average review rating or review count
• Build merchandising rules that boost highly-rated products
• Filter products by star rating or review count without extra catalog setup
• No storefront code changes required. Junip writes review data to Shopify metafields, and Layers picks them up automatically

​

Reviews.io

• Sort collection and search results by average review rating or review count
• Build merchandising rules that boost highly-rated products or products with a minimum number of reviews
• Filter products by star rating without any additional catalog setup
• Ratings stay current automatically. Reviews.io webhooks push new review events to Layers so aggregates update as reviews come in

1. Enable the Reviews.io integration in the Layers dashboard under Settings → Integrations
2. Enter your Reviews.io Store ID and API key and save
3. Layers fetches per-SKU rating aggregates from Reviews.io in batches and stores them against each product and variant
4. Layers registers a webhook with Reviews.io so new and updated reviews refresh the affected SKUs automatically
5. Ratings become available as product attributes you can reference in sort orders, merchandising rules, and search filters

​

PowerReviews

• Sort collection and search results by average review rating or review count
• Build merchandising rules that boost highly-rated products or products with a minimum number of reviews
• Filter products by star rating without any additional catalog setup
• Ratings refresh on a daily cadence, matching PowerReviews’ own 24-hour snippet cache

1. Enable the PowerReviews integration in the Layers dashboard under Settings → Integrations
2. Enter your Merchant ID and API key, and pick the Page ID attribute that holds the identifier PowerReviews knows each product by
3. Layers fetches a rating snippet per product from the PowerReviews Display API and stores the rating and review count against each product (and variant, when a variant Page ID attribute is configured)
4. A nightly sync keeps ratings current; each product is fetched as its own job so one slow product never holds up the rest
5. Ratings become available as product attributes you can reference in sort orders, merchandising rules, and search filters

​

Swym Wishlist Plus

• Sort collection and search results by wishlist count to surface trending products
• Build merchandising rules that boost products with strong wishlist demand
• Filter products by wishlist count without extra catalog setup
• No storefront code changes required. Swym already writes wishlist counts to a Shopify metafield, and Layers picks them up automatically

​

Fish Wishlist

• Personalize search and collection results using each shopper’s saved items
• Strengthen shopper affinities automatically as wishlists change
• Combine wishlist affinity with other session signals for richer targeting
• Nothing to configure. Install Fish Wishlist and wishlist events start feeding shopper profiles right away

​

Stockful

• Sort collection and search results by sales velocity or units sold
• Build merchandising rules that demote low-stock or out-of-stock products before they disappoint shoppers
• Push products approaching a projected stockout up or down without manual curation
• No storefront code changes required. Stockful writes inventory data to Shopify metafields, and Layers picks them up automatically

​

Moast

• Place Moast carousels, stories, and other widget types as merchandising banners
• Target and schedule Moast banners with the same contextual conditions and schedules as any other banner
• No new storefront plumbing. Layers ships the exact <moast-…> custom element markup Moast documents

1. Toggle Moast on in Settings → Integrations and select Save changes. Layers seeds a system banner type with slug moast on your store.
2. Open a merchandising rule and add a banner. Select Moast Widget as the banner type.
3. In the banner’s data fields, select a widget from the Moast widget dropdown. Widgets scoped to a product or collection in Moast are labeled as such. Moast resolves them on the page they render on.
4. Set the banner’s Web Media and Mobile Media (banners still require both), select a placement, and save the rule.
5. On matching browse requests, the banner’s data.widget field carries the resolved embed payload. Your storefront reads the payload and drops the markup into the DOM.

{
  "ref": "featured-carousel",
  "name": "Featured carousel",
  "type": "carousel",
  "placement": "global",
  "requires_product": false,
  "requires_collection": false,
  "tag_name": "moast-carousel",
  "script_src": "/apps/moast/embed/carousel.js",
  "payload_url": "/apps/moast/api/example.myshopify.com/widget/featured-carousel",
  "html": "<script src=\"/apps/moast/embed/carousel.js\" async type=\"module\"></script>\n<moast-carousel widget=\"featured-carousel\" shop=\"example.myshopify.com\"></moast-carousel>"
}

​

Klaviyo

• Target merchandising at shoppers arriving from a specific campaign without copying UTMs by hand
• Consistent campaign targeting across every contextual surface (rules, banners, blocks, sequences, search, sort orders)
• Automatic nightly sync keeps the campaign list current as you launch new sends
• Resolves Klaviyo’s dynamic campaign-name UTM placeholders to the literal values that actually reach the storefront

1. Go to Settings → Integrations in the Layers dashboard
2. Toggle Klaviyo on. A dialog opens with a Continue to Klaviyo button
3. Approve the requested read-only access to campaigns and account info in Klaviyo
4. Klaviyo redirects back to Layers and the initial campaign sync starts automatically
5. Open any surface that supports contextual conditions (for example, a merchandising rule) and select Campaign from the Klaviyo group in the condition field picker
6. Select a campaign from the searchable dropdown. The condition matches when the shopper’s session UTMs match that campaign’s source, medium, and campaign values

• equals — the rule matches only when the shopper arrived from the selected campaign
• does not equal — the rule matches every shopper except those who arrived from the selected campaign

​

Listrak

• Target merchandising at shoppers arriving from a specific Listrak send without copying UTMs by hand
• Consistent campaign targeting across every contextual surface (rules, banners, blocks, sequences, search, sort orders)
• Automatic sync keeps the message list current as you launch new broadcasts
• Falls back to the message subject line when a broadcast does not define a Google Analytics campaign name

1. In Listrak, open Integrations → Integration Management, create an integration with type Email, and enable the List and Message areas. Note the generated Client ID and Client Secret.
2. Go to Settings → Integrations in the Layers dashboard and toggle Listrak on.
3. Enter the Client ID and Client Secret and select Save changes. Layers validates the credentials against the Listrak API.
4. The initial message sync starts automatically. Ongoing syncs run every 15 minutes with a wider daily reconciliation.
5. Open any surface that supports contextual conditions (for example, a merchandising rule) and select Campaign from the Listrak group in the condition field picker.
6. Select a message from the searchable dropdown. The condition matches when the shopper’s session UTMs match that message’s tracking values.

• equals — the rule matches only when the shopper arrived from the selected message
• does not equal — the rule matches every shopper except those who arrived from the selected message

​

Intelligems

• Intelligems runs price tests on your store by updating product prices in Shopify and applying each shopper’s test-group price through its storefront price updates and checkout adjustments.
• Product tiles rendered by Layers use standard price markup, so Intelligems displays each shopper’s test-group price on them the same way it does everywhere else on your storefront.
• Price filters and price sorting in your search and collection results use the Shopify catalog price — the value Intelligems writes to your products when a test starts. Filtering and sorting can therefore differ from the test-group price your shopper sees displayed when that price differs from the catalog price.

​

Event forwarding

​

Implementation notes

• Integrations only forward events to services that are already loaded on your page
• Enabling integrations doesn’t load any additional scripts
• All integrations respect your store’s consent management settings
• Events are forwarded with the same payload structure as they are sent to Layers
• If an integration service is not available on the page, events will silently skip forwarding

​

Requesting new integrations

1. Go to Settings → Integrations in the Layers dashboard
2. Select Request an integration in the page header. The same button also appears when your search matches no integrations
3. Fill in the request form:
   • Service name — the tool or platform you want connected
   • Category — the closest matching category, or Other
   • What should it do in Layers? — which data should flow in and how you’d use it, such as sorting, filters, or targeting
4. Select Send request

• Technical feasibility
• Merchant demand
• Privacy and performance considerations
• Alignment with Layers’ integration principles

​

Need help?