Recommendations Analytics shows how products found through your Recommendations Elements contribute to sales. Open Analytics > Recommendations to compare placements and find areas to improve.
When your store provides profit data, use the metric dropdown in the page header to switch between Revenue and Profit. Your selection is remembered when you move between analytics pages.
Stores without profit data do not see this dropdown. The sections below describe the Revenue view. See
Profit for how profit is supplied and calculated.
Search Analytics shows what visitors search for, which products they buy through Search, and where they struggle to find results. Open Analytics > Search to review your store.
When your store provides profit data, use the metric dropdown in the page header to switch between Revenue and Profit. Your selection is remembered when you move between analytics pages.
Stores without profit data do not see this dropdown. The sections below describe the Revenue view. See
Profit for how profit is supplied and calculated.
Clerk.io can read, analyse, and act across almost every part of your setup. Below is an overview of what it can do — both in terms of the questions it can answer, and the changes it can make.
All actions require your confirmation before they are applied.
Clerk.io can dig into your numbers in detail. This includes pulling core KPIs like revenue, orders, conversion rate, and average order value — and breaking them down by time period, product, or traffic source.
This guide covers the setup needed before Clerk.io can send emails on your behalf.
It applies to campaigns, flows, and automated triggers like Abandoned Cart. If you only want to add personalised product recommendations to emails sent from Klaviyo, Mailchimp, or another platform, go to
Embeds instead.
Each concept below explains what it does, when you need it, and how to manage it with Clerk.js or the API where code is required.
The recommended way to sync ideal.shop data is an
AI Integration using the shop’s API. Set it up for all data types, with content pages fetched through the sitemap as part of the same integration.