Company

Measuring Impact

Monitor your return on investment.

Clerk.io is built to help you grow your bottom line. The Dashboard and product analytics let you review the revenue associated with sales through Clerk.io and, when you provide profit data, the profit from those sales.

You can use actual profit for each sale, product-feed values, or estimates created with AI Modifiers. See Profit to choose the approach that fits your business.

Precise Tracking #

Sales tracking connects products found through Clerk.io with the orders in which they were bought. Use this attribution to inspect the products behind your dashboard totals.

An order is considered impacted by Clerk.io when a customer has bought at least 1 product from a Clerk.io element.

Clerk.io attributes a product as sold through Clerk.io when a visitor goes through these exact steps in the same session:

  1. Click a product through a Clerk.io recommendation, email, chat, or search result.

  2. Proceed to put the product in their basket.

  3. Place the order with the product in their basket.

Any other products in the order that were found elsewhere are considered organic.

Dashboard #

Open Analytics > Overview for your store’s main performance dashboard. It combines attributed sales, shopper comparisons, an estimated return, and peer benchmarks.

Timeframe #

Use the date-range selector to choose 30 days, 90 days, 1 year, YTD, All, or Custom. The last-update time shows when the displayed figures were refreshed.

Metric #

When your store provides profit data, choose Profit or Revenue in the page header. Your selection is remembered between the overview, Search, Recommendations, and Email analytics.

Stores without profit data do not see the dropdown. The descriptions below explain the Revenue view. See Profit for setup and calculation details.

Revenue overview #

The four cards show different parts of your store’s activity:

  • Sessions using Clerk.io: Sessions using Clerk.io, with their share of all sessions.
  • Orders with Clerk.io products: Orders containing at least one product found through a Clerk.io element, with their share of all orders.
  • Revenue from Clerk.io shoppers: The full revenue from orders containing at least one product found through a Clerk.io element, including the other products in those orders.
  • Revenue from products sold via Clerk.io: The exact revenue from the directly attributed products found through Clerk.io elements and added to the cart.

For example, a shopper buys a €30 product found through Clerk.io and a €20 product found elsewhere. The order contributes €50 to revenue from Clerk.io shoppers and €30 to revenue from products sold via Clerk.io.

These figures overlap. Do not add them together or interpret either amount as a measured increase caused by Clerk.io.

Sales breakdown #

Where your sales come from shows sales by Search, Recommendations, Email, and Chat, alongside sales not attributed to Clerk.io. Switch between Whole store and Clerk.io products to change the grouping.

Shopper comparison #

How Clerk.io changes the shopping journey compares conversion rate, average order value, basket size, and revenue per session. Choose Without Clerk.io or Store overall as the baseline.

Comparisons are observational: Shoppers who use Clerk.io may differ from other shoppers. These differences do not establish that Clerk.io caused additional sales.

Estimated return #

Your Clerk.io ROI shows the average order value difference between shoppers using Clerk.io and those without it. It multiplies that difference by the displayed order count to estimate additional revenue.

The section then shows Clerk.io subscription cost and revenue return when available. Unavailable cost or return figures appear as Unavailable. The additional-revenue calculation is an estimate based on the comparison, not a controlled measurement of uplift.

Peer comparison #

How you compare with your peers benchmarks conversion rate, average order value, and basket size against other webshops using Clerk.io. It shows percentile bands such as top 10% or bottom 30%.

Use the benchmarks to identify areas to investigate. Ask Clerk.io now opens the AI agent, while Meet our team takes you to help from the team.

Orders #

Open Data > Orders to inspect individual orders. Stores that provide profit data see profit in the overview, on the order details page, and for each product line. Read Orders for the underlying order data and Profit for setup and historical calculations.

Clerk tracks all orders from your webshop and gives you a single Orders overview for referencing how we get to the numbers in the Dashboard. This page merges the previous Tracked Orders and Order Details sections.

Orders overview #

Shows all orders Clerk receives—both orders tracked from the frontend and those imported via Data Sync. For orders tracked from the frontend, you’ll see the estimated value added by Clerk.

Orders are listed by their ID, and the time they were placed, so they reflect the listings from your webshop platform.

The overview gives you a quick insight into the impact from Clerk on recent orders, including an estimate of the value added.

When viewing orders in Clerk.io, you will see them marked with different sources:

  • Tracked: Orders received via the sales tracking script in the frontend
  • Synced: Orders received from the data sync with your platform

Order Details #

This lists all the orders that Clerk has received, whether through frontend tracking or by import. It’s used mainly to let you browse and reference any order that Clerk has access to.

Product analytics #

Each channel has a dedicated Analytics page with more detail:

  • Search: Find the searches that generate revenue, expose demand, or return no results.
  • Recommendations: Compare the performance of each Recommendations Element.
  • Email: Review revenue from clicked products, full orders, embeds, and campaigns.
  • Chat: Connect conversations with revenue, estimated time saved, topics, and unsolved chats.

Number Significance #

Attribution tells you which products shoppers found through Clerk.io before buying. Shopper comparisons show how groups differ, but do not isolate the effect of Clerk.io from purchase intent or other differences.

A larger order count makes averages more useful, but no fixed threshold proves causation. Use a controlled experiment when you need to measure incremental sales.

Clerk vs. GA #

Google Analytics (GA) is one of the most used analytics tools for eCommerce.

Many eCommerce owners use this tool to track important metrics, such as pageviews, searches, conversion rates, ROI of paid advertising and so on.

It is then natural to try comparing the data provided by GA with the data calculated by Clerk.io, especially regarding Clerk.io’s product usage

However, the two tools are meant to measure different metrics with different calculation logics. Here are the main differences:

  • By default, GA only measures searches from the actual search page, as it’s based on pageviews.
  • Clerk measures searches for both the Search Page and dynamic results shown by Instant Search or Omnisearch while the visitor is typing. This means that Clerk will show a higher number of searches and more realistic insights.

Recommendations #

  • GA only registers individual pageviews and does not consider the number of recommendation banners installed. Further, the number of pageviews can differ from Clerk since GA’s tracking script is often blocked by Ad Blockers.
  • Clerk shows the total number of recommendation banners viewed across pages. If your product page has 2 banners and 1.000 views pr. month, your monthly usage for this page is 1.000 x 2 = 2.000.