--- title: "Prerequisites for Mapp Fashion Onboarding" slug: "mapp-fashion-prerequisites" description: "What to provide before Mapp Fashion onboarding: product data, domain delegation, Smart Pixel tracking, order data, widget and email specs, per use case." updated: 2026-10-08T14:18:19Z published: 2026-10-08T14:18:19Z canonical: "docs.mapp.com/mapp-fashion-prerequisites" --- > ## 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. # Prerequisites for Mapp Fashion Onboarding This page lists what you need to provide before the Mapp Fashion onboarding starts. Please review it and provide the requested information before implementation begins. Which prerequisites apply depends on your use cases. The matrix in [section 5](/v1/docs/mapp-fashion-prerequisites#5-prerequisites-matrix) shows the requirements per use case. For the onboarding phases, see [Onboarding Steps](/v1/docs/mapp-fashion-onboarding-steps). --- ## 1 All Use Cases ### 1.1 Technical Contact Information Provide details of a technical contact person to ensure we can reach out regarding: - Website or domain issues - Third-party access Send this information to your Account Manager. ### 1.2 Product Data How you provide product data depends on when your implementation started. #### Product Catalog (New Implementations) New implementations manage product data in the [Product Catalog in Connect](/v1/docs/connect-product-catalog). Once the Product Catalog is available for your account, it is the required source for product data. - Use a catalog in Fashion-enabled mode. - Include all attributes with the State **Mandatory** and **Mandatory for fashion**. - Provide all available product images for each variant. Mapp Fashion labels each garment based on its images. - If the catalog contains fashion and non-fashion products, set the Enrichment Type for each variant. For details, see [Prepare Your Product Data for Import](/v1/docs/connect-product-catalog-prepare-product-data-for-import). #### Product Feed (Existing Implementations) Implementations that started before the Product Catalog deliver product data through the [Product Feed](/v1/docs/product-feed-mapp-fashion). Provide a CSV file containing a sample of your products. The file must include the required columns listed in the [Product Feed Attributes Reference](/v1/docs/product-feed-attributes-reference-mapp-fashion). *Example file:* [](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/sample_product_feed.csv)sample_product_feed3.73 KB[](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/sample_product_feed.csv) The complete product file with all required attributes must: - Be available via SFTP - Refresh at least once per day to ensure accuracy Provide Mapp with your SFTP credentials and configuration details. If IP allowlisting is in place, make sure Mapp IP addresses are allowed. --- ## 2 Recommendations The following prerequisites apply to recommendation use cases such as outfits, similar items and top or basket recommendations. The matrix in section 5 shows which of them each use case needs. > [!NOTE] > Note > > Product and customer identifiers must be identical across your product data, transaction data and tracking. For how identifiers map across product data, tracking and the API, see [Product and Customer Identifiers](https://docs.mapp.com/docs/mapp-fashion-product-and-customer-identifiers). ### 2.1 Domain Delegation Delegate and confirm your chosen subdomain for tracking user behaviour and activity on your website. Mapp only uses the delegated subdomain; your primary domain remains unaffected. Follow the instructions in [Delegate a Domain](/v1/docs/mapp-fashion-delegate-a-domain). Once delegated, provide your subdomain address to your Account Manager so we can create the DNS records and finalize setup. ### 2.2 Tracking Setup and GTM Access Mapp Fashion tracking runs on Mapp Intelligence Smart Pixel with the Mapp Fashion extension. - Smart Pixel must be integrated on your website. - Mapp provides the `host` and `namespaceId` that the extension needs. For the setup, see [Mapp Fashion extension](/v1/docs/fashion-extension) and [Tracking Setup](/v1/docs/mapp-fashion-tracking-setup). We require edit access to your Google Tag Manager (GTM) account to configure data collection. We will: - Send you a list of email addresses that need edit rights - Carry out all changes in a dedicated workspace You remain responsible for reviewing, testing, and publishing once setup is complete. ### 2.3 Sample Data (Orders / Returns) Provide two CSV files: one for Orders and one for Returns. Each file must: - Include a header row and one row per purchased item - Use a unique, incrementing `EntryId` for each record - Use the same product and customer identifiers as your product data and tracking See [Transaction Feed Attributes Reference](/v1/docs/attributes-reference-mapp-fashion) for required columns. ### 2.4 Live Data Feed (Orders / Returns) Complement the sample files with daily refreshed CSVs available via SFTP. For the format, see [Transaction Feed](/v1/docs/transaction-feed-mapp-fashion). Share SFTP credentials and add Mapp IPs to the allowlist if applicable. ### 2.5 Historical Orders / Returns Data Provide a historical dataset covering at least 12 months (preferably 24). Include: - Header row - One row per item purchased (multiple quantities of the same item must appear as separate rows) - Unique incrementing `EntryId` starting from 1 This data supports model training and analysis. --- ## 3 On-Site Recommendations (Hosted Widgets) ### 3.1 Widget Design Assets To customize widgets, provide: - Font color (HEX code) - Font family (include .ttf or .woff2 if custom; also include a web-safe fallback such as Arial or Helvetica) - Font size and line height (in pixels for headers, subtitles, and body text) Only one round of design changes is possible after implementation, so ensure details are final. ### 3.2 Widget Placement Prepare empty DIVs with static HTML IDs on your product detail pages for widget injection, for example for [Personalized Outfits](/v1/docs/mapp-fashion-use-case-outfits) and [How Similar Items Help Shoppers Find Alternatives](/v1/docs/mapp-fashion-use-case-similar-items). Share these DIV IDs with Mapp to ensure correct integration. For the available widgets, see [Widget Types and Configuration](/v1/docs/smart-hosted-widgets). --- ## 4 Themed, BAU, and Outfit Emails The following prerequisites apply to Themed, BAU and Outfit Emails. ### 4.1 Email Block Design Provide design specifications for: - Font color (HEX code) - Font size and line height for headers, subtitles, and body text Custom fonts are not permitted. Only one round of design changes will be possible after implementation, so finalize design details in advance. ### 4.2 Theme Brief *(Applies to Themed Emails only)* Provide a **theme brief** including: - Planned send date (or first send date for recurring campaigns) - Theme description - Product inclusion criteria - Preview or mockup of recommendation slots in the email This allows the Stylists team to align themes with your marketing strategy. --- ## 5 Prerequisites Matrix | Prerequisite | Enriched Attribute Export | Personalized Outfits | Similar Items | Top & Basket Recommendations | On-Site Recommendations (Hosted Widgets) | Themed Emails | BAU Emails | Outfit Emails | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1.1 Technical Contact Information | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | 1.2 Product Data | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | 2.1 Domain Delegation | ➖ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | 2.2 Tracking Setup and GTM Access | ➖ | ✅ | ✅ | ✅ | ✅ | ➖ | ➖ | ➖ | | 2.3 Sample Data (Orders / Returns) | ➖ | ✅ | ✅ | ✅ | ➖ | ➖ | ➖ | ➖ | | 2.4 Live Data Feed (Orders / Returns) | ➖ | ✅ | ✅ | ✅ | ➖ | ➖ | ➖ | ➖ | | 2.5 Historical Orders / Returns Data | ➖ | ✅ | ✅ | ✅ | ➖ | ➖ | ➖ | ➖ | | 3.1 Widget Design Assets | ➖ | ➖ | ➖ | ➖ | ✅ | ➖ | ➖ | ➖ | | 3.2 Widget Placement | ➖ | ➖ | ➖ | ➖ | ✅ | ➖ | ➖ | ➖ | | 4.1 Email Block Design | ➖ | ➖ | ➖ | ➖ | ➖ | ✅ | ✅ | ✅ | | 4.2 Theme Brief | ➖ | ➖ | ➖ | ➖ | ➖ | ✅ | ➖ | ➖ | BAU refers to Mapp Fashion Business as Usual emails. ## Related - [Onboarding Steps](/mapp-fashion-onboarding-steps.md)