Skip to main content

Tracking Smartfit Activity

Smartfit HTML elements emit browser-based activity events during initialization and whenever a result or relevant status is produced.

These callbacks allow shops to forward Smartfit activity to their own analytics, tag management, customer data, or data warehouse setup. When combined with the shop’s existing e-commerce events, they can help evaluate how Smartfit results relate to the buying journey.

important

Smartfit activity callbacks provide information about Smartfit initialization and results. They do not track purchases, revenue, add-to-cart actions, or the complete customer journey by themselves. These events must be collected separately by the shop and connected within the shop’s analytics environment.

For a complete list of available payloads, sources, and statuses, see the Activity Callback Reference.

What can be analyzed?​

Activity callbacks can be used to analyze areas such as:

  • Whether a Smartfit element initialized successfully
  • How often a fitting size or another Smartfit result was returned
  • How often no fitting size or no available fitting size was found
  • Which product codes were returned and whether they were in stock
  • How frequently recommendation, geometry, fallback, Category Sizing, or leasing results were displayed
  • Which products could not be found by Smartfit
  • Which technical errors occurred during initialization or result generation

When these events are combined with the shop’s own analytics data, additional analyses become possible, e.g:

  • Add-to-cart rates after a successful sizing result
  • Performance of alternative product recommendations
  • Product and category coverage

Comparing Smartfit events with shop data can provide further insights into customer behavior and correlations within the customer journey. A callback alone does not prove that Smartfit caused a specific user action or conversion. Controlled testing or another suitable comparison methodology is recommended when measuring such effects. Your Customer Success contact can advise you on designing such a controlled testing setup.

Common use cases​

Analyze the sizing funnel​

A shop can combine the following events:

  1. Product detail page view (event origin: shop analytics)
  2. Smartfit initialization (event origin: Smartfit activity callback)
  3. Smartfit sizing result (event origin: Smartfit activity callback)
  4. Add to cart (event origin: shop analytics)

This makes it possible to compare users who received a successful sizing result with users who received another result, such as no fitting size or no available size.

An initialization event only confirms that the Smartfit element loaded. It does not necessarily mean that the customer opened or interacted with the widget.

Button clicks or widget openings should therefore be tracked separately by the shop when this distinction is required.

Analyze no-stock and no-fit situations​

The following sizing statuses can help identify buying situations in which the customer cannot immediately continue with a fitting product, e.g:

  • 202: No fiting recommendations are currently in stock
  • 203: No fitting sizes were found

These events can be connected with subsequent recommendation clicks, product views, add-to-cart actions, or exits. For a more detailed description, see the Activity Callback Reference.

Possible questions include:

  • How often is a fitting product unavailable?
  • How many customers continue to an alternative product?
  • Which product categories generate the most no-stock results?
  • Does a recommendation help retain users who would otherwise leave the shop?