Chat provides information about specific attributes of a product like the weight of a tent. Chat is context-aware and knows which page a visitor is currently on.
A Store is a separate entity in Clerk.io that contains all the data and settings for a specific domain. This can be a unique webshop, platform, language version, or anything else that should function as a separate entity.
They work completely separately and do not share data between each other. The only exception is that some features like Merchandising and Synonyms can be added across multiple Stores at once when needed.
A single User has access to all Companies, and usually all Stores that they are added to, from a single my.clerk.io login. There are no extra charges for users, so we recommend that everyone working with Clerk has their own user.
Clerk uses
Liquid for managing code designs. It’s a safe and flexible templating language that enables you to create any kind of design you want for your Clerk elements. This article covers the basics.
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.
Using Clerk should technically be free - you should always earn substantially more than you pay for it. That’s why we’ve built a detailed Dashboard and Analytics for all products, to show how it helps your business.
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 Recommendations and how they work.
The names of these Product Logics match what you see in the my.clerk.io backend when using
Sliders. 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 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 Search 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.