How to migrate to Loomi for Shopify

Migrating to Loomi for Shopify moves your setup to Data hub and adds support for more markets. This guide walks you step by step, from staging to production. For more information on who benefits from the migration and what changes, see Migrate to Loomi for Shopify.

Prerequisites

Before you start migration work, confirm the following:

• Data hub access: Loomi for Shopify requires Data hub. Make sure your team can access and configure integrations there before you begin.
• Shopify staging or development store: You need a non-production store to validate the migration safely.
• Current setup inventory: Know which Bloomreach products you use today, whether you have custom consent or tracking logic, and which campaigns, reports, or templates depend on your current catalog names or event names.
• Required identifiers for Marketing: Ensure your project uses the required identifiers expected by Loomi for Shopify: email_id, shopify_id, cart_id, and cookie. These ID names must match exactly.
• Consent management: For the standard Web SDK setup, ensure your cookie banner includes the following consent categories before you enable tracking:
  • Marketing and Analytics
  • Sale of Data

1. Set up a staging environment

Use a Shopify staging or development store to validate the migration before modifying your live store.

Recovery requires engineering intervention. If something goes wrong, contact Support before attempting to reconfigure.

When you're ready to remove the legacy setup, always disconnect the integration in Data hub first, then uninstall the Shopify app. The order matters.

2. Review your current setup

Before you configure Loomi for Shopify, review your existing setup to understand what will be affected:

• Which Bloomreach products you use — Marketing, Search, or both.
• Whether you use custom consent logic.
• Whether you use custom web tracking or a legacy Bloomreach tracking implementation.
• Which campaigns, reports, or templates reference current catalog names or use the legacy search event.

3. Create the integration in Data hub

Follow the steps in Integrate Loomi for Shopify to connect your Shopify store, configure consent management, and select your destination products.

When you reach the token step, use the integration token shown in the Bloomreach: Loomi app in your Shopify admin (Apps > Bloomreach: Loomi). This token is specific to the Loomi for Shopify integration.

Don't use any of the following tokens as they authenticate different things and won't work here:

• Marketing project token — authenticates your Marketing project, not the Shopify integration.
• Search project token — authenticates your Search project, not the Shopify integration.
• Event Stream ID — identifies a Data hub event stream, not the integration itself

4. Configure Shopify Markets

During integration setup, if your store uses Shopify Markets, add each active country-language combination in the Markets, countries and languages section of the integration. Each configuration creates its own item collection in Data hub. You need one integration per store, not one per market.

5. Set up web tracking

Before you set up new web tracking during integration configuration, check your store for any legacy tracking code or an older Shopify pixel implementation. The review tells you which of the two paths below applies to you

Avoid duplicate historical events

When you migrate a store from the legacy Shopify connector to Loomi for Shopify, both integrations can try to import the same historical events—for example, purchase, purchase_item, and cart_update—causing duplicities. Follow these steps to keep only one integration as the source of truth at a time.

1. Turn off historical event sync when you set up Loomi for Shopify. Disable the Import historical data toggle in the integration configuration to skip the initial historical sync for stores that already have data from the legacy connector.

   

2. Let Loomi for Shopify create its item collections and event streams, then confirm it's receiving live customers, consents, and events correctly.

3. Validate your event and product counts before and after you enable the new feed to confirm the numbers match your expectations.

4. Stop the legacy Shopify integration only after you've validated the new feed. Customers, consents, and events now flow to your project through Loomi for Shopify and Data hub instead.

Avoid resyncing historical events after both integrations have run in parallel. A resync at that point reintroduces the duplicate data you just eliminated.

6. Configure the item collections (catalogs)

Finally, review the item collections created in Data hub or set up a new one.

Item collections are the containers in Data hub that store and manage your catalog data, making it available to Search, Marketing, and related use cases. If you configured Shopify Markets, each active country-language combination creates its own item collection with localized product data and currency.

In Data hub, go to Items and open the item collection created for your store. Confirm the following:

• The expected item collection exists for your store or market configuration.
• Product and variant data is present and matches your Shopify catalog structure.
• If you use multiple markets, each required country-language combination has its own item collection.
• Any downstream references to your previous catalog are updated to use the new item collection.

If you need to adjust how catalog data is structured, review the schema and destinations for the collection before go-live.

7. Validate before go-live

Before you launch Loomi for Shopify on your production store, review downstream dependencies, particularly catalog references and event-name dependencies in campaigns, reports, or templates.

Data and tracking

• Product and variant data is syncing correctly.
• Customer consent updates behave correctly.
• Key storefront events are arriving as expected: view_item, view_category, search_submit, view_search_results, add_to_cart, checkout, and purchase-related events.
• Switch from Marketing SDK to the Web SDK replaced the legacy search event with search_submit and view_search_results successfully.

Live experience

For Search:

• Events are validated using the Bloomreach Tracking Console.
• Search, autosuggest, collections, and recommendations widgets render correctly with live data.

For Marketing:

• Incoming events are correct. Open a customer profile in your project to verify.
• Campaigns and templates render correctly with the new item collection and event data.

Cleanup

• Reports or templates that use the legacy search event are updated to use search_submit or view_search_results.
• Campaigns, recommendations, or templates that reference old catalog names are reconnected to the new catalogs created by the migration.

8. Roll out to production

After staging validation is complete, repeat the approved configuration in your production store. Run a final QA pass on storefront behavior, event tracking, and any Bloomreach-connected campaigns or use cases before going live.

See also

• Loomi for Shopify FAQ