Clerk uses a single product catalogue for all visitors. This means that by default, every visitor sees the same price and list_price values synced from your store.
Many B2B and membership-based stores need to show different prices depending on who is logged in. Clerk supports this through two approaches, and the right choice depends on how your pricing works.
When to use which
#
Both approaches work across Search, Recommendations, and Email, on any platform.
...Product Data Uses
#
Clerk.io relies heavily on product data to understand the structure of your catalogue. Below are the various uses that your product attributes have in Clerk.io’s AI.
Optimising Search
#
Any texts that are sent for each product, will be indexed as keywords for that product.
This means that the more attributes you can send ( colors, sizes, brands, model-numbers, descriptions etc .), the better the search engine can become and the more it will be able to help your customers find the right products.
...Redirects allows you to create a direct connection between a query or keyword and a specific url. When can you use it?
For example, you have a stand-alone product for one category, and you want to make it possible for your costumers to directly search for the product page from the search, without passing by the search page.
This guide will be divided into two sections. The first one is to show you how to create a Redirect for your store and the second part the additional steps you will have to follow if you have a custom API store.
...Sales tracking is the link between what Clerk shows visitors and the orders they place. Without it, Clerk cannot learn from real purchases, personalise recommendations, or show accurate revenue attribution in the dashboard.
This article explains how tracking works at the API level, how to set it up, and how to debug it when orders are not being registered correctly.
How It Works
#
Every tracked order in Clerk goes through a chain of three connected pieces.
...Search comes with several settings that allow you to adjust its behavior.
When you change a setting, it triggers an analysis of your data that must complete before changes take effect.
This process can take up to 15 minutes but may be faster depending on the size of your catalogue. You can monitor the status in Data > Configuration.
The settings require
Search 3.0 to be enabled. Afterwards, you can access them in Search > Configuration.
...Hide Category slider
#
When a Clerk.io Recommendation is added to a category page that contains a low amount of products, it will show the same products on the page.
To avoid this, you can hide the Recommendation on category pages, by adding an if statement to the
Recommendation design code.
Change the number in the if statement to the minimum amount of products needed to show the Recommendation.
{% if products.length > 7 %}
<!-- Recommendation code -->
{% endif %}
E.g.:
...Moving your webshop from one platform to another — say, Magento 2 to Shopify, or WooCommerce to BigCommerce — involves more than just reinstalling the Clerk.io extension.
Your product IDs will likely change. Your sync method needs switching. Your designs may reference platform-specific attribute names. And your historical order data needs to carry over to keep the AI performing from day one.
This guide walks through each step.
Before Starting
#
Before touching anything in Clerk.io, answer these two questions:
...Running into issues with your custom integration? This FAQ covers the most common problems and their solutions, from single-page apps to tracking sales.
Single-page apps
#
These are also called Progressive Web Apps (PWA) and generally load the site as a single page, rather than loading individual pages as normal.
When a page is loaded for the first time, the Clerk.js library automatically fires a function to render all
Element blocks on that page.
...
