Basics
#
The Purchase Intent section of Audience allows you to find customers with specific purchasing patterns and intent. You have several ways of choosing the products that customers should have an interest in:
- Typing with free text. This uses Clerk’s search engine to find all matching products, and creating the Audience based on those.
- Using
filters to select items based on their attributes like
price > 100. - Writing product IDs separated by commas. This allows you to choose very specific products.
Interested In
#
This is the most powerful feature of Audience as it uses Clerk.io’s AI to intelligently predict which customers are likely to buy the products you want to sell, even if they have not purchased anything similar yet.
...Chat helps visitors describe what they need in natural language. It can use details such as brand, price, fitment, and product specifications to search your catalogue, choose relevant products, and ground its answers in your product data.
The sections below explain how each part of that conversation works.
Product search
#
Chat handles shopping questions about brand, price, fitment, and product specifications. It searches the catalogue using the details in the question and keeps the response grounded in your product data.
...The Chat guidance allows you to personalize your Chat to fit your exact needs.
Manage instructions
#
Open Chat > Guidance in
my.clerk.io. Click Add instruction in the relevant section. Use Title to name the entry and Instructions to write what Chat should do.
Use the toggle beside an entry to enable or disable it. Open the entry’s three-dot menu for actions such as Optimize, Undo and Delete.
For a frequently asked question, click Add FAQ and enter Question and Answer in the vertically arranged fields. Its secondary actions are also in the entry’s three-dot menu.
...Basics
#
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.
Inviting new users
#
Users with Admin or Manager roles can add new team members to a Clerk.io account.
- Click your Store name in the upper left corner
- Click your Company name in the top of the dropdown
- Click Users
- Click the button Invite new user
- Enter their email address
- Set the role that best matches their needs
- Click Send invite
Getting access
#
If a user already has access to another Clerk.io Company, they will automatically have access to your Company next time they log in.
...Clerk.io 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.io elements.
You can build designs by writing HTML, CSS, and Liquid directly in the code editor — or by describing what you want to an AI that writes the code for you.
...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.
...Omnisearch is a complete search experience in one overlay. It combines results as visitors type with full result browsing and facets, replacing the separate
Instant Search and
Search Page components.
Choose either Omnisearch on its own or Instant Search and Search Page together. If Omnisearch is already installed, you do not need to add either component. Customise your existing Omnisearch design and settings to improve the experience.
Omnisearch includes:
...