--- title: "Recommendation Tracking (Standalone)" slug: "mapp-fashion-recommendation-tracking-standalone" updated: 2025-12-19T11:19:08Z published: 2025-12-19T11:19:08Z canonical: "docs.mapp.com/mapp-fashion-recommendation-tracking-standalone" --- > ## 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 (Standalone) ## 1 Overview Recommendation Tracking records user engagement with recommendation placements when using the [Mapp Fashion API](https://docs.mapp.com/apidocs/introduction-2), rather than hosted widgets. It tracks when users: - Click on a recommendation - Interact with recommendations (for example, by navigating a carousel) This tracking is handled through Standalone Tracking, which automatically detects HTML data attributes and reports the relevant events. Hosted widgets include this tracking automatically. If you are using Standalone Tracking to fetch recommendations as JSON, follow the steps below to enable it manually. --- ## 2 Setup 1. Install Standalone Tracking on your site. 2. Add the required HTML data attributes to your recommendation placement elements (see examples below). 3. Once configured, Standalone Tracking automatically monitors and reports interactions — no additional scripting is required. > [!TIP] > **Tip:** You can freely style your placement HTML. Only the data attributes are required for event tracking. --- ## 3 Example Implementation ### 3.1 API Request Example Use the Mapp Fashion API to retrieve outfits or similar items: ```bash curl --request GET \ --cookie "x-session-id=1ed19575-8f0c-4fcf-90a9-cadb53d16960" \ --url 'https://example.org/api/items/123456/related?exclude_source_garment=true&max_simil' \ --header 'accept: application/json' ``` --- ### 3.2 Example API Response A simplified example of the JSON response: ```json {  "event_id": "64a4235910bb3e5ff0155f85",  "outfits": [    {      "content_id": "64a4235910bb3e5ff0155f86",      "raw_garment_id": 123456,      "items": [        { "raw_garment_id": 5417179 },        { "raw_garment_id": 5447235 },        { "raw_garment_id": 5403634 }      ]    }  ],  "similar_items": {    "content_id": "64a4235910bb3e5ff0155f8a",    "items": [      { "raw_garment_id": 5368268 },      { "raw_garment_id": 5387457 },      { "raw_garment_id": 5418274 }    ]  } } ``` --- ## 4 Tracking Events and Functions ### 4.1 HTML Markup Example Mark up your placement HTML using the **data attributes** returned from the API: ```xml
 

Outfits

 
   
     
                           Dress                        
     
                           Shoes              
   
 
     
         
``` Once these attributes are in place, Standalone Tracking automatically listens for and tracks: - Product clicks - Carousel navigation - Pagination interactions --- ### 4.2 Attribute Reference | **Attribute** | **Value Type** | **Purpose / Description** | | --- | --- | --- | | `data-dressipi-placement-id` | UUID | Provided by Mapp. Identifies where recommendations are displayed on the page. Use a separate placement ID for each placement type (e.g., “similar items”). | | `data-dressipi-event-id` | UUID | Returned by the API when retrieving related items. Must be set on the element containing the recommendations. | | `data-dressipi-content-id` | UUID | Returned by the API. Set this on the container, wrapping each set of items (for example, each outfit or similar items group). | | `data-dressipi-raw-garment-id` | String | Represents the `raw_garment_id` returned by the API. Corresponds to the Mapp Fashion identifier for the product shown. | | `data-dressipi-product-link-pdp` | None | Attach to any link element that leads to a Product Detail Page (PDP). Tracks when users click to view a product. | | `data-dressipi-product-link-quickview` | None | Attach to any element that triggers a quick view. Tracks quick-view interactions automatically. | | `data-dressipi-navigate-next` | None | Attach to any element that navigates to the next group of garments (for example, the next outfit in a carousel). | | `data-dressipi-navigate-previous` | None | Attach to any element that navigates to the previous group of garments (for example, the previous outfit in a carousel). | | `data-dressipi-paginate` | Number | Attach to any element that paginates between sets of items (for example, pagination dots in a carousel). | | `data-dressipi-tab` | String | Attach to any tab that toggles between content types (for example, “personalized outfits” vs. “model wear”). | --- ### 4.3 Carousel Navigation and Pagination For carousel navigation and pagination, you may need to customize your carousel library’s HTML controls. Most popular libraries (e.g., Slick or Swiper) allow this via their navigation or pagination configuration. - [Slick Example](https://codesandbox.io/s/slick-navigation-pagination-dressipi-qlyqj7) - [Swiper Example](https://codesandbox.io/s/swiper-navigation-pagination-dressipi-t74d92) --- ## 5 Manual Tracking via JavaScript If you render recommendations via the API (JSON) instead of hosted widgets, call these tracking functions directly. **Note:** All parameters below are required unless marked as Optional. > [!TIP] > **Tip**: > > When using hosted widgets, the HTML attributes you already documented fire the equivalent functions automatically (e.g., `data-dressipi-product-link-pdp` → `itemClickPDP`, `data-dressipi-navigate-next` → `carouselNavigate`). --- ### 5.1 itemClickQuickView Use this function when a shopper opens a product in a **Quick View** from a recommendation set. ```javascript Dressipi('track', 'itemClickQuickView', {  setId: '44ff586f-ac79-4810-bbac-146f49f02f9c',  itemId: 123,  requestId: 'UUID',  parentPageViewId: 'SnowplowParentPageViewUUID' // Optional }); ``` **Parameters** | Parameter | Type | Description | | --- | --- | --- | | `setId` | String | Identifier of the set containing the item (returned by the API as `content_id`). | | `itemId` | Number | The item ID that was clicked (API `raw_garment_id`). | | `requestId` | String | Identifier of the server request that generated the content (`event_id`). | | `parentPageViewId` | String | *(Optional)* Page view context ID that links the interaction to the correct page. | --- ### 5.2 itemClickPDP Use this function when a shopper clicks from a recommendation to a **Product Detail Page**. Parameters are the same as **itemClickQuickView**. ```javascript Dressipi('track', 'itemClickPDP', {  setId: '44ff586f-ac79-4810-bbac-146f49f02f9c',  itemId: 123,  requestId: 'UUID',  parentPageViewId: 'SnowplowParentPageViewUUID' // Optional }); ``` **Parameters** | Parameter | Type | Description | | --- | --- | --- | | `setId` | String | Related items set ID (API `content_id`). | | `itemId` | Number | Clicked item ID (`raw_garment_id`). | | `requestId` | String | Request identifier for the placement (`event_id`). | | `parentPageViewId` | String | *(Optional)* Page view context ID. | --- ### 5.3 carouselNavigate Use this function when a shopper moves between carousel slides (e.g., **Next** / **Previous**). ```javascript Dressipi('track', 'carouselNavigate', {  requestId: 'UUID',  direction: 'next',  parentPageViewId: 'SnowplowParentPageViewUUID' // Optional }); ``` **Parameters** | Parameter | Type | Description | | --- | --- | --- | | `direction` | String | `"next"` or `"previous"`. | | `requestId` | String | Identifier of the request that produced the carousel content (`event_id`). | | `parentPageViewId` | String | *(Optional)* Page view context ID. | --- ### 5.4 carouselPaginate Use this function when a shopper uses **pagination dots/pips** to jump between carousel pages. ```javascript Dressipi('track', 'carouselPaginate', {  requestId: 'UUID',  page: 2,  parentPageViewId: 'SnowplowParentPageViewUUID' // Optional }); ``` **Parameters** | Parameter | Type | Description | | --- | --- | --- | | `requestId` | String | Identifier of the request that produced the content (`event_id`). | | `page` | Number | Page number (numeric). | | `parentPageViewId` | String | *(Optional)* Page view context ID. | --- ### 5.5 tabClick Use this function when a shopper **switches tabs** between content groups (e.g., “You May Also Like”, “Recently Viewed”). ```javascript Dressipi('track', 'tabClick', {  tabName: 'Recently Viewed',  requestId: 'UUID',  parentPageViewId: 'SnowplowParentPageViewUUID' // Optional }); ``` **Parameters** | Parameter | Type | Description | | --- | --- | --- | | `tabName` | String | Name of the tab as displayed to the user. | | `requestId` | String | Identifier of the request that produced the tab’s content (`event_id`). | | `parentPageViewId` | String | *(Optional)* Page view context ID. |