Clerk is built around a powerful API that offers many different ways to display results to customers. These are called Product Logics and offer various functionalities suited to different use cases.
This article explains the available logics for Email and how they work.
The names of these Product Logics match what you see in the my.clerk.io backend when using
Content. Each of them has a matching Endpoint in Clerk’s API, which you can inspect in our developer docs using the links provided below.
Clerk.js comes with a built-in function for showing products with sliders. This feature shows a row of products with a set of arrows, that lets customers navigate many products with just a few clicks.
It basically works by creating a long, horizontal list of products, and then showing a fixed “window” of products at a time, which is controlled with the buttons.
The slider functionality is coded to show an entire new row of products for each click, to show as many new products as possible with as few clicks as possible.
Instant Search is the dropdown component of the setup that pairs
Instant Search with a Search Page. The alternative is
Omnisearch, which combines both roles in one overlay.
If Omnisearch is already installed, you do not need a separate Instant Search dropdown. Configure live results in your existing Omnisearch setup instead.
This dropdown allows your customers to browse and purchase products directly from your search bar. It combines the best features from modern search engines, with an eCommerce-specific twist:
AI Importer lets you connect Clerk.io to any platform that exposes an API — without predefined configuration or fixed form fields.
The setup happens entirely within Ask Clerk.io. Describe what you want to connect, and Ask Clerk.io guides you through the rest: finding the API, requesting credentials, building the importer, and testing it before handing off to Data Sync.
These keys are used to access the data of your Store. They are found in my.clerk.io > Developers > API Keys.
They consist of a Public key, which gives access to endpoints exposing non-sensitive data, and a Private Key which allows you to work with data on the Store and access sensitive data, such as customer and order information.
As you probably know, email clients do not support the typical HTML/CSS/JS that run smoothly on all browsers.
For this reason, we use a workaround to produce our Email product recommendations dynamically.
We use a web template engine called Jinja and, through this, we can dynamically print all the product attributes and styles as plain images with links.
Clerk.io is fully GDPR compliant. This article explains everything you need to know about Clerk.io and GDPR, and how we make it easy for you to handle GDPR requests.
At
trust.clerk.io, you can review our privacy policy, subprocessors, data management, and much more. The page contains everything needed to understand how Clerk handles your data.
MJML is a markup language designed specifically for building responsive emails. Instead of wrestling with HTML tables and inline styles to get a consistent result across Gmail, Outlook, and Apple Mail, you write clean semantic markup and MJML compiles it into battle-tested HTML that works everywhere.
Clerk.io’s email campaign editor includes a built-in MJML editor, making it the recommended approach for creating email designs that look great on any device or client.
Clerk.io can inject recommendation popups into your webshop and let you control them from my.clerk.io. Use them to suggest products after a visitor adds an item to their cart or when they are about to leave.
Set up Search after
importing and checking your data. First identify how your theme opens Search on desktop and mobile, then choose the experience that fits it.
A theme can have separate desktop inputs, mobile icons, hidden panels, and homepage search fields. Inspect each before choosing triggers.
Open the webshop on desktop and mobile. Find every input or control that opens Search.
Use developer tools to inspect stable selectors and confirm which input receives typed text.
Test the native dropdown, mobile panel, Enter key, and form submission. Note which behaviours need replacing or retaining.
Check another page type; a homepage search field may differ from the header input.
Fodmagasinet’s example triggers are .search-bar #search-overlay-input and #frontpage_search_container. Check whether those selectors exist and have the same role on your webshop. A trigger container is not necessarily the text input itself.