Loomi for Shopify FAQ

Find answers to common questions about the Loomi for Shopify integration, including compatibility, data sync, tracking, costs, and feature requests.

Compatibility and setup

Will the integration stay compatible with new Shopify releases?

Yes. A dedicated engineering team works exclusively on the Shopify integration and keeps Loomi for Shopify up to date with Shopify's platform changes. Existing merchants aren't disrupted, and you don't need to make code changes or involve a developer.

Upgrades: every upgrade to the highest supported Shopify API version is regression-tested against previous platform behavior and delivered centrally through the app.
Partner access: as a Shopify partner, we get advance notice of platform changes and early access to new features, so work starts before general availability. For example, we were among the first partners with early access to Shopify Sidekick extensions.
Current extensibility model: the integration uses Online Store 2.0, Theme App Extensions, and Shopify Web Pixels, rather than legacy theme-file injection. Your theme keeps receiving Shopify's own updates independently.

Does the integration support Shopify Liquid themes?

Yes. Liquid-based storefronts are the natively supported model. You add and configure the widgets in the Shopify theme editor without editing theme code, so your team doesn't need front-end development capacity.

Search, collections, and recommendations install as App Blocks.
Autosuggest installs as an App Embed.

The integration requires Shopify or Shopify Plus with an Online Store 2.0 theme. Headless storefronts use the APIs instead of the app.

Is the integration compatible with Shopify checkout extensibility?

Yes. Storefront and checkout tracking runs through a Shopify Web Pixel app extension, Shopify's native mechanism for checkout extensibility. It doesn't depend on the deprecated checkout.liquid theme file and requires no custom checkout scripting.

Shopify doesn't permit third-party app blocks on the checkout page itself, so onsite merchandising widgets appear on storefront pages rather than within checkout.

Does the integration support Shopify's B2B APIs?

No. Loomi for Shopify doesn't currently support Shopify's B2B APIs. If your store uses B2B features such as company accounts or B2B-specific pricing and catalogs, that data doesn't sync through the integration. Test any B2B-dependent workflow against a staging store before you rely on it in production, since behavior isn't guaranteed for B2B data.

Data and sync

Is the integration real-time?

Yes. Most data syncs to Bloomreach in real-time, including customer updates, consents, and events.

Product and variant updates:

Real-time updates: Attributes handled via Shopify Webhooks sync immediately. Note that Search indexes products, which may add up to 10 minutes of delay.
Daily updates: Fields without webhook support update once daily.

This ensures your data stays current, powering your use cases with fresh and accurate information.

What product and variant data are we bringing to Bloomreach?

The integration brings all product and variant data available from the Shopify product model, ensuring no field is missed.

Can I use SKU instead of Shopify variant ID as the item identifier?

Yes. Loomi for Shopify creates a product-level catalog and a denormalized variant-level catalog, and SKU is available as an attribute on variants.

To use SKU, open your item collection configuration and change the variant item identifier from the default Shopify variant ID to sku.

Use this approach when your business processes (for example, recommendations or reporting) rely on SKU rather than Shopify's internal variant ID.

Can I enrich Shopify product data directly in my item collection?

No. Loomi for Shopify manages the product and variant data it syncs from Shopify. Changes you send directly to those items through the API can be overwritten when the integration runs its full sync periodically.

To keep enriched data, add it in Shopify instead:

Add the enrichment data to your products in Shopify, for example as product metafields.
Let the integration sync the data to your item collection. It imports all product tags and metafields by default.
Use mapping to keep the fields you need.

Tracking

Why isn't `view_item` firing for some customers?

The Bloomreach Web SDK requires 3 Shopify customer privacy consent flags to return true before view_item fires:

window.Shopify.customerPrivacy.analyticsProcessingAllowed()
window.Shopify.customerPrivacy.marketingAllowed()
window.Shopify.customerPrivacy.saleOfDataAllowed()

If view_item doesn't fire for some customers, sale-of-data consent is the most common cause, since cookie banners often leave this category in a restrictive default state even when analytics and marketing consent are granted.

To debug:

Run all 3 functions in the browser console on the affected storefront.
Check whether saleOfDataAllowed() returns false. This is the most likely blocker, even when the other two return true.
Have the customer review their CMP's sale-of-data ("Do Not Sell") consent category configuration.

Configure your cookie consent banner to grant all three categories by default ("Always On") to avoid this issue.

Costs and support

Does the integration come with additional costs?

No. Bloomreach integrations are included as part of the platform at no additional cost.

I have a feature request. Is it possible to include it in the integration?

Yes. We have a dedicated engineering team that maintains and improves this integration, including adding new functionality.

Submit a feature request

Share your ideas with your Customer Success Manager.
They'll forward your request to the Product team.
Due to high user volume, the team carefully prioritizes all requests.

You can also ask your Customer Success Manager to share the Shopify roadmap for the current half-year to see upcoming planned features.