Purchase Intent

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.

Settings

Chat Context #

Influence the tone of voice to match your brand. For example, tell Chat that it should reply in a formal tone without emojis or in a friendly, more laid-back tone. The language you use to write this prompt will control which language the Assistant communicates in.

Store description #

This text teaches the Chat how to perceive your webshop. It will be used as a reference when talking to customers.

Stores

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.

Users

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.

1. Click your Store name in the upper left corner
2. Click your Company name in the top of the dropdown
3. Click Users
4. Click the button Invite new user
5. Enter their email address
6. Set the role that best matches their needs
7. 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.

Code Designs

You can check the full documentation in our developer docs.

Objects #

Data points that are displayed when the design is rendered. They are wrapped with {{ and }}. E.g:

{{ product.price }}

In this example, Liquid is accessing the product object and renders the price attribute contained in it.

Logics

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.

Measuring Impact

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.

Precise Tracking #

One of the great things about our Dashboards is that you can see exactly which orders were impacted by Clerk and how much more valuable they are.

Recommendations

Logics

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 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.

Logics

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.