--- title: "Recommendation Tracking" slug: "recommendation-tracking-plugin-intelligence" status: "update" updated: 2026-10-07T10:41:44Z published: 2026-10-07T10:41:59Z canonical: "docs.mapp.com/recommendation-tracking-plugin-intelligence" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Recommendation Tracking Recommendations display dynamically suggested products, for example, related items on a product page or personalized suggestions on the homepage. The Recommendation Tracking extension enables **product-level analysis** of these widgets. It captures which recommended products were loaded into a widget, which of them became viewable on screen, and which were clicked, and links these interactions to later purchases. This enables the evaluation of how effective different widget placements, positions, and algorithms are. --- ## What you can do - Measure recommendation performance from delivery through on-screen exposure to clicks and conversions - Compare placements (e.g., homepage vs. PDP vs. checkout) - Understand which product positions drive engagement - Attribute purchases back to earlier product interactions --- ## How it works - When recommended products are loaded into a widget, become viewable on screen, or are clicked, tracking requests are sent, including widget context (placement, product position, algorithm). - If a recommended product is **clicked**, its context is temporarily stored on the client-side (in a cookie). - If the product is **purchased** within seven days, this stored context is automatically attached to the purchase request, enabling attribution in Mapp Intelligence. - After sending, or after seven days, the stored data is removed. - All results are available through dedicated dimensions and metrics. > [!NOTE] > Note > > In this documentation, we use the term 'widget' to refer to any area on the page where product recommendations are displayed. --- ## Integration options How much you need to implement depends on how your recommendations are delivered. ### Mapp Fashion hosted widgets The built-in Mapp Fashion recommendation widgets need no additional implementation. ### Mapp Fashion API You use Mapp Fashion recommendation data but render the recommendations yourself. Register your product elements as described in [Step 3](/v1/docs/step-3-initializing-the-recommendation-elements). ### Custom recommendations You build your own recommendation logic and user interface. Register your product elements as described in [Step 3](/v1/docs/step-3-initializing-the-recommendation-elements). > [!NOTE] > Note > > Mapp Fashion also has a page called Recommendation Tracking. It covers the interaction tracking of Mapp Fashion recommendations, such as carousel navigation and pagination. This section covers the Mapp Intelligence extension that measures loaded, viewable, and clicked products and attributes purchases. --- ## Product statuses The extension records three separate stages for every recommended product. Each stage has its own product status, and the dimensions and metrics in Mapp Intelligence are built on them. | **Status** | **Pixel value** | **When it is triggered** | | --- | --- | --- | | loaded in reco widget | `loaded-reco` | The product is rendered inside the widget and registered with `add()`. The event fires as soon as the registered element is found on the page, so a product that sits below the fold and is never seen is included. | | viewable in reco widget | `viewable-reco` | The product has been visible in the visitor's browser viewport long enough to count as seen. By default this means completely visible for one second. Both the visible share of the element and the duration can be configured in the Recommendation Tracking extension. A product that only scrolls past is not counted, and each product is counted once even if it enters the viewport several times. | | clicked in reco widget | `click-reco` | The visitor clicks the product inside the widget. | Viewable means the visitor had the opportunity to see the product. It does not confirm that the visitor looked at it. Every viewable product was loaded into the widget first, so the three stages always narrow down in that order. > [!WARNING] > Warning > > The pixel values for the loaded and viewable statuses have changed. The Smart Pixel sends the new values from version 6.12.1 onwards. Version 6.12.0 sends `display-reco` and `view-reco`. Versions 6.8.0 to 6.11.x send only `display-reco` and `click-reco` and have no viewable status. The previous values are still processed, so existing implementations keep working. If you send recommendation tracking events without the Smart Pixel, use `loaded-reco` and `viewable-reco` in new implementations. ## Related - [Recommendation Tracking](/recommendation-tracking.md)